e what I needed to see to solve
my problem. Very useful, and not in the general JBoss documentation, as far as
I could see.
-Original Message-
From: Apache [mailto:[email protected]]
Sent: Monday, January 16, 2017 2:16 PM
To: Log4J Users List
Subject: Re: jboss-loggin
> worked without incident, disproving my theory.
>
> Ugh, now to figure out how to debug java.lang.NoClassDefFoundError.
>
>
>
> -Original Message-
> From: Apache [mailto:[email protected]]
> Sent: Monday, January 16, 2017 10:43 AM
> To: Log4J Users Lis
java.lang.NoClassDefFoundError.
-Original Message-
From: Apache [mailto:[email protected]]
Sent: Monday, January 16, 2017 10:43 AM
To: Log4J Users List
Subject: Re: jboss-logging vs log4j2 in ejb-client application
Can you provide a test application along with a link to the JBoss
Can you provide a test application along with a link to the JBoss version you
are using? I haven’t worked with JBoss in several years but would happy to
take a look - if for no other reason than to do something with LOG4J2-18.
Ralph
> On Jan 16, 2017, at 9:11 AM, COHEN, STEVEN M wrote:
>
> O
Our team is fairly standardized on using log4j2 over log4j, commons-logging or
any other framework.
This had presented some issues with jboss-eap which does not support log4j2.
Nevertheless, for applications running on the jboss-server it was fairly easy,
and even a good thing to package log4j
