"Jung , Dr. Christoph" wrote:
> That�s funny,
>
> we�re doing something
> quite similar with a modified deployer here at infor ... and I just had a
> very fruitful discussion with Rickard on jboss-dev about that issue ...
>
> If you just like to "reuse" the byte-code of some class, put it into a
> seperate jar,
> say addressDetails.jar, and refer it in the Class-Path: addressDetails.jar
> entries of the
> dependent EAR manifest files.
>
> If you would like to "embed" an EAR into other EARS such that it is only
> once deployed and communication is optimised (technically, it is put into a
> parent classloader to the ones of the dependent ears), then
> wait two weeks - I just committed to do that extension to the
> J2EEDeployer (hey, BEA, can you do that?)
> ... will send a notification when ready.
>
> Best,
> CGJ
>
> -----Urspr�ngliche Nachricht-----
> Von: Manie Coetzee [mailto:[EMAIL PROTECTED]]
> Gesendet: Freitag, 8. Dezember 2000 15:03
> An: [EMAIL PROTECTED]
> Betreff: [jBoss-User] Shared classes
>
> Hi
>
> I am currently having a problem with shared classes.
> To give an example. I have two totally independant entity
> beans name Contact and Organization. Both use a class named
> AddressDetails. I do not want to have the AddressDetails in
> every bean that I deploy, and do not want seperate versions
> of the same thing. I want to know if there is a general way
> how you deploy a common package that all beans can use instead
> of it being packaged in each bean jar.
>
> Thanks in advance
> Manie Coetzee
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
Hi
Thanks for the help.
You were speaking of ear files... I think what you mean is that in the
ear jar file, the shared classes is included so that it is available in
the VM that JBoss and the beans runs in?
If that is the case I wonder if there is a way to have that
classes available while deploying individual beans for testing
and development purposes. I don't want to make and deploy a ear jar file
each time I just modify a bean or any other source file.
Thanks
Manie Coetzee
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
