Thanks Vincet and Sergiu. But After doing suggested steps and i hit the url https://localhost/mywiki/. I get http status 404 error(requested resource not found). What i did is this inside WEB-INF\lib 1)placed log4j-1.2.8 and slf4j-log4j12-1.6.1 2)removed log4j-over-slf4j-1.6.2,logback-classic-0.9.30 and logback-core-0.9.30 inside WEB-INF\classes placed log4j.properties On startup, inside the tomcat logs 28-Apr-2012 18:50:05.468 SEVERE org.apache.catalina.core.StandardContext.start Error listenerStart 28-Apr-2012 18:50:05.468 SEVERE org.apache.catalina.core.StandardContext.start Context [/mywiki] startup failed due to previous errors Looks like there is some other jar too which is conflicting. As soons as reverted back above steps , application runs fine. On Sun, Apr 29, 2012 at 12:01 PM, Vincent Massol <[email protected]> wrote:
On Apr 29, 2012, at 5:24 AM, Sergiu Dumitriu wrote:
On 04/28/2012 04:40 PM, Vincent Massol wrote:
On Apr 28, 2012, at 8:48 PM, Sergiu Dumitriu wrote:
On 04/28/2012 08:02 AM, Vincent Massol wrote:
Hi Mohit,
On Apr 28, 2012, at 1:34 PM, mohit gupta wrote:
At http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Logging, it
is
stated that By default XWiki is configured so that SLF4J uses Logback. XWiki's Logback configuration is located in the WEB-INF/classes/logback.xml file for For XWiki 3.1 and beyond. But if user want to use log4j instaed of logback, where it needs to be configured.
I did not find any property related to that in xwiki.cfg or xwiki.properties.What i tried deleting the logback.xml and putting my log4j.properties instaed. But xwiki does not pick log4j.properties. As per my understanding, xwiki is using SLF4J, there should be hook somewhere where we should be able to change to log4j insteadd of logback.
I've updated http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Logging
Some feedback on the documentation you just added:
I wonder if log4j-over-slf4j should be removed or not, since it might conflict with the real log4j library (they define the same classes).
It must be there or the bridging won't work. Our build automatically verifies that no 3rd party dependency we drag includes log4J. We handle this by using<exclusions> when a jar includes log4J transitively.
What bridging? From log4j to slf4j? But when slf4j will try to write back to log4, won't it cycle back through this bridge? As I said, this jar defines the same classes as the real log4j jar. One can't have two classes with the same name in the classpath.
You're right. I thought you wanted to do this for our build. I didn't understand you meant fixing the doc…
Fixed now.
Thanks -Vincent
Also, should the documentation mention that the log4j jar must be included as well? slf4j-log4j12 declares it as a dependency, so it's not included in that jar.
Indeed, fixed, thanks.
Thanks -Vincent
You could also have read about how SLF4J works at http://www.slf4j.org/ ;)
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users