>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?
No, I mean that in the ear jar file (META-INF/Manifest.mf), you rather place
a
reference to the jar file (or the directory) where the shared class is
located in.
When the ear is deployed, this path is then automatically added to the
classloader.
>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.
If I�m right informed, the J2EEDeployer can also immediately deploy
directories ...
this doesn�t make any difference to the "sharing" technique and allows you
to connect to your
build from the IDE of your choice ...
Otherwise, it is very convenient to have a composer tool. We built an
extension to Together/J that does everything from compiling, dependency
analysis,
xmi-export, generating meta-data from xmi, packaging and ... ta, ta ...
hot-deploying.
Very comfortable, very useful ...
Best,
CGJ
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
