Alexey,
> BindingType annotation was original and probably preffered way we wanted
> to use, but were concenred that it could have just 1 binding
> description. (just tcp, just http... and what if we need other
> transports?), thats why then we decided to use policy to say that this
> BindingType is also tcp enabled. Solution with policies looked more
> scalable, as similar way we can support enableSMTP... enableWhatever and
> dont depend on any existed binding.
> Also seems Jitu mentioned that there is some spec proposal to use this
> annotation BindingType with String[]... probably that is solution we
> really need, but meanwhile have to have some "temporary"?
I've already added a basic implementation for BindingType features (type
String[]) in JAX-WS 2.1 branch. That is how WS-A support is enabled
starting from Java anyway.
So how long will this "temporary" solution need to exist ? I agree there
is a dependency on JAX-WS 2.1 integration in WSIT but I plan to do that
either this week or sometime next week.
What will be the migration path from this "temporary" to a "proper"
solution ?
-Arun
>
> So as conclusion i think BindingType annotation is natural solution we
> need to use (natural when it will support String[] of bindings), but
> currently we can use either BindingType annotation with some tricky URIs
> to say whether its tcp, http or both, or put that info to policies
> (wsit.xml).
>
> WBR,
> Alexey.
>
>>>
>>>>> I tend to agree with the overall approach, we just need to refine
>>>>> the syntax.
>>>>>
>>>> Yes. Basically we need 3 bindings ids, one for soap11+http+tcp,
>>>> another for soap 12+http+tcp and the last one thats only soap over tcp.
>>> I think we'll need 4:
>>>
>>> SOAP 1.1/HTTP + SOAP1.1/TCP
>>> SOAP 1.2/HTTP + SOAP1.1/TCP
>>> SOAP1.1/TCP
>>> SOAP1.2/TCP
>>>
>> yep.
>>
>> -vivek.
>>> -Arun
>>>
>>>>
>>>> -vivek.
>>>>> -Arun
>>>>>
>>>>>>
>>>>>> -vivek.
>>>>>> [1]https://jax-ws.dev.java.net/issues/show_bug.cgi?id=40
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_wsit.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_wsit.dev.java.net
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_wsit.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_wsit.dev.java.net
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_wsit.dev.java.net
>> For additional commands, e-mail: dev-help_at_wsit.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_wsit.dev.java.net
> For additional commands, e-mail: dev-help_at_wsit.dev.java.net
>
--
Web Technologies and Standards
Sun Microsystems, Inc.
Blog: http://blogs.sun.com/arungupta