You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by kpalania <kp...@yahoo.com> on 2008/10/01 23:02:13 UTC
@WebParam does not seem to change the name of the parameter
Just so that theWSDL has more specific parameter names as opposed to arg0,
arg1, etc, I added the "@WebParam" annotation to my interface but that
doesn't seem to make any difference for my web services deployed in JBoss.
Note that the WSDL is auto-generated. My API spec looks like this -
public void doSomething(@WebParam(name="message")String msg);
Any thoughts?
--
View this message in context: http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19768253.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: @WebParam does not seem to change the name of the parameter
Posted by Benson Margulies <bi...@gmail.com>.
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html?
If you're not configuring with Spring, I can send you a better pointer.
On Wed, Oct 1, 2008 at 6:47 PM, kpalania <kp...@yahoo.com> wrote:
>
>
> Benson Margulies-4 wrote:
> >
> > Could I interest you in either using the JAX-WS front end or the Aegis
> > data
> > binding? I'm not saying that the current behavior is correct, just that I
> > have reason to suspect that (in particular) using JAX-WS would do what
> you
> > want for a minimum of fuss.
> >
>
> Sure why not! Any quick pointers?
> --
> View this message in context:
> http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19770630.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
Re: @WebParam does not seem to change the name of the parameter
Posted by kpalania <kp...@yahoo.com>.
Benson Margulies-4 wrote:
>
> Could I interest you in either using the JAX-WS front end or the Aegis
> data
> binding? I'm not saying that the current behavior is correct, just that I
> have reason to suspect that (in particular) using JAX-WS would do what you
> want for a minimum of fuss.
>
Sure why not! Any quick pointers?
--
View this message in context: http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19770630.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: @WebParam does not seem to change the name of the parameter
Posted by Benson Margulies <bi...@gmail.com>.
Could I interest you in either using the JAX-WS front end or the Aegis data
binding? I'm not saying that the current behavior is correct, just that I
have reason to suspect that (in particular) using JAX-WS would do what you
want for a minimum of fuss.
On Wed, Oct 1, 2008 at 6:11 PM, kpalania <kp...@yahoo.com> wrote:
>
>
> Benson Margulies-4 wrote:
> >
> > What front-end? What data binding? What version of CXF ......
> >
> > What rough beast ...
> >
>
> Version 2.1.2 deployed in JBoss 4.0.5. Default JAXB data binding and
> Simple
> Front-End.
>
> http://cwiki.apache.org/CXF20DOC/simple-frontend.html
> --
> View this message in context:
> http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19770185.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
Re: @WebParam does not seem to change the name of the parameter
Posted by kpalania <kp...@yahoo.com>.
Benson Margulies-4 wrote:
>
> What front-end? What data binding? What version of CXF ......
>
> What rough beast ...
>
Version 2.1.2 deployed in JBoss 4.0.5. Default JAXB data binding and Simple
Front-End.
http://cwiki.apache.org/CXF20DOC/simple-frontend.html
--
View this message in context: http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19770185.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: @WebParam does not seem to change the name of the parameter
Posted by Benson Margulies <bi...@gmail.com>.
What front-end? What data binding? What version of CXF ......
What rough beast ...
On Wed, Oct 1, 2008 at 5:02 PM, kpalania <kp...@yahoo.com> wrote:
>
> Just so that theWSDL has more specific parameter names as opposed to arg0,
> arg1, etc, I added the "@WebParam" annotation to my interface but that
> doesn't seem to make any difference for my web services deployed in JBoss.
> Note that the WSDL is auto-generated. My API spec looks like this -
>
> public void doSomething(@WebParam(name="message")String msg);
>
> Any thoughts?
> --
> View this message in context:
> http://www.nabble.com/%40WebParam-does-not-seem-to-change-the-name-of-the-parameter-tp19768253p19768253.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>