Assume you are not using EAR, how are people dealing with dependencies
between beans across multiple EJB Jars?
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.
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?
regards
Bhupesh Wagjiani
GamCom Solutions Limited
[EMAIL PROTECTED]
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Dave Wolf
Sent: 29 November 2000 18:06
To: [EMAIL PROTECTED]
Subject: Re: EJB packaging
I prefer to use a mixture of JAR and EAR
I like to use one JAR for each bean. Then for each system I write, I can
combine these JAR's into an EAR file for deployment. In this way I have a
modular design where I can bundle JARs into EAR in any order I need.
If the DD is properly created it should be fully portable. I reccomend
using the J2EE verifier program to be sure your vendor isnt adding
proprietary info into the DD.
<vendor>
I can say for Sybase we put no proprietary info into the DD. We should
accept any legal DD.
</vendor>
Dave Wolf
Internet Applications Division
Sybase
----- Original Message -----
From: "Kenneth D. Litwak" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 29, 2000 1:00 PM
Subject: EJB packaging
> What are the releative mertis of the two following approaches:
>
> 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?
>
>
> 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.
>
>
> Ken
>
>
===========================================================================
> 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".
>
>
===========================================================================
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".
===========================================================================
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".
