You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Sergey Beryozkin <sb...@gmail.com> on 2010/11/16 19:53:20 UTC

Changing WSDLEndpointFactory interface

Hi

I've been working on a CXF JAX-RS demo recently and after being forced to
add a wsdl4j dependency to a basic JAX-RS server I decided to give it a go
and
fix CXF-3021 [1].

The 'fix' is to remove a javax.wsdl.Port reference from WSDLEndpointFactory
interface and replace with a list given that the current CXF implementations
simply use it to get to the list of extensors.

While changing the interface is generally not something we can do IMHO in
this particular case it is warranted given that the http transport depends
on wsdl4j and also it is probably unlikely anyone uses a CXF
WSDLEndpointFactory directly. Just CC-ing to users to verify this claim.

Comments ?
Sergey

[1] https://issues.apache.org/jira/browse/CXF-3021

Fwd: Changing WSDLEndpointFactory interface

Posted by Sergey Beryozkin <sb...@gmail.com>.
Just FYI...

---------- Forwarded message ----------
From: Sergey Beryozkin <sb...@gmail.com>
Date: Tue, Nov 16, 2010 at 6:53 PM
Subject: Changing WSDLEndpointFactory interface
To: dev@cxf.apache.org


Hi

I've been working on a CXF JAX-RS demo recently and after being forced to
add a wsdl4j dependency to a basic JAX-RS server I decided to give it a go
and
fix CXF-3021 [1].

The 'fix' is to remove a javax.wsdl.Port reference from WSDLEndpointFactory
interface and replace with a list given that the current CXF implementations
simply use it to get to the list of extensors.

While changing the interface is generally not something we can do IMHO in
this particular case it is warranted given that the http transport depends
on wsdl4j and also it is probably unlikely anyone uses a CXF
WSDLEndpointFactory directly. Just CC-ing to users to verify this claim.

Comments ?
Sergey

[1] https://issues.apache.org/jira/browse/CXF-3021

Re: Changing WSDLEndpointFactory interface

Posted by Daniel Kulp <dk...@apache.org>.
This more or less makes sense, but likely for 2.4 only as it does change a 
method signature that someone MAY be using for a custom transport.  It would 
need to be noted in a migration guide.

Dan


On Tuesday 16 November 2010 1:53:20 pm Sergey Beryozkin wrote:
> Hi
> 
> I've been working on a CXF JAX-RS demo recently and after being forced to
> add a wsdl4j dependency to a basic JAX-RS server I decided to give it a go
> and
> fix CXF-3021 [1].
> 
> The 'fix' is to remove a javax.wsdl.Port reference from WSDLEndpointFactory
> interface and replace with a list given that the current CXF
> implementations simply use it to get to the list of extensors.
> 
> While changing the interface is generally not something we can do IMHO in
> this particular case it is warranted given that the http transport depends
> on wsdl4j and also it is probably unlikely anyone uses a CXF
> WSDLEndpointFactory directly. Just CC-ing to users to verify this claim.
> 
> Comments ?
> Sergey
> 
> [1] https://issues.apache.org/jira/browse/CXF-3021

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