[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies

Fri May 18 03:28:57 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12362492 ] 

Andrei Martchouk commented on JBMESSAGING-804:
----------------------------------------------

Tim briefly described what we need. That's correct.

This issue planned for 1.2.0.SP2 according to this jira entry. And it's marked as "closed". Is the workaround described by Ovidiu the solution? 
I'd prefer the Tim's proposal as maintenable solution. Is any work planned for it?

> Provide a clean jboss-messaging-client.jar without containing external dependencies
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-804
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-804
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Build System
>    Affects Versions: 1.2.0.Beta1, 1.0.1.SP3
>            Reporter: Galder Zamarreno
>         Assigned To: Clebert Suconic
>             Fix For: 1.2.0.SP2
>
>
> We've installed JBoss messaging instead of JBossMQ and updated our application to connect to this. 
> We have to include jboss-messaging-client.jar to be able to use it, but now the following problem arises:
> jboss-messaging-client.jar has log4j classes in it, which are of an old version. Therefore, our .war 
> cannot deploy because it uses methods of log4j of the newer version (e.g. Logger.isTraceEnabled()).
> To your approach of patching jboss-messaging-client.jar: maybe we'll try it, but I'm afraid it includes 
> more classes that may clash with our system... What we need is a clean jboss-messaging-client.jar file, 
> without external dependencies, but I don't want to build it myself as it makes maintaining our JBoss 
> setup very hard.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira