Arun Gupta wrote:
>>> Think we are talking about syntax like this:
>>> /@BindingType({"http://schemas.xmlsoap.org/soap/http",
>>> "http://schemas.xmlsoap.org/soap/tcp"})/
>>> correct?
>>>
>> No. What arun is talking about is BindingType.featuers(String[])
>> which is different from BindingType(String[]). In the latter case its
>> binding ids.
> Yep, we discussed to use BindingType.features(String[]). In
> retrospect, BindingType should have been designed to take multiple ids
> but for backwards compatibility this cannot be changed.
But doesnt BindingType.features suppose to have some wider purpose of
use, not just like list of additional BindingIDs? In this case not all
listed BindingType.features could be treated as BindingIDs... How JAXWS
will distinct them?
Arun, where in wsit BindingType.features will be used, just interesting
to see what actual are usecases for it?
Thanks.
Alexey.
>>> As Arun said, wsit will move to jaxws 2.1, then probably it make
>>> sense to stick with @BindingType implementation and dont use any
>>> policy assertion for SOAP/TCP,
>> The timeline I am talking about only in JAXWS 2.1, no changes are
>> being planned in jaxws 2.0.1.
> Yes, this is *only* in JAX-WS 2.1.
>
> -Arun
>
>