[jboss-user] [JBossWS] - Re: @WebService method argument names

2008-04-23 Thread 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 ? View the original post :

[jboss-user] [JBossWS] - Re: @WebService method argument names

2008-04-23 Thread 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. View the original post :

[jboss-user] [JBossWS] - Re: @WebService method argument names

2008-04-23 Thread [EMAIL PROTECTED]
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

[jboss-user] [JBossWS] - Re: @WebService method argument names

2008-03-06 Thread 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 View the original post :

[jboss-user] [JBossWS] - Re: @WebService method argument names

2008-03-06 Thread rcarmichael
That solution works perfectly, thank you for taking the time to respond. - Ryan View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4134559#4134559 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4134559