Re: [jboss-as7-dev] manual way to do logging?
----- Original Message -----
From: "Jason T. Greene" <jason.greene(a)redhat.com>
To: "Bill Burke" <bburke(a)redhat.com>
Cc: "JBoss AS7 Development" <jboss-as7-dev(a)lists.jboss.org>
Sent: Wednesday, June 6, 2012 2:17:03 PM
Subject: Re: [jboss-as7-dev] manual way to do logging?
On 6/6/12 2: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)
>
>> 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.
Right its not like you had any opportunity during the TAG discussions
to
disagree with any particular discussion. Or that you got to see
people
saying they disliked the first API which looked similar to what you
just
pasted here because of duplication of messages, like of type safety,
lack of message in the java source, performance problems etc. Oh wait
you did!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
I'm not sure we have to have these discussions over and over and over again. From my
perspective, performance being my primary concern, JBoss logging has been awesome, and it
meets all the companies requirements. I haven't been able to put an exact percentage
on it yet, but the use of JBoss logging has improved throughput on all the workloads I
have tested, that is for sure.
If we continue to pollute the code base with different logging frameworks, a lot of those
gains could start to disappear. Besides the fact, that we are about to ship a product in
multiple languages for the first time, and we have to continue to finish the work we
started.
Is is all that difficult to adopt JBoss logging? This all seems counter productive.
Andy