I'm having a weird problem where my service returns strings which are
zero terminated ( like C ), but
actually _IN_ the XML. The client side parser complains of invalid
XML characters.
I created the framework for this code with the
interface -> java2WSDL -> WSDL2java -> subclass technique.
The strings are fields of a class which is returned as elements in an array.
Here's a chunk from a tcpdump session watching the traffic:
0x0490 6f70 6c65 2e63 6f6d 223e 0a20 2020 3c61 ople.com">....<a
0x04a0 7274 6973 7420 7873 693a 7479 7065 3d22 rtist.xsi:type="
0x04b0 7873 643a 7374 7269 6e67 223e 4d6f 7263 xsd:string">Morc
0x04c0 6865 6562 6100 3c2f 6172 7469 7374 3e0a heeba.</artist>.
0x04d0 2020 203c 616c 6275 6d20 7873 693a 7479 ...<album.xsi:ty
You can see the zero just after the end of "Morcheeba"
I'm guessing this is an issue in org.apache.axis.encoding.ser.BeanSerializer
Anybody have a clue, or seen this before?
-C-
- Can't JMS Sample Chris Schaefer
- Can't JMS Sample David payam
- Re: xsd:String encoded with zero at the end... Steve Loughran
- Re: xsd:String encoded with zero at the end... Chris Schaefer
- Re: xsd:String encoded with zero at the end... Chris Schaefer
- property PROP_SEND_XSI BOURLON Agn�s
- Re: property PROP_SEND_XSI Dennis Sosnoski
- Re: property PROP_SEND_XSI BOURLON Agn�s
- Re: property PROP_SEND_XSI Dennis Sosnoski
- Re: property PROP_SEND_XSI BOURLON Agn�s
- Re: property PROP_SEND_XSI Dennis Sosnoski
