Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      JBoss and perhaps other "containers"

      Description

      JBoss currently uses log4j for its own logging purposes. This causes numerous problems for applications that also want to use log4j for logging. JBoss has some documented methods for addressing the problems but none of them are particularly attractive. The goals for this issue should be:
      1. Allow each "application" to have its own configuration separate from JBoss' jboss-log4j.xml
      2. Allow applications to provide their own log4j components (Appenders, layouts, filters, etc) without having to put them in JBoss' classpath or the server/lib directory.

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Ralph Goers
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development