dev@jax-ws.java.net

Re: Features added to WSDL port.binding

From: Rama Pulavarthi <Rama.Pulavarthi_at_Sun.COM>
Date: Fri, 03 Nov 2006 09:04:15 -0800

Hi Paul,
I just looked at the code and it looks fine to me.
Features can be specified on WSDLPort, WSDLBoundPortType (
port.getBinding()). Features from WSDLBoundPortType will be copied to
WSDLPort during freeze.
When you do port.getBinding().addFeature( ), this feature will be added
to port during freeze() of the WSDLModel.
As Fabian suggested, If the WSDLModel is not frozen, you need to query
on the same entity where it is set.

Wherever you set in the WSDLModel, it ultimately goes in to binding
(WSBinding).
But as per you email, when you do port.addFeature(), if it is not
propagated to WSBinding, then it is a issue. Let me know if this is the
case.

thanks,
Rama Pulavarthi

Paul Sandoz wrote:
> Hi,
>
> Something subtle has changed recently that stopped the
> FastInfosetFeature being propagated from the WSDL port binding to the
> JAX-WS binding.
>
> I modified the FastInfosetModelConfiguratorProvider to:
>
> port.addFeature(new FastInfosetFeature(isFastInfosetEnabled));
>
> (like addressing) instead of:
>
> port.getBinding().addFeature(
> new FastInfosetFeature(isFastInfosetEnabled));
>
> and the feature then gets propagated to the ones that are merged and
> passed to the binding.
>
> The some problem will occur with MTOM as well.
>
> Paul.
>