- This topic has 14 replies, 6 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
Unbound classpath container: ‘com.genuitec.eclipse.j2eedt.core.J2EE13_CONTAINER’
I have been running myEclipse for several months now, and had things clicking along nicely for a project I am working on. Things got a little confusing when I upgraded from 2.6.2 to 2.7 last month, but things continuted to run. Now, I am attempting to build a new project (actually the same project, but recreating it (with a new name) outside of the eclipse structure and into it’s own area on the File System, so that PVCS can get to it as welll, but that is another story.)
When I tried to add the J2EE 1.3 Library Set, under (Right Click)Project, Properties, Libraries, I receive the error above. This strutcutture is nowwhere to be found under the MyEclipse/plugins directory at all. I know what I am looking for, and it is not there, thus the error.
I assume I have to have this library so that I may do the servlet/request/reponse portion of my app. Without it, I can’t compile any of my servlets or Struts Actions, or anything that references the
javax.servlet.http.HttpServletRequest.Do I need to go back to 2.6.2? Did I botch something in the upgrade that I am just now seeing the effect of?
Ideas? Suggestions?
Skip.
I checked my installed plugins, and it said com.genuitec was at release 2.7 and not 2.7.1. I am currently updating to 2.7.1 to see if this takes care of things. If not, I will be removing it all, and reinstalling Eclipse 2.1.3 then installing MyEclipse 2.7.1. Anyone see any problems with this approach beside the fact that I am sick of reinstalling all this stuff every month or 2?
I am having the same error, except that I have to rebuild my project twice a week. Does 2.7.1 truly address this bug? Cannot continue like this.
rshan,
It cannot hurt to upgrade and our changelog is available here: http://www.myeclipseide.com/ContentExpress-display-ceid-27.htmlI found the solution to my problem. The J2EE 1.3 Library Container was not installed for the project. Solution:
1. Right mouse click on the project.
2. Select Properties
3. A dialog window will pop up. Click on “Java Build Path” on the right-sided panel.
4. Click on the Libraries tab on the left-sided panel.
5. Click on the “Add Library..” button.
6. Select “Java 1.3 Library Set”.
7. Click the Next button.
8. Click Finish button.
9. Click on OK button.I have a simular problem. Same error message. Using Eclipse 2.1.3 and myeclipse 2.7.1 on Windows 2000 with JDK 1.4.2.
In my situation however, the msg all of a sudden popped in the tasks view while working on a project that I’ve been working on for months. I updated to 2.1.3 and 2.7.1 right after they came out and everything has worked until now.
Using project->properties->java build path->add library…->J2EE 1.3 Library set, I tried to add the library again.
Right after adding it however, in the add library… dialog I could not unfold the newly added set (i.e. clicking the plus sign would not reveal the contained jar files). In the Package Explorer view of the Java Perspective, there was an entry saying something along the lines of “unresolved classpath entry”.
I restarted Eclipse, and all of a sudden the J2EE Library Container did show up in the Package Explorer, could be unfolded, and rebuilding my project worked.
So, my problem is solved for now, but I would really like to know if you have any idea what might have caused this and what was going on.
I don’t know if it’s related, but last week all of a sudden my project appeared to be not deployed anymore (I’m very sure I did not undeploy myself). I simply redeployed the project.
Thans in advance for all help.
So, my problem is solved for now, but I would really like to know if you have any idea what might have caused this and what was going on.
This was fixed with 2.8 beta 1 release, so when 2.8 GA comes out, this shouldn’t happen anymore. Also when we roll out future releases (3.9+) we can start taking advatage of ‘official’ Library Sets provided by the Eclipse 3 platform.
I don’t know if it’s related, but last week all of a sudden my project appeared to be not deployed anymore (I’m very sure I did not undeploy myself). I simply redeployed the project.
I’ve seen this happen before, and it just seems that the deployment list forgets sometimes. If you can narrow this problem down to reproducable steps, please let us know so we can get a test case together to see what is causing it. In the mean time I will continue to try and find one myself.
So, my problem is solved for now, but I would really like to know if you have any idea what might have caused this and what was going on.
This was a bug in ME 2.7.1 caused by a race condition that has been fixed in 2.8-Beta1.
I don’t know if it’s related, but last week all of a sudden my project appeared to be not deployed anymore (I’m very sure I did not undeploy myself). I simply redeployed the project.
It’s not related. Projects (especially packaged deployments) would be automatically undeployed in 2.7.1 if changes made to it were too large to be properly resynced. In 2.8 Beta 1 this behavior has been changed to marking the deployment as old.
It’s not related. Projects (especially packaged deployments) would be automatically undeployed in 2.7.1 if changes made to it were too large to be properly resynced. In 2.8 Beta 1 this behavior has been changed to marking the deployment as old.
I believe he is referring to a bug I see as well, where the deploy for a project is not longer available in the drop down, and you have to readd it.
@support-rkalla wrote:
I believe he is referring to a bug I see as well, where the deploy for a project is not longer available in the drop down, and you have to readd it.
I consider it a bug indeed. The issue is:
My project is deployed and I’m working with it. Suddenly I notice changes I make to source code are not reflected when I run my application through the webserver.
So, I go to [project root]->MyEclipse->Add and remove project deployments… I notice that the deployments table is simply empty. No messages or exclamation marks or anything.
I have had this happening multiple times with earlier versions of MyEclipse. It’s the first time I’ve seen this in the latest version(s).
arjan.tijms,
Ok since we are both on the same page, I’ll send the report in. Thank you for clarifying for us.I created this report to track it:
https://www.genuitec.com/forums/topic/deployments-in-dropdown-are-removed-at-random-closed/
