| J2EE Module Dependencies Disappear [message #205497] |
Fri, 07 December 2007 22:35  |
|
Originally posted by: bob.bucy.gmail.com
Having some problems with a ear file and getting the J2EE Module
Dependencies to take under WTP 2.0.1. I have an ear that consists of a
dynamic web project and an EJB project.
I can go into the J2EE Module Dependencies of the ear project and check
both the ejb and war projects, Apply, exit, and deploy the ear. In
other words, as long as I don't exit Eclipse I am fine.
But, If I re-start Eclipse, then go into the J2EE Module Dependencies of
the ear project, the war project is no longer selected, and when I look
at the "Add/Remove Projects" from the server view, it shows both the ear
and war projects as independent projects that can be deployed to server
(e.g. rather than just the ear).
Running out of ideas, read various information on the J2EE Module
Dependencies and how it relates to the Java Build Path and possibility
of dependencies not "persisting', but I'm not sure that is were my
problem is (e.g. this is at the ear level vs at a child project, seems
to be some what related, but slightly different).
Anyways, if anyone can give me some hints on what to look for. Thanks, Bob
|
|
|
] 
Search
Help
Register
Login
Home
