Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
2.5.2
-
None
-
Java 6, Jetty, Java 5, Glassfish 2
-
Unknown
Description
I have two methods in my webservice that start with the same parameter (but one has two parameters, I know there is a general SOAP issue if two methods have identical signature):
@WebService(targetNamespace = "http://dummy/", name = "Dummy")
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
public interface Dummy {
@WebMethod
public void method(
@WebParam(partName = "badParam", name = "badParam", targetNamespace = "http://dummy/")
java.lang.String badParam,
@WebParam(partName = "anotherParam", name = "anotherParam", targetNamespace = "http://dummy/")
java.math.BigInteger anotherParam
);
@WebMethod
public void anotherMethod(
@WebParam(partName = "badParam", name = "badParam", targetNamespace = "http://dummy/")
java.lang.String badParam
);
}
This causes a javax.xml.ws.soap.SOAPFaultException: Message part
{http://dummy/}anotherParam was not recognized. (Does it exist in service WSDL?)
If I try to call those methods (I call them with the default test client generated with the Maven plugin).
I have attached cxfbug.zip and cxfbug_client.zip which are test projects where you can start the service with maven and then execute the default client against it, also with maven.