Re: [jboss-as7-dev] manual way to do logging?
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:
>>
>> On 6/6/12 2:11 PM, David M. Lloyd wrote:
>>> On 06/06/2012 12:35 PM, Bill Burke wrote:
>>>> I do not want to use the JBoss Logging annotation framework as I do not
>>>> want to have a hard dependency on JBoss Logging for my project.
>>>>
>>>> Is there a manual API that I can use instead to build a message?
>>>> Something like:
>>>>
>>>> String getMessage(long id, Object... params);
>>> No, there isn't (and if there were, it'd be part of JBoss Logging,
>>> so...). You can however use the maven-shade-plugin to slurp the JBoss
>>> Logging classes into your project (even under another package name).
>>> It's a pretty small project and we're working to make it smaller.
>>>
>> Eh, I guess I could just use reflection techniques to create my own
>> abstraction and stuff the logging interfaces in a separate jar.
>>
>> BTW, this is ridiculously over-engineered and at least for me, harder to
>> adapt to my project. These engineering hours could have been better
>> spent elsewhere.
> 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).
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat