Checks done before deploying a EJB

Question

Weblogic Gurus,
I have a question about checks done before an EJB is successfully deployed by
WLServer.
Does the deployer try to resolve all classes in the jar file recursively down
to the last level, before reporting successful deployment? If it does, is this
equivalent to static linking as against dynamic linking generally encouraged by
Java Technology?
Thanks,
Abhay

Answer 1

abhay kulkarni wrote:
Rob,
Thanks for the reply.
Do you mean that the class implementing the remote interface is loaded at the
time of deployment?Yes, this class is loaded.
I tested with a small test case where the entity bean's method
instantiated an object whose class was not in the classpath of the WLS or in the
jar file for the EJB. The deployment succeeded. However, in a more complex case
I am developing, with a similar scenario, the deployment of the EJB failed with
NoClassDefError.We don't actually call any business methods on your bean during
deployment so it's possible that some classloader errors are seen later.
It depends on how your classes reference each other.
-- Rob
>
Thanks,
Abhay
Rob Woollen <[email protected]> wrote:
No, the EJB deployment does load your bean, home, local/remote
interface, primary key class, etc.
What problem are you seeing?
-- Rob
abhay kulkarni wrote:
Weblogic Gurus,
I have a question about checks done before an EJB is successfully deployedby
WLServer.
Does the deployer try to resolve all classes in the jar file recursivelydown
to the last level, before reporting successful deployment? If it does,is this
equivalent to static linking as against dynamic linking generally encouragedby
Java Technology?
Thanks,
Abhay