What does XMLRPC change an undef type to when it reaches Java?

[cpjust]

Another problem I'm seeing is when passing a null value to a Java function over XMLRPC from Perl. I tried this:

$api->setExternalData( $ticketID, $key, undef );

and if I pass a null in Java to that same function, an exception is thrown, but in Perl it's not throwing an exception. Is undef changed to something other than null, like "" or something?

 

[Kirsle]

It might be not sending a value at all. In Java, functions are frequently overloaded (able to be called with varying lists of arguments). Check the javadocs. It might be something like:

public void setExternalData (int TicketID, string Key, whatever Else)

public void setExternalData (int TicketID, string Key)

And the API might be calling the latter.

If not, what does the Javadoc say? That'll help in figuring out what Perl's doing that isn't throwing an exception.

Cuvou.com | My personal homepage

perl -e '$|=$i=1;print" oo\n<|>\n_|_";x:sleep$|;print"\b",$i++%2?"/":"_";goto x;'

 

[cpjust]

No, there's no such overload.
I just fixed it by checking for undef in my Perl abstraction and die so that it's consistent to the way it works in Java.
Apparently that's how my co-workers were handling null (undef) parameters.