One option would be to treat the data as a binary message and use MTOM to send it. This should reduce the XML processing and will also avoid any encoding issues.
Paul On Jan 14, 2008 3:36 PM, Scott Malinowski <[EMAIL PROTECTED]> wrote: > > Hello, > > This is probably a SOAP question more than an AXIS2 question. If there 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 to 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 '<') and that 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 building the > response and leaves it unencoded? > > Thanks, > Scott > > ________________________________ > Looking for last minute shopping deals? Find them fast with Yahoo! Search. -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
