Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: dev@cxf.apache.org
Subject: Re: Properties Overriding in WSDL usage
Date: Mon, 6 Jul 2009 10:30:50 -0400
User-Agent: KMail/1.11.4 (Linux/2.6.30-gentoo-r1; KDE/4.2.4; x86_64; ; )
Cc: Willem Jiang <willem.jiang@gmail.com>
References: <4A4E2AD4.4080800@gmail.com> <4A51A168.6080700@gmail.com>
In-Reply-To: <4A51A168.6080700@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907061030.50414.dkulp@apache.org>

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