The JAX-WS in JDK 9 is going to be 2.3.0 [1].  java.xml.ws is not resolved by 
default.  JAX-WS 2.1 API can only be loaded to the runtime from class path if 
java.xml.ws is not resolved.  The JAX-WS runtime in JDK 9 will not be loaded in 
this case.  If this message is specific for this scenario, this message is okay 
to keep it and would be good to add a comment saying “this message should not 
be loaded from JDK 9 runtime"

Roman has to confirm whether this message will not be used when running in JDK 
9.

Mandy
[1] http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-May/047426.html


> On May 3, 2017, at 7:24 PM, Leo Jiang <li.ji...@oracle.com> wrote:
> 
> ===  Copy from David's email
> That endorsed part is problem. It is valid in JDK-8 but not in 9. Following 
> message is my proposed solution. It would fit JDK-8 and 9.
> JAX-WS 2.1 API is loaded from {0}, But JAX-WS runtime requires JAX-WS 2.2 
> API. Use the standard override mechanism to load JAX-WS 2.2 API
> 
> Do you think that this solution is OK?
> ===
> 
> Thanks,
> Leo
> 
> 
> On 05/04/2017 05:14 AM, Mandy Chung wrote:
>> 
>>> On May 3, 2017, at 1:35 PM, Alan Bateman <alan.bate...@oracle.com> wrote:
>>> 
>>> On 03/05/2017 19:58, Lance Andersen wrote:
>>> 
>>>> +
>>>> +runtime.modeler.addressing.responses.nosuchmethod = JAX-WS 2.1 API is 
>>>> loaded from {0}, But JAX-WS runtime requires JAX-WS 2.2 or newer API. \
>>>> +  Use the standard override mechanism to load JAX-WS 2.2 or newer API.
>>>> \ No newline at end of file
>>>> 
>>> "Use the standard override mechanism". I wonder if this meant to say the 
>>> "endorsed standards override mechanism". In any case, it feels like a 
>>> message for when JAX-WS is running on an older release. Do you know if that 
>>> is true?
>>> 
>> 
>> Since this resource bundle is for JDK 9, it should say “upgradeable module 
>> path” instead. But is this message intended for older release and is it ever 
>> used for JDK 9?
>> 
>> Mandy
>> 

Reply via email to