I am having a problem with Axis 1.1 Beta mapping a request to the proper method and it appears that the class RPCElement is choosing the wrong operation for my call. I would like to know if anyone considers this a bug or not.
My web service contains overloaded methods. For example, here are two methods: 1) MyObject test1(String s1, String s2, MyObject obj); 2) MyObject[] test1(String s1, String s2, MyObject[] obj); When my client calls method (1), Axis executes method (2) on the server. I ran my debugger with the Axis code and found that the class RPCElement selects the first matching operation that is a good fit rather than the one that is the exact fit. This is because the method isConvertable() in JavaUtils says it is OK to map a single instance of a class to an array of the class. If I shuffle methods (1) and (2) around in my web service's source code so that method (2) is found before (1), everything works OK. In my real application, I have five versions of the overloaded method plus many other methods, so this example has been simplified. This behavior seems to be a bug. Shouldn't RPCElement be finding the EXACT match instead of the first one that might be suitable? Can anyone comment on whether this is a bug or not? Thanks, Tim Dierks __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
