On Jun 11, 2008, at 5:57 PM, David Blevins wrote:
The crux of the issue is that perfectly valid approach to testing is
to treat the entire classpath and all modules in it as essentially
one big ear, the things like persistence units declared in other
jars will still be considered part of
of the classpath problem David points
at.
I suggest you try the same just to ensure that everything else works
correctly.
Anyway, David I'm looking forward to test your new OpenEJB build !
Regards,
Juan Manuel
--
View this message in context:
http://www.nabble.com/Eclipse-Multiple-Projects
-jar.xml file to register
the local
interfaces for my beans (at this point I don't have any remote beans).
--
View this message in context:
http://www.nabble.com/Eclipse-Multiple-Projects-and-Missing-persistence.xml-tp16391627p17764028.html
Sent from the OpenEJB User mailing list archive
://www.nabble.com/Eclipse-Multiple-Projects-and-Missing-persistence.xml-tp16391627p17764028.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
On Mar 30, 2008, at 8:29 PM, Chad and Doria Skinner wrote:
I have a project I am working on and we have separated our business
model from our business logic by placing them into different
projects in eclipse. These projects are both jars that are placed in
our ear file. When I try to run a
I have a project I am working on and we have separated our business
model from our business logic by placing them into different projects in
eclipse. These projects are both jars that are placed in our ear file.
When I try to run a test on one of our session beans in the EJB project
I keep
