Hi!
Ari Suutari wrote:
> Imagine a company that developes and sells various EJB beans,
> say "customer" bean and "car" bean. One of their customers might
> buy the "custmer" bean and an other one would by the "car" bean,
> maybe someone would buy them both. So I guess that it would
> make sense to put those beans in separate jars.
If they are interrelated, no. Components in this context are rarely used
on their own, which is why component vendors tend to sell you complete
suites (that can be extended with individual customized components)
instead of components.
There is no normal case here though. It all depends on the actual beans.
If several components form an application why separate them? I don't
understand this tendency to do micro-management. It seems to introduce
more problems than it fixes.
> Also same thing for internal business: If you maintain
> a system with many different beans, woudn't it be a little
> bit hard to re-build a huge jar every time you update your code ?
One word: Ant :-) No, it's not a problem.
> However, building several jars is not good if parts (ie. remote interfaces)
> must be deployed by putting multiple copies of them in different
> jars.
Exactly. It will only introduce more micro-management. It is all about
deciding the coarseness of your application. If your application, or
suite, *really is* one component then fine, but otherwise I don't see
the point of having lots of jars. If the decision is based solely on
practical grounds I have found that using Ant I have much more control
over how jars are created and do not have to do it the bad way because
it is "easier".
regards,
Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
