cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Properties Overriding in WSDL usage
Date Mon, 06 Jul 2009 07:02:00 GMT
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.

Willem

liucong wrote:
> Hi all,
> 
> In the
> SOAP/JMS(http://www.w3.org/TR/2008/WD-soapjms-20081121/#wsdl-11-properties).
> 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.
> 


Mime
View raw message