ment the jar files from these directories are
within
the same ear, so they are classloaded together.
FYI, started working on this.
-David
--
View this message in context:
http://www.nabble.com/Load-time-dependency-ordering-problem-tp15361292p15546899.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
files from these directories are
within
the same ear, so they are classloaded together.
FYI, started working on this.
-David
--
View this message in context:
http://www.nabble.com/Load-time-dependency-ordering-problem-tp15361292p15546899.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
he same ear, so they are classloaded together.
>>
>
> FYI, started working on this.
>
> -David
>
>
>
--
View this message in context:
http://www.nabble.com/Load-time-dependency-ordering-problem-tp15361292p15546899.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
On Feb 11, 2008, at 6:56 AM, Jack Cox wrote:
David,
Thanks for the response. Using the application.xml to group the class
directories did not have the desired effect. The loader still sees
them as
separate 'jars' and appear to be classloaded separately. In their
'in-container' deployment
in an openejb.xml),
> when we do that we know in advance what classloader they come from and
> could easily roll them into one ear instead of creating one ear each
> as we do now.
>
> -David
>
>
>
David,
Thanks for the response. Using the application.xml t
On Feb 8, 2008, at 10:32 AM, Jack Cox wrote:
I'm trying to setup a 'out-of-container' test rig to test both a set
of
session beans and entity beans with openEJB. The session beans
depend on
the entity beans. The session bean class files are located in one
directory
tree, and the entit
at the entities get defined before
they are required by the session beans?
Thanks,
Jack
--
View this message in context:
http://www.nabble.com/Load-time-dependency-ordering-problem-tp15361292p15361292.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
