XOM API for Processing XML with Java

[Adam Constabaris <adamc AT unc.edu>]

You have four, no, five, no, six options that don't involve calling for 
a change in the XOM API; they are, presented in no particular order:

1) Use something other than XOM.
2) Rewrite the bits of XOM needed to make Document objects Serializable. 

3) Ignore the error messages.
4) Direct the servlet engine to not serialize the sessions.
5) Use a different servlet engine that doesn't spit out the error 
messages for non-Serializable Session attributes.
6) Write an HttpSessionActivationListener that serializes any XOM 
documents in a passivating session as XML, and another that, on session 
activation, reads them back as XOM Documents.

For (4), see http://www.systemmobile.com/wp/?p=20

For (6), start here (despite the URL, this is Servlet Spec Javadoc):
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/servletapi/index.html

AC


Luca Passani wrote:
> Elliotte Harold wrote:
>
> > I'm sorry. I don't believe you, my son. Just because the serialization 
> > happens outside your control in the VM in no way means it takes zero 
> > time.  Serialization costs, whatever format you use.
> the serialization only happens once in a while under exceptional 
> circumstances (i.e. when the application server is restarted).
>
> The solution you propose would be wasting lots of CPU at each and every 
> HTTP request...
>
> Luca
>
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest