> 1. Create an application, with one ejb-jar file which contains multiple
> EJBs.
>
> 2. Create an application which has multiple ejb-jar files, oen for each
> EJB in the application?
2- will lessen the coupling of your application and will probably make it easier
for you to update parts of it, but fundamentally, these two approaches are fairly
similar in EJB 1.1.
The consequences for EJB 2.0 (and to some extent, J2EE with .ear files) are
different. For example, your EJB-QL queries will have to refer to non-local beans
as remote if they are not in the same application, which has some consequences
(like only unidirectional relationships are allowed in this case).
> While speaking of packaging, I was under the impression that a deployment
> descriptor should be portable across servers, including vendors. Yet, I've
> been told taht the DD for, say, Webloic, is very different from the DD for
> Websphere. What kindof portability are DDs supposed to have? Thanks.
The standard descriptors (ejb-jar.xml) are portable. Then each server has to have
its own set of proprietary descriptors in order to specify whatever extra
information or functionality they provide.
Theoretically, an EJB packaged with ejb-jar.xml and all the extra proprietary
deployment descriptors should be portable on all those different servers without
any modification.
--
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".
