Andy,
If you haven’t already opened a Bugzilla, see if Bug 217131[1]
applies to your situation. I've just added the workaround from a WTP newsgroup
post [2] to that bug.
Cheers,
Larry
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=217131
[2] http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.webtools/msg15652.html
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf
Of Tim deBoer
Sent: Tuesday, May 06, 2008 5:39 PM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Exception when deploying project to Tomcat from
Eclipse
Hi Andy,
Please open a
bugzilla against jst.server so that we can investigate. This mailing list is
not for reporting defects.
Thanks,
Tim deBoer
deboer@xxxxxxxxxx
|
From:
|
"Andrew
Murray" <Andrew.Murray@xxxxxxxxx>
|
|
To:
|
<wtp-dev@xxxxxxxxxxx>
|
|
Date:
|
05/06/2008
02:20 PM
|
|
Subject:
|
[wtp-dev]
Exception when deploying project to Tomcat from Eclipse
|
Hi. I could use
some assistance with the following problem:
“Could not
publish server configuration: null. java.lang.NullPointerException” when
deploying a project to Tomcat.
Steps:
1. Create new
server based on Tomcat 5.5 runtime
2. Choose a
single project to deploy on this server
2. Rename
server, check “Serve modules without publishing” and “Publish module contexts
to separate XML files”.
3. File + Save
4. Close file
and click OK to rename configuration files to match new server name.
5. Try to run
the server – causes the error when it attempts to publish
Environment:
- Tomcat 5.5
- Eclipse
3.3.1.1
Things that did
not fix the problem:
1. unchecking
“Publish module contexts to separate XML files”
2. clean the
server
3. clean the
workspace
4. restart
Eclipse
5. try Tomcat
6.x runtime
6. delete and
recreate the servers
7. delete and
recheckout the project, then re-add to server
8. rebuild
entire workspace
9. bang head
against desk
Temporary
workaround:
- Uncheck the
“Serve modules without publishing” checkbox – don’t want to do this as it
messes with a servlet filter we’ve written (which may be an issue on our part).
Things that did
fix the problem:
1. Rename the
entire project and web application – don’t want to do this, though, since it
puts me out of sync with the rest of the team. After a few weeks, the problem
mysteriously reappeared. It seems to be intermittent. If renaming the project
and web app fixed it, maybe it’s related to some kind of caching problem.
Is anyone else
having this problem?
- Yes, one
other person. The other team members seem to be running ok.
A google search
turned up this link (http://dev.eclipse.org/newslists/news.eclipse.webtools/msg15819.html), but everything
looks ok on our server.xml. I could provide this if needed.
Regards,
Andy_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
