Re: xmlc reloading and autocompilation feature

On Friday, Feb 21, 2003, at 00:19 Asia/Tokyo, Richard Kunze wrote:

> On Thursday 20 February 2003 14:49, Jacob Kjome wrote:
> > 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.
>
> If I'm not mistaken, it's strongly suggested but not actually required.
> Doesn't make much difference, though :-)

I just look at the Servlet 2.3 Spec. In 7.7.2 and 10.6, it discusses 
about serializable objects and HTTP Session.

It doesn't say anything about objects being put into the context to be 
serializable, only for the HTTP session. Also, it doesn't suggest or 
require the object to be put into the session to be serializable. Just 
mandate the containers be able to handle objects in the session that 
marked with Serializable interface in a distributed environment.

However, it's stated in the J2EE 1.3, 6.5. The only object that can be 
put into a HttpSession object are of Serializable, EJBHome, EJBObject 
and two others.

However, nothing about ServletContext's attribute is specified only 
that context is scoped to one instance per VM and nothing about if it 
has to be synchronized.

> > 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.
>
> +1 from me - many appservers want serializable sessions, and there's 
> no harm
> in making the XMLCContext serializable.

There is really no such requirement on the ServletContext unless it's 
in Servlet 2.4 or J2EE 1.4.

Again, the XMLCContext is bound to ServletContext not HttpSession.

I think the NAS implementation is not following the spec.

David