You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Sean Capes <Se...@systemsunion.com> on 2001/01/11 18:06:08 UTC
Large SOAP messages??
Can anyone tell me if they have implemented a SAX based version of the
servlet (or indeed one of their own) that supports streaming right to the
HttpServlet boundary.
Our SOAP messages can be massive because we're using it as a portal into the
system, and I wondered if anyone had any insight into streaming end to end?
Or other methods of reducing the footprint in the JVM?
Don't really fancy rewriting the servlet if I can help it, can enough to do
already!! Any info you can provide would be greatly received.
Thanks in advance.
Sean Capes
Systems Union
Senior Principal Software Engineer
Systems Union House
(01252)556752
1 Lakeside Road
mailto:sean_capes@systemsunion.com
Farnborough
http://www.systemsunion.com
Hampshire
GU14 6XP
Re: Large SOAP messages??
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Sean Capes wrote:
> Can anyone tell me if they have implemented a SAX based version of the
> servlet (or indeed one of their own) that supports streaming right to the
> HttpServlet boundary.
>
> Our SOAP messages can be massive because we're using it as a portal into the
> system, and I wondered if anyone had any insight into streaming end to end?
> Or other methods of reducing the footprint in the JVM?
>
> Don't really fancy rewriting the servlet if I can help it, can enough to do
> already!! Any info you can provide would be greatly received.
>
hi,
streaming in HTTP is difficult as POST request requires content-length. however
with HTTP/1.1 it is possible to do chunking. generally streaming output
(serializing into XML) is easy but streaming input when deserializing is more
difficult as you need to start parsing and working on parsed input before all
XML is available.
we have implemented a version of SoapRMI that is based on pull parser that is
producing parsing events translated into deserialized object graph without
intermediary DOM tree (or such in memory representation of parsed tree). however
we have not implemented yet HTTP chunking (or tested with maybe some existing
servlet container that could do it).
in our implementation we have separated (de)serialization code called on
Writer/Reader. this part of code can be used separately of SoapRMI. all that is
need is to call simple API (modeled after castor API):
Marshaller.marshal(testObject, writer, SoapStyle.IBMSOAP);
and
deserTestObject =
(TestObject) Unmarshaller.unmarshal(TestObject.class, reader);
our implementation is open source and will be shortly available so we welcome
you to try it.
thanks,
alek
p.s. i have attached example test program that just do serialization and
deserialization to file but no streaming.
--
Aleksander Slominski, IU, http://www.extreme.indiana.edu/~aslom
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall - Fujiwara no Teika (1162-1241)