RFR: 8076549: Update JAX-WS RI integration to latest version (2.2.11-b150402.1412)

[Aleksej Efimov]

Hi Joe,

Yes, the extensive testing took place before syncing the standalone 
implementation to JDK: JCK, sets of jaxws/b unit tests, JPRT testing.

Thank you for your comments and suggestions - we'll try to address them 
and integrate during the next integration. About diamond operator in 
MIMEMessage - not sure that we can put it there - AFAIK the standalone 
JAXWS/B still supports JDK6 and we can't use "diamonds" there.

With Best Regards,
Aleksej

On 04/10/2015 09:50 AM, huizhe wang wrote:
> Hi Aleksej,
>
> I assume the JAX-WS/JAXB standalone releases are well tested for this 
> integration, esp. the service finder code.
>
> I see a great number of "<>" to "<>" changes that was suggested 
> by Alan in the last integration. Besides that, you may consider 
> removing </p>, using {@literal @} to replace &#64, and the diamond 
> operator in new expression in MIMEMessage.  Also, new 
> StringBuilder().append("META-INF/services/").append(jaxbContextFQCN).toString() 
> isn't any better than "META-INF/services/"+jaxbContextFQCN since 
> they'll be compiled into the same.
>
> None of the above should prevent you from pushing your changes.
>
> Cheers,
> Joe
>
> On 4/8/2015 1:57 PM, Aleksej Efimov wrote:
>> Hi,
>> Can I kindly ask for a review of this JAX-WS update?
>>
>> With Best Regards,
>> Aleksej
>>
>> On 04/03/2015 06:20 PM, Aleksej Efimov wrote:
>>> Hello,
>>>
>>> Can I have a review for a JDK9 bulk update of JAX-B/WS from upstream 
>>> projects.
>>> Webrev:
>>> More details in issue description: 
>>> https://bugs.openjdk.java.net/browse/JDK-8076549
>>>
>>> Thank you,
>>> Aleksej
>>
>