For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 2 voices, and was last updated 12 years, 10 months ago by
.
-
Posts
-
I recently upgraded to v10.6 build: 10.6-20120727
However my problem started when I was using v8.x. I was hoping that upgrading to v10.x would fix the problem. It hasn’t.
I have a production enterprise application that runs on JBoss. Call the project Parcel. So I have the top level Parcel project and a Parcel EJB project and a Parcel WEB project. I also have a fourth project called Common that contains modules used by both the EJB and WEB projects. When I deployed the application I would put the ear file in the JBoss deploy directory and the common jar file in the JBoss lib directory. It has run like this for several years.
Recently I started getting class load problems in production on a specific set of beans in the Common jar file. The failure is in a jsp that is using iterate to go through a list of the beans. I could not find a second instance of the common jar file anywhere on the machine. So I removed ALL instances of the jar file and created a lib directory under the META-INF directory of the main Parcel project hoping that would fix the problem. NOT!!
So I dug further and have found that when I deploy to the EAR file the packages of the Common project is placed in the classes directory of the Parcel WEB.war directory in the EAR. I can’t remove the common jar file from the JBoss lib or the Parcel WEB-INF because the EJB.jar would not have access.
I have checked the build configuration and cannot see anything that tells MyEclipse to include the Common project during deployment. I do not know exactly when this started. I received a call from my user informing me this feature of the website was not working. Now I can’t figure out how to fix it other than physically deleting these packages from the war file.
I am at a total loss!!! Can someone please help?
I kept digging while working on the application. After months of research I just lucked on the cause.
If you go to Window > Preferences > MyEclipse > Java Enterprise Project > Web Project > Deployment it has a Dependent Java Project Deployment Policy. For Web projects MyEclipse was set to “Use Smart Deployment”. I changed it to Ignore. The EJB project was already Ignore. This resolved the issue.
Don’t know how this setting was changed. The project deployed successfully for years. It is working fine now.
