Rama Pulavarthi wrote:
> 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.
OK, when does the freeze occur, after the JAX-WS binding has been
created? i.e. after the codec has been created?
> 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.
>
When i add to the WSDL port it does get propagated. I just was not aware
of the freeze semantics.
Paul.
> 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.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109