@WebService method argument names

[rcarmichael]

If I've got an EJB3 Bean with @Stateless and @WebService defined with a method like:

addNumbers(int num1, int num2)

the WSDL generated will simply call the arguments arg0 and arg1. Is there a way to force the WSDL generated to actually use the proper argument names? In this silly case it isn't important but it is confusing for my web service users not to know the argument names.

Thanks!
- Ryan

[schueffi]

Hi

i think the solution should be somewhat like

@WebMethod
public int addNumbers(
 @WebParam(name = "myParamName1") int num1,
 @WebParam(name = "myParamName2") int num2
)

regards

Stefan Schueffler

[rcarmichael]

That solution works perfectly, thank you for taking the time to respond.

- Ryan

[itsjewel]

Isn't this a bug? Why should I annotate every parameters just to get a readable name? Is there any better workaround for this, so that Java parameters name directly got reflected to the generated wsdl without using @WebParam ?

[joshua.dev]

Sun's reference implementation for JAX-WS behaves identically so it's not a bug of JBossWS. It's inconvenient however and against the principle of sensible defaults, like for example @WebService taking the annotated interface (or class) name as the service name.

[dlofthouse]

"itsjewel" wrote:
Isn't this a bug?

This was a problem with Java 5 and before, the names assigned to parameters were not retained in the resulting .class files when you compile the class - this means at deployment time it is not possible to obtain the parameter name using reflection.

The @WebParam annotation is a workaround to get this information into the compiled .class file.