Hi Mandy,
Looks good to me.
Best Regards,
Aleksej
On 25/05/16 22:48, Mandy Chung wrote:
On May 25, 2016, at 12:45 PM, Alan Bateman wrote:
On 25/05/2016 20:29, Mandy Chung wrote:
wsgen and wsimport tools use the utility classes in java.xml.bind module to
localize messages. Resource bundles
> On May 25, 2016, at 12:45 PM, Alan Bateman wrote:
>
> On 25/05/2016 20:29, Mandy Chung wrote:
>> wsgen and wsimport tools use the utility classes in java.xml.bind module to
>> localize messages. Resource bundles are encapsulated in named modules and
>> hence utility like
>> com.sun.istack.
I looked at this also and do not see anything glaring.
> On May 25, 2016, at 3:45 PM, Alan Bateman wrote:
>
> On 25/05/2016 20:29, Mandy Chung wrote:
>> wsgen and wsimport tools use the utility classes in java.xml.bind module to
>> localize messages. Resource bundles are encapsulated in named m
On 25/05/2016 20:29, Mandy Chung wrote:
wsgen and wsimport tools use the utility classes in java.xml.bind module to
localize messages. Resource bundles are encapsulated in named modules and
hence utility like
com.sun.istack.internal.localization.LocalizableMessageFactory.
The owner of the r
wsgen and wsimport tools use the utility classes in java.xml.bind module to
localize messages. Resource bundles are encapsulated in named modules and
hence utility like
com.sun.istack.internal.localization.LocalizableMessageFactory.
The owner of the resource bundle should be the one loading R