> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bhupesh Wagjiani
> For example, you have EJB Jar 1 that contains an entity bean and you have
> EJB Jar 2 that contains a session bean that uses the entity bean in EJB Jar
> 1. How would you package this. Our practice has been to package the remote
> jar for EJB Jar 1 within EJB Jar 2.
Pros:
- Good flexibility from a development standpoint (no classloading interdependency,
consistency can be enforced within the same deployment descriptor, etc...)
- EJB 2.0 relationships can be bidirectional
Cons:
- A little more awkward to use from an architectural point of view (increase
coupling in your application, forces to rejar/undeploy/redeploy a bigger
deployment unit)
> We also have a utility jar (non-ejb) that is used by all beans. Using this
> policy means we have to include the utility jar within every EJB Jar. This
> has the consequence that if something in the utility jar changes, all EJB
> jars need to be rebuilt and re-deployed. Is this good practice? Is there a
> better way to do this in order to minimise re-building and re-deploying?
No easy solution to this...
--
Cedric
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
