Hello Vivek,
please, see my comments inline.
vivekp_at_dev.java.net wrote:
> https://jax-ws.dev.java.net/issues/show_bug.cgi?id=52
>
>
>
> User vivekp changed the following:
>
> What |Old value |New value
> ================================================================================
> Assigned to|issues_at_jax-ws |vivekp
> --------------------------------------------------------------------------------
> Priority|P2 |P4
> --------------------------------------------------------------------------------
> Target milestone|milestone 1 |2.1
> --------------------------------------------------------------------------------
>
>
>
>
> ------- Additional comments from vivekp_at_dev.java.net Mon Sep 18 04:37:00 +0000 2006 -------
> When wsimport is run over a WSDL with SOAP 1.2 binding it gives clear error:
>
> ---
> warning: Ignoring SOAP port "HelloPort": it uses non-standard SOAP 1.2 binding.
> You must specify the "-extension" option to use this binding.
>
> warning: Service "Hello" does not contain any usable ports
> ---
>
I am not sure I understand why this warning couldn't instead hold
following message (with respective meaning as well):
warning: SOAP port "HelloPort" uses non-standard SOAP 1.2 binding.
To remove this warning message, please specify the "-extension" option.
Seems much more user friendly to me. And since we want to attract
masses, JAX-WS is about user friendliness, isn't it.
> First of all what MS tools does is not an standard. wsimport requires this
> because it goes in mustang and java ee platform and is RI for jaxws 224 (JAXWS
> 2.0) and soap 1.2 binding for WSDL 1.1 is not a standard binding. For this
> reason wsimport requires users to use -extension.
>
Does that mean that the specification forbids implementation to consume
non-standard bindings without a switch turned on?
> One simple tip could be that you can always run wsimport in -extension mode if
> you dont care about your endpoint being incompatible/un-interoperable for such
> non-standard binding.
>
As I understand it, that is exaclty what we want to avoid. We want user
to succeed with deployment in most of the cases. How do developers
evaluate WS frameworks? A short example:
Developer has a non-standard webservice that should be deployed. He
evaluates two frameworks - JAX-WS which is strictly compliant to some
spec and some other framework X which not that strict. He tries to
deploy the service. JAx-WS deplyment fails. The deployment on the
framework X works just fine (maybe except for a minor warning message).
What does the developer care about more? About some strict
spec-compliance or about the ease-of-use experience? I am sure latter is
the more important of the two.
That leads me to a question I keep asking me more and more often: Who
are we really trying to please: JAX-WS developer or JAX-WS user?
> Since this ENHANCEMENT is not about some missing feature rather a change in
> default behaviour which is serious issue from jaxws perspective, I am lowering
> the priority to P4. We will consider your concern any may be after considering
> the compatibility impacts we will decide whether to change this behaviour of
> wsimport.
>
It would be nice to have a deadline set for the decision making.
Otherwise I could again ask myself my last question.
Thanks.
Marek
--
Marek Potociar
Web Technologies & Standards
Sun Microsystems Czech