It cannot be classified as a bug, because the SOAP spec does not require xsi:type. Apache SOAP was originally written to require it, though, so it has problems when it is not included. The current code base (available, e.g., in the nightly builds) has some code to help with the exact case of xsi:null (or xsi:nil) being specified without an xsi:type. If you are not using a nightly build, you might want to try one to see whether it works for you.
BTW, there *may* be a bug in the code generating the message: the 2001 XML Schema specifies xsi:nil instead of xsi:null. .NET is known to have this bug. Scott Nichol ----- Original Message ----- From: "Justin F. Knotzke" <[EMAIL PROTECTED]> To: "Soap User Group" <[EMAIL PROTECTED]> Sent: Thursday, December 05, 2002 11:19 AM Subject: Missing Type.. > > I am getting the following back in an envelope: > > <rocomment xsi:null="1"/> > > According to the API, I rocomment is of type 'string'. > > I assume this is a bug on their end? Is there a way I can handle for > this? > > Justin > > > -- > Justin F. Knotzke > [EMAIL PROTECTED] > http://www.shampoo.ca > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
