I haven't found any obvious code to handle the loading order for
ejb-in-war case yet, so probably that part is indeed undeterministic.
Yes, please try to see if you could work around this problem and we will
try to address this in the future release.
- Hong
On 3/8/2012 12:52 PM, forums_at_java.net wrote:
> Ah, very astute. Yes, the EJB in question is within a common library
> JAR,
> not within the EJB jar. That makes sense. I'm not sure how we would work
> around it, but I guess we could remove them from the common library
> jar and
> put them instead in to a "common" ejb Jar. Then we'd have two ejb jars
> in the
> application, (the main ejbs and the common ejbs). Perhaps that would
> solve
> this at least for the short term.
>
> We'll have to try that out.
>
>
>
>
> --
>
> [Message sent by forum member 'whartung']
>
> View Post: http://forums.java.net/node/883988
>
>