Aaron Mulder wrote:
> But we do have the manifest classpath working, right? If you put
> all your "external" classes in a JAR (in the deploy directory, I
> think) and then put that JAR in the Class-Path entry of the manifest file
> of your EJB JAR, I think both JARs will be reloaded when you update the
> EJB JAR. Someone who knows more about this can feel free to jump in
> here...
You are quite correct. That would work well in the case that the
additional classes don't do anything that would otherwise be restricted
by the EJB-spec, i.e. it is not "system code".
/Rickard
>
> Aaron
>
> On Thu, 12 Oct 2000, Rickard [iso-8859-1] �berg wrote:
> > Hi!
> >
> > Tilmann Ludwig wrote:
> > > I have one bean which is instantiating several classes, which are not
> > > EJB-beans. This classes
> > > are in the classpath, but outside the jar-file which is containing the
> > > bean-classes.
> > > When i redeploy the bean, only the classes inside of the ejb-jar-file are
> > > reloaded, not
> > > classes in the classpath, which has changed, too.
> > > Is it possible to do such a thing (perhabs from the management console) or
> > > had i to restart the
> > > server everytime, when i changed something in classes outside the
> > > ejb-jar-file?
> >
> > Since they are loaded through the system classloader you must restart
> > the entire server.
> >
> > In the future it might be possible to upgrade such classes without
> > taking down the entire server. But it is a very very tricky issue.
> >
> > /Rickard
> >
> >
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
