<vendor>
Hot deploy in GemStone/J can be done while the server is up and running with
none of these constraints. Furthermore the configuration information in the
directory service is updated when any provisioning is done, so there is no
hand adjustment to do the next time you re-start the server.
On-line management is a strength of GemStone/J that we designed in from the
beginning.
</vendor>
-Chris.
> -----Original Message-----
> From: Colin Sampaleanu [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, February 15, 2000 9:36 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Dynamic Class Loading with Weblogic
>
> Dynamic class loading is what allows the hot deploy feature. The WL docs
> say
> that if you turn off the dynamic class loading (everything is on the
> system
> classpath), then hot deploy does not work. The documentation for hot
> deploy
> specifically mentions jars, and never mentions beans deployed just via the
> .ser file reference, so I would have to presume that you can only hot
> deploy
> via jars.
>
> You have to disable the existing bean to hot deploy a new version of it
> (and
> from what I know the jar has to have a different name). I don't know how
> you
> can do the disable and add outside of the console, I could find no api to
> do
> it. Ultimately, I would be curious how many people are really using hot
> deploy in WL, since it is so inconvenient to take advantage of.
>
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Thomas
> > Sent: Tuesday, February 15, 2000 4:51 AM
> > To: [EMAIL PROTECTED]
> > Subject: Dynamic Class Loading with Weblogic
> >
> >
> > This was also posted to the weblogic.developer.interest.ejb, but to
> date
> > there has been no answers.
> > Using Weblogic Server 4.51, I have set the class paths using the
> > recommended
> > WL approach to allow dynamic class loading :-
> > -classpath : contains the bare minimum
> weblogic\classes\boot
> > and JDK classes
> > -Dweblogic.class.path : contains our application classes and other
> > required WL paths
> >
> > However I am confused about what dynamic class loading really is ?
> > We were hoping that we could recompile a Bean (or any other
> > non-bean class)
> > and that the changes would be picked up straightaway. This appears to
> work
> > very occasionally, but most of the time we need to restart weblogic.
> > Our code changes DO NOT require the bean to be redeployed (i.e no
> > signature
> > changes etc).
> > When are classes reloaded ?
> > We are not using hot deploy yet (this we might try later) as our beans
> are
> > deployed using .sers, which I believe doesn't work ?
> > Does the dynamic class loader only work if a bean is redeployed using
> hot
> > deploy ?
> > Can anyone advise what steps we need to take to deploy using using JARS
> > instead of sers ?
> > And can anyone provide a script to allow hot redeploying using a script
> > (remotely without having to visit the weblogic console) ?
> >
> > thanks
> > Pete
> >
> > ==================================================================
> > =========
> > To unsubscribe, send email to [EMAIL PROTECTED] and include
> > in the body
> > of the message "signoff EJB-INTEREST". For general help, send email to
> > [EMAIL PROTECTED] and include in the body of the message "help".
> >
> >
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
