cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Properties Overriding in WSDL usage
Date Mon, 06 Jul 2009 14:30:50 GMT
On Mon July 6 2009 3:02:00 am Willem Jiang wrote:
> Hi,
>
> I think this is a bug of CXF, if the user define the extension in the
> service and binding,
>  we should use the service's value.

Agreed.   Good catch.

Dan


>
> Willem
>
> liucong wrote:
> > Hi all,
> >
> > In the
> > SOAP/JMS(http://www.w3.org/TR/2008/WD-soapjms-20081121/#wsdl-11-propertie
> >s). If a property is specified at multiple levels, the most specific
> > setting will take precedence (port first, then service, then binding).
> >
> > But I invetigate the code of CXF. I find someting int
> > org.apache.cxf.service.model.EndpointInfo.getTraversedExtensor(T
> > defaultValue, Class<T> type):
> > @Override
> > public <T> T getTraversedExtensor(T defaultValue, Class<T> type) {
> > T value = getExtensor(type);
> >
> > if (value == null) {
> > if (value == null && binding != null) {
> > value = binding.getExtensor(type);
> > }
> >
> > if (service != null && value == null) {
> > value = service.getExtensor(type);
> > }
> >
> > if (value == null) {
> > value = defaultValue;
> > }
> > }
> >
> > return value;
> > }
> >
> > The code shou that:port first, then binding, then service.
> >
> > Now. Which is right?
> >
> > thanks.

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

Mime
View raw message