Rickard �berg wrote:
>
> Hi!
>
> danch 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.
> > In addition to Rickard's response to this point, remember that Bean
> > Provider and Application Assembler are two distinct J2EE roles: just
> > because a one provider gives me a Customer bean and another an Order
> > bean doesn't mean I don't assemble them into one jar.
>
> An extremely important point. However, as pointed out by Marc, and which
> is critical, the really good way to do this is to use EAR files. That is
> the holy grail IMO.
It's the EAR that contains a WAR and any ejb-jars? I haven't read that
bit of spec in a long time.
<snip!>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
