cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Björn (Commented) (JIRA) <>
Subject [jira] [Commented] (CXF-4201) Error if two methods start with a parameter of the same name
Date Mon, 26 Mar 2012 22:04:27 GMT


Björn commented on CXF-4201:

Thank you for your reply. Do I read it correctly that in document-literal soap, every method
should accept only one parameter? That is I should have written my methods in such a way that
they accept one wrapper object as parameter which contains all the other parameters? I wasn't
aware of that - in fact I struggled for a long time to make jax-ws/soap behave in such a way
as to not generate zillions of extra classes.

Thanks for the info!
> Error if two methods start with a parameter of the same name
> ------------------------------------------------------------
>                 Key: CXF-4201
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.5.2
>         Environment: Java 6, Jetty, Java 5, Glassfish 2
>            Reporter: Björn
>            Assignee: Daniel Kulp
>              Labels: jax-ws,
>         Attachments:,
> 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 =
>         java.math.BigInteger anotherParam
>     );
>     @WebMethod
>     public void anotherMethod(
>         @WebParam(partName = "badParam", name = "badParam", targetNamespace = "http://dummy/")
>         java.lang.String badParam
>     );
> }
> This causes a 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 and which are test projects where you can
start the service with maven and then execute the default client against it, also with maven.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message