[jboss-as7-dev] manual way to do logging?

Jason T. Greene jason.greene at redhat.com
Wed Jun 6 16:39:06 EDT 2012


On 6/6/12 3:33 PM, David M. Lloyd wrote:
> On 06/06/2012 02:27 PM, Bill Burke wrote:
>>
>>
>> On 6/6/12 3:19 PM, David M. Lloyd wrote:
>>> Up to you, but you get to be the one to tell the translation team
>>
>> I'll just forward those emails onto you.
>>
>>> why
>>> they have to key all their messages off of an integer ID instead of a
>>> descriptive name. And you also get to reinvent the tooling which
>>> provides them with the English translation to work from.
>>
>> You mean all this crap isn't built on top of simple property files? (At
>> least thats what I saw in the jboss-logging-processor testsuite)
>
> It is.  Our tooling generates the property file skeletons.  Then the
> translation team translates them, and then the tooling compiles them
> down to classes.
>
>>> Doesn't sound
>>> like a good use of time to me.
>>>
>>
>> I agree. Which is why this is at the very bottom of my queue now because
>> you guys had to over-engineer this.
>
> We have these things called "requirements" which we met exactly afaict.
>    This is the exact opposite of "over-engineering", which is, by
> definition, adding in un-required features.  The jboss-logging API is
> minimal; the i18n solution exactly implements the requirements.
>

Ironically adding an abstraction layer over an abstraction layer doesnt 
seem to have a requirement associated with it.....

-- 
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat


More information about the jboss-as7-dev mailing list