On 06/06/2012 12:06 PM, Jason T. Greene wrote:
On 6/6/12 1:56 PM, James Perkins wrote:
>
>
> On 06/06/2012 11:37 AM, Jason T. Greene wrote:
>> On 6/6/12 1:32 PM, Bill Burke wrote: You don't have to use it. You
>> just need a message format that meets
>> TAG-2. Everything the framework does, is meets the TAG-3 requirements
>> (discussed ad nauseam years ago).
>>
> This was all done before I started so I could be wrong, but I think
> JBoss Logging is supposed to be used.
>
https://issues.jboss.org/browse/ANDIAMO-2
It the preferred option, but we anticipated the impossibility of
making everyone happy, so the official decision was that you could use
something different provided you met the same requirements. Weld for
example went this route (although we did share tools code IIRC)
because of licensing requirements. We are changing the license to ASL
which should solve that particular problem.
One of the challenges in doing i8ln is making it scale, and keeping
the english description in source. so thats why jboss logging
precompiles (no resource bundle lookup on every invocation). So while
you roll your own, you have to solve these same issues.
Anything in the AS codebase though MUST use jboss logging (no reason
not to).
Thanks for the clarification Jason. This is good information to know.
--
James R. Perkins
JBoss by Red Hat