>>> Are you proposing using BindingType.fearures to enable TCP transport?
>>> Such as we use normal binding id for lets says soap11/http and in
>>> features we have TCP transport?
I'm just restating what was discussed at one point of time :)
>> 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.
>> 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
--
Web Technologies and Standards
Sun Microsystems, Inc.
Blog: http://blogs.sun.com/arungupta