cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse (JIRA)" <>
Subject [jira] Closed: (CXF-115) org.apache.cxf.jaxws.EndpointImpl needs additional constructors
Date Wed, 11 Oct 2006 23:04:36 GMT
     [ ]

Dan Diephouse closed CXF-115.

    Fix Version/s: 2.0-M1
       Resolution: Fixed

I added a patch for this to SVN. To use it do something like so:

 GreeterImpl greeter = new GreeterImpl();
        JaxWsServiceFactoryBean serviceFactory = new JaxWsServiceFactoryBean();
        serviceFactory.setInvoker(new BeanInvoker(greeter));
        EndpointImpl endpoint = new EndpointImpl(getBus(), greeter, serviceFactory);

It passes the servicefactory as we need to get information from it inside EndpointImpl.

> org.apache.cxf.jaxws.EndpointImpl needs additional constructors
> ---------------------------------------------------------------
>                 Key: CXF-115
>                 URL:
>             Project: CeltiXfire
>          Issue Type: Improvement
>          Components: JAX-WS Runtime
>            Reporter: Seumas Soltysik
>             Fix For: 2.0-M1
> Currently Endpoint impl has the following constructor:
>   public EndpointImpl(Bus b, Object implementor, String uri) 
> This constructor extracts annotation information from the implementor object in order
to create the Endpoint. However, if a user wants to over-ride one of the annotation values
such as the wsdlLocation value they cannot do this. This situation happens when a implementation
is code generated and then the location of the wsdl changes. This could happen if you are
packaging up a endpoint along with a wsdl for deployment into a container.
> I think what is needed is a more flexible constructor that looks something like this:
> public EndpointImpl(Bus b, Object implementor, Service s, String portname)
> This way a user is free to contruct their own Service from a wsdl not specified by the
WSDL location. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message