cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <>
Subject Re: How to handle a configuration problem generally in CXF code
Date Tue, 07 Oct 2008 21:41:18 GMT

Yes, it was good that James Mao created a CXF-zh list, with so many Chinese
committers, developing a Chinese language CXF community was a huge bonus for
us that the other web service stacks didn't have.  Doing Google blog
searches, we do seem to lag in Japan though because the Axis 1.x web site is
translated into Japanese.


dkulp wrote:
> I'd definitely prefer if the excpetion was on of the I18N things.   A 
> LARGE chunk of our users are actually from China.  According to google 
> analytics, China is #2 after the US.   It's definitely important to keep 
> the option open to make this stuff localizable.  ESPECIALLY for 
> configuration things where a non-developer might need to make changes.  
> More "admin" like tasks.   
> Note: if you have a Logger, you already have the bundle.   The i18n 
> message can take the Logger instead of the bundle.
> Dan
> On Monday 06 October 2008, Christian Schneider wrote:
>> Hi all,
>> when there is a problem with the configuration i currently throw a
>> simple RuntimeException. I think this can be handled better.
>> I have found a class ConfigurationException but it only accepts a
>> message as i18 Message. Should this class be used? I do not like that
>> much that it always needs a resource definition.
>> Is internationalization for config errors that usefull? Whenever I got
>> a german exception I had much problems trying to google for it. So I
>> personally like english exceptions.
>> Another possibility would be to throw an AssertionError. As it is for
>> example an assertion that a certain property is not null.
>> Any ideas?
>> Greetings
>> Christian
> -- 
> J. Daniel Kulp

View this message in context:
Sent from the cxf-dev mailing list archive at

View raw message