For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 3 voices, and was last updated 21 years, 11 months ago by
.
-
Posts
-
Got a strange one – I have created a new project, copied some files from an existing project, and created a new deployment.
When I run the application (JSP creating Javabean) it looks as if a previous project is being referenced somehow!
Looks like the deployer has somehow cached the Launch Configuration, I have tried to delete in and recreate but get the same problem!
<html>
<table>
<tr><td>What operating system and version are you running? </td><td><b>Windows XP Professional 2002 SP1</b></td></tr>
<tr><td>What Eclipse version and build id are you using? (Help > About Eclipse Platform)</td><td><b>Version: 3.0.0 Build id: 200312182000</b></td></tr>
<tr><td>- Was Eclipse freshly installed for MyEclipse?</td><td><b>Yes</b></td></tr>
<tr><td>- If not, was it upgraded to its current version using the update manager?</td><td></td></tr>
<tr><td>- Are any other external plugins installed?</td><td><b>No</b></td></tr>
<tr><td>- How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*</td><td><b>8</b></td></tr>
<tr><td>What MyEclipse version are you using? (Help > About Eclipse Platform > Features)</td><td><b>3.6.200</b></td></tr>
<tr><td>What JDK version are you using to run Eclipse? (java -version)</td><td><b>1.4.2_03-b02</b></td></tr>
<tr><td>What JDK version are you using to launch your application server?</td><td><b>1.4.2_03-b02</b></td></tr>
<tr><td>What steps did you take that resulted in the issue?</td><td><b>Created new project and copied files from another project</b></td></tr>
<tr><td>What application server are you using?</td><td><b>JBoss 3.2.3</b></td></tr>
</table>
</html>Chris Parsons
Chris,
I don’t completely understand what is happening from your sentence:When I run the application (JSP creating Javabean) it looks as if a previous project is being referenced somehow!
I would say that 3.7 GA is out now, so I would encourage you to upgrade before continuing incase there was a bug fix in place that cleared this up for you.
When I run the application, it fails, and the error log says ‘Unable to load Launch Configuration for closed project XXX’ in the debug window, when XXX is a different project which is not referenced at all in the application I am running, by the Deployment Manager or anything else!
I have got around this problem by deleting and reinstalling Eclipse and MyEclipse, but now find the debugger does not appear to be working on JSP pages
I really don’t want to go to Eclipse 3.0 M7 because I use another plugin that does not yet work with this release – tying your releases to an particular version of Eclipse is a real pain – or will 3.7 GA work with 3.0 M6?
Cheers
Chris
When I run the application, it fails, and the error log says ‘Unable to load Launch Configuration for closed project XXX’ in the debug window, when XXX is a different project which is not referenced at all in the application I am running, by the Deployment Manager or anything else!
This does sound odd, I have never seen someone report this before.
I have got around this problem by deleting and reinstalling Eclipse and MyEclipse, but now find the debugger does not appear to be working on JSP pages
This is because you are not using a servlet container that supports the JSR 45 spec. You can find help in the forums on how to use the beta release of JBoss (that is using Tomcat 5) to support proper JSP debugging.
I really don’t want to go to Eclipse 3.0 M7 because I use another plugin that does not yet work with this release – tying your releases to an particular version of Eclipse is a real pain – or will 3.7 GA work with 3.0 M6?
3.7 GA was built against the M7 release of Eclipse 3, I do not know for a 100% that it won’t work against M6, but would bet that it probably wouldn’t.
tying your releases to an particular version of Eclipse is a real pain
We are as fond of it as you are. Unfortunately there is no way around it, we cannot predict or code against the API changes going into the future Eclipse codebase. If the Eclipse team decided to freeze the APIs for backward compatability sake, then we wouldn’t need to code against individual releases because we would be garunteed a stable API. However, things are not this way.
Sorry, I should have said – I _am_ using the Tomcat 5 container for JBoss (thanks to the info on this forum) so the JSR 45 spec should be supported (I have had this working previously, is there something I heed to set up again in Eclipse/MyEclipse??)
Chris
