Re: Too many jar files

Hi, Myrna.  I scanned through the docs you mention, but I can't find 
anything that says each locale requires its classes to be in a separate 
jar file.  It *does* talk about having lots of smaller resource bundles, 
and how you have a group of resource bundles that follow a naming 
pattern so that they are loaded based on the current locale.  But all 
these resource bundles, as far as I can see, can all go into a single 
JAR file.   Knowing what I do about Java and classloading, I can't see 
what difference it could make.  But it's more than likely I am missing 
something :)

Another data point for me is: I have worked with a lot of other 
internationalized Java products, and these folks all seem to have their 
resource bundles embedded in their main jar files, regardless of how 
many locales they support.  I also did a general Google for this topic, 
and couldn't find anything about having to have a separate jar file for 
each locale.

Can you point me to the place where it says specifically that each 
locale needs its own jar file?

Thanks!

David

myrna wrote:

> David Van Couvering wrote:
>
> > The testing instructions include having to create this long 
> > CLASSPATH, the majority of which are independent locale JAR files.  
> > These files also seem to be deliveredas independent files in the 
> > release.  Apologies for being a newbie, but is there any reason these 
> > locale jars can't be combined into a single jar?  I checked and as 
> > far as I can see all the file names are unique across all these jar 
> > files.  Is this a space concern?
> > Thanks,
> >
> > David
> Ha, it so happens I just read up on some of this stuff.
>
> There's some good info pages around, about how to do 
> internationalization, and work with the java.util.ResourceBundle class.
> See for instance:
> http://java.sun.com/developer/technicalArticles/Intl/ResourceBundles/
> http://java.sun.com/docs/books/tutorial/i18n/
>
> So, yes, those files need to remain separate.
>
> However, regarding the functionTests, most tests do *not* need the 
> localization jars.
> I'd have to confirm, but I *believe* that only the following tests 
> need the locale jars:
>     i18n/* tests (suite i18nTest)  - only need a few of the locale jars
>     sysinfo  - expected output expects all locale jars to be in the 
> classpath.
>
> We do need some more internationalization tests that run the same on 
> all platforms (windoze, linux, mac), but that's another issue.
>
> Myrna