Paul Sandoz wrote:
> Something subtle has changed recently that stopped the
> FastInfosetFeature being propagated from the WSDL port binding to the
> JAX-WS binding.
I thought so as well, because our unit tests had started to fail, but
that likely was a failure in our tests rather than JAX-WS. With earlier
versions of JAX-WS, the tests had not failed. Originally, the tests had
created a feature on the port and then queried the binding and
apparently that worked with older versions of JAX-WS. Now, you have to
read the feature from the same entity that it had been attached to.
> 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.
Did you change our unit test as well?
BTW, I noticed you have one more web service feature
(OptimizedSomething) but no ModelConfigProvider for it?
> The some problem will occur with MTOM as well.
I'm not sure what behavior is invalid, the previous one or what we have now?
Fabian
--
Fabian Ritzmann
Sun Microsystems, Inc.
Stella Business Park Phone +358-9-525 562 96
Lars Sonckin kaari 12 Fax +358-9-525 562 52
02600 Espoo Email Fabian.Ritzmann_at_Sun.COM
Finland