I added the Logger and TracePriority classes to the jboss-client.jar. Isn't this required by JBossMQ clients? If not, then these classes need to be redundantly added to jbossmq-client.jar
----- Original Message ----- From: "David Maplesden" <[EMAIL PROTECTED]> To: "JBossDev (E-mail)" <[EMAIL PROTECTED]> Sent: Thursday, December 13, 2001 2:57 PM Subject: RE: [JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq SpySession.java SpyMessageConsumer.java > Ok, I know this was a bit naughty. > > Part of the reason I did it (and I know this is not a good excuse) is that > we have a small problem in the build, introduced when you (I think it was > you) changed the Connection class to use org.jboss.logging.Logger. > > The problem is that Connection (along with SpySession and SpyMessageConsumer > etc) are client side classes and org.jboss.loggging.Logger is not included > in the jbossmq-client.jar. This means that jbossmq-client.jar is no longer > sufficient by itself for people to connect to JBossMQ, a CNF exception > occurs. > > The reason I am mentioning it is that I have had a look at the way > jbossmq-client is built and I am not sure of the best way to resolve this > problem, what do you suggest? > > David > > > -----Original Message----- > > From: Scott M Stark [mailto:[EMAIL PROTECTED]] > > Sent: Friday, December 14, 2001 11:58 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq > > SpySession.java SpyMessageConsumer.java > > > > > > Don't just drop the debug msgs, change them to trace msgs using > > the org.jboss.logging.Logger rather than org.apache.log4j.Category. > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
