Also, just to let you know. It looks like there is a bug in the generation of the wsdl file from the service. This bug is related to the function parameter names that get generated. The first parameter is always called "in1" in the wsdl file and the other parameters match the original signature but are moved over to the right one (the second parameter name really should be the name of the first parameter, the third parameter name should be the second, etc.)
For example, the method --> foo(int bar, String[] baz) becomes in the wsdl file --> foo(int in1, String[] bar) but should probably be --> foo(int bar, String[] baz) Just trying to help out here, Adam -----Original Message----- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 2:25 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: xsd:byte??? I'll look into this if you send me your wsdl file describing the service. Thanks, Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115) "Adam Freeman" <afreeman@lightsu To: <[EMAIL PROTECTED]> rf.com> cc: Subject: xsd:byte??? 02/25/2002 03:53 PM Please respond to axis-user Hello, I am trying to send over an array of bytes to an axis service. I was running out of memory and took a look at what was getting sent over the wire and it looks like every single byte in the byte[] that is being sent over is being marshalled as an xsd:byte type. Is this a performance hit, a joke or what?? Is this supposed to be an improvement over base 64 encoding/decoding? <item xsi:type="xsd:byte">0</item> <item xsi:type="xsd:byte">0</item> <item xsi:type="xsd:byte">1</item> <item xsi:type="xsd:byte">-84</item> <item xsi:type="xsd:byte">0</item> <item xsi:type="xsd:byte">0</item> <item xsi:type="xsd:byte">0</item> <item xsi:type="xsd:byte">20</item> HUH??? (Please reply to this address because I am no longer on the axis user mailing list.) - Adam
