Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1313

RepositorySelector should be integrated into JBoss Server


    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M3
    • Component/s: JMX
    • Labels:


      Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging

      The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly.

      This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger().

      We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration.

        Gliffy Diagrams


          1. log4j-rs-withTimerTask.zip
            71 kB
          2. log4j-test.sar
            3 kB
          3. log4-rs.zip
            16 kB
          4. TestingLog4j.zip
            4.42 MB

            Issue Links



                • Assignee:
                  ssilvert Stan Silvert
                  ssilvert Stan Silvert
                • Votes:
                  7 Vote for this issue
                  6 Start watching this issue


                  • Created: