- This topic has 3 replies, 2 voices, and was last updated 19 years ago by
Riyad Kalla.
-
AuthorPosts
-
mwunderlichMemberDear all,
Working on a JSP project with Tomcat as the server. Up until yesterday evening, whenever I made any changes to a Java source file, the file would be redeployed automatically. This isn’t working anymore. I have to redeploy the project manually in order for any changes to take effect.
It might be related to the following error, which I get when starting eclipse:
“An internal error occurred during loading “<MyEclipsePath>/eclipse/plugins/com.ibm.webtooling.system.dtds_14.0.1/xsds/web-app_2_4.xsd”I have tried to start eclipse with “eclipse.exe -clean”l, which didn’t have any effects.
Any other ideas?Cheers,
Martin
*** Date: Fri Feb 10 09:18:07 GMT 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_05*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 4.0.3 GA
Build id: 20051025-4.0.3-GA*** Eclipse details:
Eclipse SDKVersion: 3.1.1
Build id: M20050929-0840Eclipse Platform
Version: 3.1.1
Build id: M20050929-0840Eclipse Java Development Tools
Version: 3.1.1
Build id: M20050929-0840Eclipse Project SDK
Version: 3.1.1
Build id: M20050929-0840Eclipse Graphical Editing Framework
Version: 3.1
Build id: 200507071758Eclipse RCP
Version: 3.1.1
Build id: M20050929-0840Eclipse Plug-in Development Environment
Version: 3.1.1
Build id: M20050929-0840Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
F:\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1660_798
-clean
-vm
C:\Programme\Java\jdk1.5.0_05\bin\javaw.exe
Riyad KallaMemberMartin,
Can you actually open the file that MyEclipse is complaining about? Also have you tried stopping the server, removing the deployment, rebooting your machine (I know, let’s just rule out everything) then recreating the deployment as exploded (it must be an exploded deployment) and then restarting the app server and seeing if that helps?
mwunderlichMemberThanks for quick reply! Actually, this morning everything was fine again. The console is back and the auto-deployment unfctioning again – for whatever reason. However, I do keep getting that error message when starting Eclipse. I just checked for that xsd file (which I should have done beforehand, I hear you moan) and it isn’t there, neither is that folder. So the only remaining questions are why is eclipse looking for that xsd all of a sudden and do I need it?
Cheers,
Martin
Riyad KallaMemberMartin,
If things are working that is the primary issue. That warning could be harmless from an outdated plugin registry entry especially if you have upgraded your release from a previous build. Just ignore it for now and I’ll double check on it and file a bug with the dev team if it is an issue. -
AuthorPosts