Related to this one:
There has been a problem with using manifest classpath entry in ejb jar
files that are deployed in jboss. Has there been any solution on this
problem? There is a need for this when communicating between EJBs
deployed in separate jar files, i think.
If not i hope that someone that has insight in it (Rickard?) could give
a look on it. I will also try but i'm not too familiar with the deep
code yet :(
/Lennart
Tom Cook skrev:
>
> On Fri, 02 Feb 2001, you wrote:
> > Putting the helper class in the ejb.jar files becomes a maintenence nightmare.
>
> Well, you have a choice. You can put them in a jar in lib/ext, in which case
> you will need to restart the server when you change the class. Or you can put
> them in your jar files, in which case you will need to re-build and re-deploy
> all your jar files when you change it. A well-set-up build process should deal
> with this without hassle.
>
> Of course, if you want to pass instances of the class between EJBs and you have
> the class in each ejb jar file, then they will be loaded by different class
> loaders and will therefore give a ClassCastException. In this case lib/ext may
> well be your only option.
>
> Tom
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
http://www.benefit.se/english
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
