Re: xmlc reloading and autocompilation feature

I didn't read this directly from the spec.  I just remember it from
many conversations on the tomcat-user list where people stated this and
referenced the spec as requiring this.  So, you might want to double
check.  However, even if it isn't explicitly stated in the spec,
this is a good idea since at least Tomcat serializes sessions to disk at
server or app shutdown by default.  If you have non-serializable
stuff in your Objects that you haven't marked as transient or aren't
already static members, then you will probably get some pretty buggy
behavior when that object is deserialized.

Jake

At 06:42 PM 2/20/2003 +0900, you wrote:
> Is that in 2.3 spec? I seem to
> remember reading something like that. I will change the XmlcContext
> object to follow that. 
>
> David Li 
>
>
> On Wednesday, Feb 19, 2003, at 23:25 Asia/Tokyo, Jacob Kjome wrote:
>
>
> > Stuff that is put in the session
> > should be serializeable anyway if you want to have a portable
> > app....unless you mark non-serializable features of object as transient
> > (if they are not already static) or static.  Of course after making
> > those changes, your object *will* be serializable and, thus, your app
> > portable across appservers :-) 
> >
> > Jake 
> >
> > At 10:39 PM 2/19/2003 +0900, you wrote: 
> >
> > http://www.websina.com/bugzero/faq/iplanet.html
> >
> > According to this document, you should disable
> > the distributed session so the context doesn't expect the object put into
> > it to be serializable. 
> >
> > David Li 
> >
> >
> > On Wednesday, Feb 19, 2003, at 00:50 Asia/Tokyo, Tay Choon Heong, Malcom
> > wrote: 
> >
> >
> > Hi, 
> >
> > I'm new to xmlc and the autocompilation and reloading feature 
> > is very interesting. However, I am not very sure how 
> > to really use it outside of enhydra (as most projects I 
> > work on usually use the commercial app servers i.e. iplanet, 
> > weblogic) 
> >
> > I am wondering if the xmlc developers could provide some 
> > examples of xmlc reloading and autocompilation feature using 
> > the various application servers outside of enhydra as these 
> > features are what makes xmlc rock. 
> >
> > I tried to install the example provided in the xmlc2.2 alpha 
> > version on an iPlanet appserver 6.5 but cannot get it to work 
> > beyond the deployment. 
> >
> > Error I got: 
> >
> > [18/Feb/2003 23:30:00:4] error: SERVLET-put_nonserial: Putting 
> > non-serializable 
> > object "org.enhydra.xml.xmlc.servlet.XMLCContext@405ffd" 
> > when using NAS 
> > session 
> >
> > [18/Feb/2003 23:30:00:6] error: Exception: SERVLET-execution_failed:
> > Error 
> > in ex 
> > ecuting servlet ReloadTest: org.enhydra.xml.xmlc.XMLCError: Couldn't load
> > XMLC c 
> > lass 
> > [18/Feb/2003 23:30:00:6] error: APPLOGIC-caught_exception: Caught
> > Exception: 
> > java.lang.ClassCastException: org.enhydra.xml.xmlc.XMLCError 
> >         at 
> > com.netscape.server.servlet.servletrunner.ServletRunner.reportError(U
> > nknown Source) 
> >         at 
> > com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
> > wn Source) 
> >
> > Any helps or hints would be greatly appreciated. 
> >
> > Regards 
> > Malcom Tay 
> >
> >
> > _______________________________________________ 
> > XMLC mailing list 
> > XMLC@xxxxxxxxxxx 
> > http://www.enhydra.org/mailman/listinfo.cgi/xmlc
> >
> >
> > _______________________________________________ 
> > XMLC mailing list 
> > XMLC@xxxxxxxxxxx 
> > http://www.enhydra.org/mailman/listinfo.cgi/xmlc
> </blockquote></x-html>