It would be good to know the uses cases, such as do we know what
endpoints publish their endpoint wsdls using EPR? Are epr endpoints are
itended to be used at runtime?
My other comments regarding the proposal are inlined below...
Arun Gupta wrote:
>> Nope. I'm just asking the team about it. When we talked a little
>> about it on the wsit email list, I think we thought the best way
>> would be to not add a switch, but simply let the file argument that
>> wsimport already takes be an epr.
>>
>> For instance, allow these:
>> wsimport <other options> service.wsdl
>> wsimport <other options> epr.xml
For this proposal +1.
> I like this approach as well as opposed to the one mentioned below.
> wsimport should be able to identify the format of the file and
> generate the artifacts based upon the embedded WSDL metadata in the
> passed EPR.
>
> Do you plan to support remote EPRs as well, such as:
>
whether EPR is fetched as local or remote it would not really matter if
the wsimport runtime known how to distinguish epr resource form a wsdl.
Assuming that it can be safely distinguished and considering an epr
endpoint would anyway send epr resource, I guess there is no need to
identify epr resource explicitly as a remote resource, such as with '?epr'.
-vivek.
> wsimport <other options> http://localhost:8080/addnumbers?epr
>
> Do you plan to make use of the service/port in the EPR in any manner ?
>
> -Arun
>
>>
>> Instead of this:
>> wsimport <other options> -epr epr.xml
>>
>> Of course, that's up to the jax-ws team, but I think that'd be best.
>>
>> Cheers,
>> Bobby
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
>> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>>
>