Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Date: Wed, 30 Mar 2005 23:52:37 +0100
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: Too many jar files
In-reply-to: <424B0C70.5050708@Golux.Com>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <424B2DB5.9010308@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
 Gecko/20040113
References: <424AA4E5.2090003@sun.com> <424AB3F9.5040901@Golux.Com>
 <424AD2AE.5050706@sun.com> <424B0C70.5050708@Golux.Com>

OK, I thought that may be the case.  I didn't mention it because I 
thought we were worried about memory footprint, not on-disk footprint, 
but I guess in smaller devices both are important.

Do we have any clear requirements about the maximum footprint of Derby?  
What are the other constraints we should be aware of so we don't cause 
problems for the small device target of Derby?  How strict are these 
constraints -- will features/fixes that have a big impact on the overall 
footprint of Derby generally be vetoed?  I guess this is one of the 
motivations for the highly modular architecture and the ability to load 
only specific modules at runtime...

Thanks,

David

myrna wrote:

> David Van Couvering wrote:
>
>> 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
>
>
> Ah, now I see what you're saying - just lob all locale files (they're 
> not classes) together into 1 jar. I am not sure about this, but I 
> would think that it was done to minimize footprint/size of jar - if 
> you know you'll be working in Italian only you wouldn't care about 
> having any other locale files sitting around.
>
> But maybe someone else can explain for sure.
>
> Myrna
>
>