- This topic has 8 replies, 4 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
Report started at the end of this thread:
https://www.genuitec.com/forums/topic/error-when-creating-code-unbound-classpath-container/#post-207551Summary:
1) Add a deployment for a project
2) Work with the project for a while, either through multiple sessions of Eclipse or in a single session
3) At some point when you open up the deployment tool to force a redeploy of the project, you’ll notice it is no longer shown in the drop down and the deployment has effectively been removed from the dropdown but NOT removed from the App Server. You can tell this because when you manually re-add the deployment, you get a message about one already existing, and if you want to back it up or remove it.This has been observed on Windows and Linux installs of MyEclipse 2.7 and 2.8 beta series.
This bug requires a reproducable test case. We would appreciate any users that are able to nail down a reproducable test case that we can use to exploit and test/fix this problem. I have been unable to find a reproducable set of steps that exploit this problem consistently.
I am facing the same problem, in two situations in WinXP:
1. when eclipse processes are killed it loses all the deployments of all projects (always);
2. at random, when it executes (i guess) hot swap/deploy.I´m using MyEclipse 2.8 beta 1
____________________
Henrique VieciliHenrique,
Are you able to find a reproducable case for this? I tried for almost an hour to and wasn’t able to. The ironic thing is that it hasn’t happened to me for a while since then. If you are able to find a reproducable sequence that we can give to the devs and say “Hey guys, this is busted, this is how you break it” then they’ll be happy to fix it. I’ve already tried approaching them with “This is busted, I don’t know how, why or when… but its busted” they weren’t really able to do anything with that 😀Try closing the project an reopening it. I typically close project when not in use then reopen them at a later point in the week. myEclipse usually loses the deployments after a close and reopen. I’m using eclipse 2.1.2 and myeclipse 2.7 RC-1.
–Damon
Today I´ve lost them when MyEclipse refreshed the workspace at launch and executed a full rebuild. 😯
_______________________
Henrique VieciliTry closing the project an reopening it. I typically close project when not in use then reopen them at a later point in the week. myEclipse usually loses the deployments after a close and reopen.
True. We remove all deployments for closed projects because the projects are closed and according to the Eclipse “rules of engagements”, closed projects are effectively ‘dead’ until reopened. This restriction is detailed in the documentation here under ‘Deployment Termination Events’:
http://myeclipseide.com/enterpriseworkbench/help/topic/com.genuitec.myeclipse.doc/html/concepts/deployment.htmTrue. We remove all deployments for closed projects because the projects are closed and according to the Eclipse “rules of engagements”, closed projects are effectively ‘dead’ until reopened.
This might shine some light on it… I close all my projects when exiting Eclipse and open them all back up when loading it. I close and reload Eclipse at least 1 time a day…
What do you guys think about persisting deployments across ‘closed’ projects?
After looking at this behavior for a while I am going to close this bug. As Scott pointed out Eclipse treates “closed” projects as removed resources and expects other resources to do the same. This doesn’t just occur with deployments, it also occurs with EAP modules, Ant builds and many other project-specific resources. So to stay consistent with the Eclipse platform and avoid going against the spec I believe this to be the correct behavior (albeit annoying) now.
