RFR: 8016271: wsimport -clientjar does not create portable jar on windows due to hardcoded '\'

Seán Coffey sean.coffey at oracle.com
Tue Sep 3 12:53:06 UTC 2013

First option sounds good to me too Miran. Sounds like we can expect this 
fix to be sync'ed into JDK8 from JAXWS team over next week or two then. 
Hopefully you can do the same for jdk7u-dev.


On 03/09/2013 13:32, Miroslav Kos wrote:
> Hi Sean,
> up to now, integrations JAX-WS > JDK haven't been done on regular 
> basis, just when bug fixes were required, for current JDK development 
> version it was time to time - 2x or 3x during a year (?) ...
> For future, we would like make it on regular basis for development 
> version JAX-WS trunk/Jdk8 - let's say once or twice (?) a month, for 
> other jdk version it would be same as now, only up on request ...
> How to proceed with this issue depends on how critical is it - we can 
> integrate that first on our side and later (one week delay) deliver 
> jdk patch or, if it is something critical, we can push it 
> simultaneously into both codebasis. We definitely prefer the first 
> option.
> Miran
> On 09/03/2013 12:18 PM, Seán Coffey wrote:
>> Miran,
>> can you clarify how we get this fix in then. Will you patch into 
>> JAX-WS and port to the jdk/jaxws repo or do can we push it to both 
>> repos independently? How often does JAX-WS team sync with openJDK ?
>> I need to get this ported to jdk7u also.
>> regards,
>> Sean.
>> On 03/09/2013 11:11, Miroslav Kos wrote:
>>> Hi Alan,
>>> good catch! Yes, we need to apply the fix on our side too, otherwise 
>>> it would be reverted with a new integration JAX-WS > JDK.
>>> Miran
>>> On 09/03/2013 12:03 PM, Alan Bateman wrote:
>>>> On 03/09/2013 10:49, Seán Coffey wrote:
>>>>> Bug report not public at moment. (should appear shortly)
>>>>> Issue with wsimport tool. Use of jar files created from wsimport 
>>>>> on windows don't work on unix systems. Portability issue.
>>>>> Simple fix. wsimport testcase to accompany it.
>>>>> http://cr.openjdk.java.net/~coffeys/webrev.8016271/
>>>> Does this need to go into an upstream project first?  As I 
>>>> understand it, the JAX-WS folks have an industrial blender to mix 
>>>> the ingredients for the jaxws repository. At one point then I think 
>>>> there were about 10 upstream projects to pull code from. Maybe 
>>>> things have changed but I just wonder if changes/patches pushed to 
>>>> the jaxws repository will be wiped by a re-sync from upstream. I've 
>>>> cc'ed martin Grebac and Miroslav Kos to comment.
>>>> -Alan.

More information about the core-libs-dev mailing list