Reminder: i18n strawman

Glyn Normington glyn_normington at UK.IBM.COM
Tue May 15 06:53:03 PDT 2007


The ResourceBundle API does not only use resource (*.properties) lookups.
It also attempts class loads to find resource bundles, effectively needing
to load classes from a split package.

Glyn

Michal Cierniak <cierniak at GOOGLE.COM> wrote on 15/05/2007 00:36:51:

> I think that it's reasonable if we decide that the only way that split
> packages may manifest themselves is as resources via the
> ResourceBundle API.  I was worried about code for the same package
> coming from multiple modules but it seems that you're not suggesting
> this.
>
> Thanks!
> Michal
>
> On 5/14/07, Stanley M. Ho <Stanley.Ho at sun.com> wrote:
> > Hi Michal,
> >
> > Yes, the i18n strawman currently assumes that the class-based resource
> > bundles in multiple modules are in the same Java package (but each
with
> > different superpackage membership), and this is consistent with the
> > existing practice in using the java.util.ResourceBundle API.
> >
> > Based on the earlier EG discussions, we have agreed to explicitly
> > disallow split packages during shallow validation so developers are
not
> > encouraged to use them and we don't have to deal with all the issues
> > that split packages may cause. However, the existing i18n practice
> > somewhat contradicts what we encourage developers to do.
> >
> > That said, this may not be a big problem after all, since split
packages
> > would still be disallowed during module initialization. This also
> > implies that a target module can't import resource modules directly
and
> > must rely on the ResourceBundle API to look up resources, and
personally
> > I think this is acceptable (if other EG members have different
opinions,
> > I would like to hear them). Therefore, we could still discourage split
> > packages in general and only let developers use them in this special
case.
> >
> > The obvious alternative is to require class-based resource bundles in
> > multiple modules to be in different Java packages. Unfortunately, this
> > is incompatible with the existing practice in translating resource
> > bundles, and I'm concerned that this would hurt adoption.
> >
> > What do you think?
> >
> > - Stanley
> >
> >
> > Michal Cierniak wrote:
> > > Stanley,
> > >
> > > It is not clear to me from the doc if i8n relies on the assumption
> > > that a package may be split across multiple modules.  Can you
clarify?
> > >
> > > Thanks,
> > > Michal
> >






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/jsr277-eg-observer/attachments/20070515/a54896ca/attachment.html 


More information about the jsr277-eg-observer mailing list