A CDATA section in the XML you're trying to send back and forth? If you try to send invalid XML, or stuff that conflicts with the SOAP wrappers then yeah, I can see that, but what if you just want to send some simple elements with attributes?

James Black wrote:
Mike Hearn wrote:

  
I assume you're referring to character encoding issues here? I don't
understand what problems the soap wrapper could cause......
    

  From what I understand, when using a CDATA element, for example, there
can be things that will cause some problems with the XML parser that is
trying to figure out the message from the headers.
  Using a byte array ensures that your xml file will not mess up the
parsing.

  
James Black wrote:

    
Barry Lulas wrote:


      
I realize this is an Axis user group, but I wanted to pick your
brains
on a related issue.

I have a generic web service that I deploy via Axis.  The web
service
takes in an XML file as a request and returns an XML file as a
response.  My question is what is the best way to pass XML data
to/from a web service?  Should I simply use strings?

Any advise would be appreciated...

        
  Pass the xml file as a byte array, else you will have problems
with
the xml wrapper that soap uses. The byte array is base64 encoded, so
it
is a safe way to send it around.
  Also, you may want to zip the byte array before sending the xml
file,
to help cut down on size.




      



  

Reply via email to