|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?)
he he he, that's the spirit :)
marc
|... 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]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
