The SOAP spec makes it optional to send type info for encoded parameters, such as input parameters in a SOAP request or the return type of a SOAP response. If an implementation assumes that the SOAP message contains type information it may not work with another that chooses not to send that info.
________________________________ Harry J. Kobetitsch UBS Warburg One North Wacker Drive Chicago, Illinois 60606-2809 312-525-5866 [EMAIL PROTECTED] -----Original Message----- From: Paolo Paganotto [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:31 AM To: AXIS Subject: Problem with null params Hallo everybody, I've a problem that I would like to share with you; every help will be highly appreciated. In my application (web server .NET, appserver Axis with Java classes), a Java class has a method that takes a bean as parameter; this bean is composed by other beans and primitive types. The point is: if .NET client sends the parameter bean with every field NON NULLin it, everything works fine; otherwise, if some of these fiels are NULL, a java.lang.reflect.InvocationTargetException is raised. I've checked the SOAP message sent to Axis by .NET with TCPMON, and I noticed that the NULL fields are omitted in the bean parameter, like if they don't exist. The method at Java side is invoked , but it raises exception before to send the result back. One way to make things work is to send empty params in the Bean, but this is not the exact behaviour I'd like. Does someone has any idea about the reason why this happen? Thank you a lot, Paolo Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
