[ http://issues.apache.org/jira/browse/JCR-200?page=all ]
Tobias Strasser resolved JCR-200:
---------------------------------
Fix Version: 1.0
Resolution: Fixed
removed log4j configuration code from the RepositoryAccessSerlvet and created a
LoggingServlet that also can be configured using log4j's DOMConfigurator.
- removed WEB-INF/repository/log4j.properties
- added WEB-INF/log4j.xml
fixed in r240176
> move log4j initialization out of RepositoryStartupServlet
> ---------------------------------------------------------
>
> Key: JCR-200
> URL: http://issues.apache.org/jira/browse/JCR-200
> Project: Jackrabbit
> Type: Improvement
> Versions: 1.0
> Reporter: Tobias Strasser
> Assignee: Tobias Strasser
> Priority: Minor
> Fix For: 1.0
>
> the RepositoryStartupServlet initializes/configures the Log4J environment.
> this might not be desirable since other applications might already done so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
