Robert Krüger wrote:
> >
> > If you need to exchange local interfaces between all the entity beans, then
> > there should be no problem putting them into one ejb-jar file. You'll
> > likely have to deploy them as a single unit anyway. You also cannot
> > distribute them across several servers unless you deploy all on each node.
> > So what's wrong with a single ejb-jar?
>
> 1) having to redeploy it when changing implementation code (not interfaces),
> finder queries or cache options in deployment descriptores etc. instead of
> redeploying a single ejb-jar which in our case is much smaller (about a
> factor of 14) - makes the development circle a pain and maintenance upgrades
> of production systems not as fast. redeployment of the entire application
> takes a while even on fast servers.
Well, if you're going to use CMR which uses local interfaces and those interfaces
use non-primitive parameters or return types, you're going to be stuck
redeploying all referenced classes anyway. For example take the case of class A
from ejb-jar 1 which has a reference to a class B in jar 2. If you attempt to
undeploy jar 2 there is no way you can unload class B since it's referenced by
class A in jar 1. So if the spec allowed CMR relationships between jars, they
would have to use remote interfaces. But then, the container would have to
maintain the relationships via remote calls.
>
>
> 2) when looking into the deployment descriptor files you deal with enormous
> monsters being a few Megs in size.
You can deploy more than one ejb-jar file in an application (and hence one VM) if
you package them in a EAR file. You would then be able to use CMR between
entities in different jars. Of course, you still have to deploy as a single unit.
>
>
> 3) we update changes to our production systems via rsync and would always
> have to update the entire beast if the implementation code or deployment
> settings were changed that only affect one part of the system.
>
I don't see why, but then this probably isn't for forum for discussing custom
deployment systems.
So in summary, using local interfaces forces you to deploy in a single package.
--Victor
===========================================================================
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".
