On 6/6/12 3:43 PM, Andrig Miller wrote:
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.
Right I think we need to know why it needs to be abstracted. What is
missing from jboss logging that requires RESTEasy to have an
abstraction? Once we know the answer to that question, we can either add
whatever the missing thing is, or recommend how to go about building
something custom with similar perf characteristics (if the advice is
even wanted).
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat