Uploaded image for project: 'JBoss Messaging'
  1. JBoss Messaging
  2. JBMESSAGING-804

Provide a clean jboss-messaging-client.jar without containing external dependencies

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.2.0.Beta1, 1.0.1.SP3
    • Fix Version/s: 1.3.0.GA
    • Component/s: Build System
    • Labels:
      None
    • Estimated Difficulty:
      Low

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  clebert.suconic Clebert Suconic
                  Reporter:
                  galder.zamarreno Galder ZamarreƱo
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: