Please send me your war file (using YouSendIt) to be able to check that. What is the WebSphere version do you use 6.0 or 6.1 or 7.0 ?
On Mon, Sep 14, 2009 at 12:32 PM, domincb <[email protected]> wrote: > > But if I delete the commons-logging.jar and the log4j.jar, I can't use the > log4j for logging ¿no? > > Anyway, I have another application, that no use jsf and use log4j, and I > have no problem. I put the same librarys (I showed it in the first > messagge) > and I get the listener problem. > > > > > > Hazem Saleh-2 wrote: > > > > http://www-01.ibm.com/support/docview.wss?uid=swg21220353 > > > > Please make sure that *"all required logging files are provided with this > > WAR file Or no other logging files are provided with this WAR file."*, so > > my > > advise is to delete all of the logging jars from your web application and > > to > > use the application server ones as WebSphere already ships these jars. > > > > On Mon, Sep 14, 2009 at 12:03 PM, domincb <[email protected]> wrote: > > > >> > >> Yes, the loading policy is PARENT_LAST and APPLICATION. > >> > >> I have tried to put a 1.0.4 version of commons-logging.jar, and I get > the > >> same message in the logs, and if I put the version 1.1.1, the exception > >> is > >> the next one: > >> > >> SRVE0026E: [Error de servlet]-[java.lang.Exception: > >> java.lang.ExceptionInInitializerError > >> at > >> > >> > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(ServletWrapper.java:1461) > >> at > >> > >> > com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1312) > >> at > >> > >> > com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:84) > >> at > >> com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:745) > >> ... > >> > >> Caused by: org.apache.commons.logging.LogConfigurationException: The > >> chosen > >> LogFactory implementation does not extend LogFactory. Please check your > >> configuration. (Caused by java.lang.ClassCastException: The application > >> has > >> specified that a custom LogFactory implementation should be used but > >> Class > >> 'com.ibm.ws.commons.logging.TrLogFactory' cannot be converted to > >> 'org.apache.commons.logging.LogFactory'. The conflict is caused by the > >> presence of multiple LogFactory classes in incompatible classloaders. > >> Background can be found in http://commons.apache.org/logging/tech.html. > >> If > >> you have not explicitly specified a custom LogFactory then it is likely > >> that > >> the container has set one without your knowledge. In this case, consider > >> using the commons-logging-adapters.jar file or specifying the standard > >> LogFactory from the command line. Help can be found > >> @http://commons.apache.org/logging/troubleshooting.html.) > >> > >> > >> any suggestions to resolve the error? > >> > >> > >> > >> > > > > -- > View this message in context: > http://www.nabble.com/log4j-and-myfaces-problem-in-websphere-tp25399180p25432855.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > > -- Hazem Ahmed Saleh Ahmed Author of (The Definitive Guide to Apache MyFaces and Facelets): http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370 http://www.amazon.com/-/e/B002M052KY Web blog: http://www.jroller.com/page/HazemBlog [Web 2.0] Google Maps Integration with JSF: http://code.google.com/p/gmaps4jsf/ http://www.ibm.com/developerworks/library/wa-aj-gmaps/
