You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2010/10/11 13:59:52 UTC

JAX-WS annotations versus the client proxy factory

I read that @BindingType goes on the implementation, not the
interface. So how do I configure it on the client with a
JaxWsProxyFactoryBean?

Re: JAX-WS annotations versus the client proxy factory

Posted by Daniel Kulp <dk...@apache.org>.

On Monday 11 October 2010 8:24:18 am Andreas Veithen wrote:
> Probably you just found the answer to Daniel's question about why
> having a WSDL on the client side is mandatory...

Not really.    With "normal" JAX-WS API's, you can do something like:

Service service = Service.create(servName);
service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, 
                        "http://localhost:8080/foo");
port = service.getPort(portName,  MyPort.class);

which works fine with CXF.

For the factory, it should just be:


clientFac.setBindingId(bindingId);

but I'm not sure if the full set of JAX-WS binding ID's works there.   Don't 
remember where we do the mapping.

Dan



> 
> Andreas
> 
> On Mon, Oct 11, 2010 at 13:59, Benson Margulies <bi...@gmail.com> 
wrote:
> > I read that @BindingType goes on the implementation, not the
> > interface. So how do I configure it on the client with a
> > JaxWsProxyFactoryBean?

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Re: JAX-WS annotations versus the client proxy factory

Posted by Andreas Veithen <an...@gmail.com>.

Probably you just found the answer to Daniel's question about why
having a WSDL on the client side is mandatory...

Andreas

On Mon, Oct 11, 2010 at 13:59, Benson Margulies <bi...@gmail.com> wrote:
> I read that @BindingType goes on the implementation, not the
> interface. So how do I configure it on the client with a
> JaxWsProxyFactoryBean?
>