Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 202.81.18.155 is neither permitted nor
 denied by domain of firepure@gmail.com)
Message-ID: <44C9A631.1080404@gmail.com>
Date: Fri, 28 Jul 2006 13:52:49 +0800
From: "Jimmy, Jing Lv" <firepure@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib]strings externalization
References: <c79906b30607270353y4dfdb16bw92bc48fed76cb1c0@mail.gmail.com>
	 <44C8AE2A.8000807@gmail.com>
	 <c79906b30607270550pc6aeb1ej2a50d2ff80e80ea@mail.gmail.com>
	 <44C8BB94.5030300@gmail.com>
 <4d0b24970607271021p1804775apc9b944d3a154a6fd@mail.gmail.com>
In-Reply-To: <4d0b24970607271021p1804775apc9b944d3a154a6fd@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Andrew Zhang wrote:
> On 7/27/06, Tim Ellison <t.p.ellison@gmail.com> wrote:
>>
>> Ilya Okomin wrote:
>> > On 7/27/06, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> >> The other reason we will need some manual intervention is that 
>> there is
>> >> plenty of code that throws exceptions without any message describing
>> the
>> >> problem, and of course the tooling won't help there.
>> >
>> > Tim, do you mean, that Exceptions without any messages supposed to be
>> > initialized with some corresponding message describing the problem? I
>> > thought only already existing in modules messages are to be considered.
>> > Just want to dispel doubts.
>>
>> I see plenty of code going in to svn that simply throws a new
>> IllegalArgumentException() or whatever.  It would be good if they had an
>> externalized message to explain what the problem was -- i.e. throw new
>> IllegalArgumentException("Parameter foobar should be less than 42") etc.
> 
> 
> Agree. Meaningful message helps. But all exceptions defined in java.nio and
> java.nio.channels only have a constructor without any parameter. :)
> Seems sun is becoming lazy on this issue. :)
> 

:) Rather call them "clever" than "lazy" in my mind, as an 
IllegalArgumentException can enough detail for user to know what is 
wrong (and javadoc also offer some information). Only some exception, 
like IOException, may need more detail for its cause.

After all, now Harmony can use RI's error message, so it is no longer 
necessary to rack our brains to write error message. :)

> You might consider this a separate task to that of externalizing the
>> existing messages, but depending on how 'manual' the externalization
>> scan is for each module it may be worth doing both simultaneously.
>>
>> >> So once we have the basic framework in place for the message 
>> handling I
>> >> think it will require a large manual effort to get all the strings 
>> that
>> >> we want externalized properly.  Luckily it is not technically complex
>> >> work and it is a task that we can easily do in parallel across the
>> >> modules.
>> >
>> > Yep, I've chosen the same way to do.
>>
>>
>> Cool -- did you get anywhere with the message handling framework
>> 'template' code?
>>
>> Regards,
>> Tim
>>
>> ---------------------------------------------------------------------
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>>
>>
> 
> 


-- 

Best Regards!

Jimmy, Jing Lv
China Software Development Lab, IBM

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org