axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Malinowski <>
Subject Re: Process SOAP message containg XHTML
Date Mon, 14 Jan 2008 17:42:19 GMT

Thanks for your response. I ran a test where I was sending back 400,000 characters, about
the same quantity as the xhtml document. The characters were simply 0123456789 repeated 40,000
times so there was no need to be encoded like the xhtml is. The test processed the data in
less than a second. This included sending the request, receiving the response, and parsing
the response via a call to getSOAPBody(). Whereas, sending just half as much data (about 200,000
characters) as an XHTML document took 68 seconds to do the exact same processing. I think
this means we are back to it being (most likely) a problem with xhtml and encoding.


----- Original Message ----
From: Jeff Greif <>
Sent: Monday, January 14, 2008 11:39:42 AM
Subject: Re: Process SOAP message containg XHTML

It's not certain that your problem is caused by parsing the XML-encoded
string.  Perhaps it would be worth testing the hypothesis by using one 
of the Axis2 samples that echo a string.  Invoke it with the several 
hundred KB string you've been testing with and measure sending and 
receiving times on client and server.


Scott Malinowski wrote:
> Hello,
> This is probably a SOAP question more than an AXIS2 question. If
> is a better place to post my question please let me know.
> I have written a SOAP web service using AXIS2. It returns XHTML as a 
> string. The problem is on the client side. It takes several minutes
> process the response, which is only a few hundred kilobytes. My 
> research on this has pointed me to the fact that the XHTML within the
> SOAP response has become encoded (e.g. '<' has become '&lt;') and
> it is taking awhile for this data to be converted back. It only takes
> a second or so for the client to send the request and receive a 
> response. The time delay comes when I call getSOAPBody() on the 
> client. I have tried wrapping the XHTML in '<<![CDATA[' and ']]>' but
> to no avail (it is still encoded in the SOAP response). How do I 
> return XHTML so that Axis2 and/or SOAP ignores the XHTML when
> the response and leaves it unencoded?
> Thanks,
> Scott
> Looking for last minute shopping deals? Find them fast with Yahoo! 
> Search. 

To unsubscribe, e-mail:
For additional commands, e-mail:

Never miss a thing.  Make Yahoo your home page.
View raw message