Actually, I was referring to the fact that MyFaces required Tomcat 6 with it's 1.2.0 version.
http://raibledesigns.com/rd/entry/thoughts_on_myfaces_1_2 As a workaround, you could use Sun's RI: http://appfuse.org/display/APF/Changing+from+MyFaces+to+Sun%27s+RI MyFaces 1.2.2 doesn't require Tomcat 6 AFAIK. Matt On Wed, May 28, 2008 at 6:56 AM, Carlos Yagüe <[EMAIL PROTECTED]> wrote: > > Hi Matt, > > I'm using Tomcat 5.5.26. > > The issue you comment is this: > "there are hotdeploy issues with tomcat and configure listeners, something > that's being corrected in TC6" > https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_03/issues.html > https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_03/issues.html > > > This issue is fixed using JSF Facelets (jsf-api.jar, jsf-impl.jar) adding > the following listeners to the web.xml: > <listener> > <listener-class>com.sun.faces.config.ConfigureListener</listener-class> > </listener> > > <!-- Listener implementation to handle web application lifecycle events --> > <listener> > > <listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class> > </listener> > > But using MyFaces, It isn't possible, because these listeners aren't defined > in classpath. > > I'm thinking in create a patch to solve this bug.. :-U > > Thanks anyway! > > > > > mraible wrote: >> >> This is a known issue - if you use Tomcat 6, you won't have to perform >> these additional steps. >> >> Matt >> >> On Wed, May 28, 2008 at 1:50 AM, Carlos Yagüe <[EMAIL PROTECTED]> >> wrote: >>> >>> Hi >>> >>> I had several problems with an JSF Modular application on starting up in >>> Apache Tomcat 5.x >>> >>> Firstable, I can't run my application using an Apache Tomcat 5.5 >>> configured >>> in Eclipse Europa like a Server. >>> >>> I got this fatal warning trace: >>> WARN [main] AbstractFacesInitializer.initFaces(99) | No mappings of >>> FacesServlet found. Abort initializing MyFaces. >>> >>> >>> May somebody help me?? >>> >>> But I don't stop to find ideas, so I've decided work with the Maven >>> Apache >>> Tomcat plugin. >>> >>> To run this server in maven, I added tomcat maven plugin in pom.xml of >>> web >>> module: >>> <plugin> >>> <groupId>org.codehaus.mojo</groupId> >>> <artifactId>tomcat-maven-plugin</artifactId> >>> <version>1.0-alpha-1</version> >>> <configuration> >>> <path>/</path> >>> </configuration> >>> </plugin> >>> >>> I re-packed my webapp and I run tomcat with the next mvn-command: >>> $mvn_project/web> mvn tomcat:run-war >>> >>> But I got a new error: >>> No valid ExpressionFactory implementation is available but that's >>> required >>> as this application isn't running in a JSP 2.1 container. >>> >>> To fix this error, you have to add 2 dependencies to the application's >>> general pom.xml: >>> ... >>> <dependency> >>> <groupId>javax.el</groupId> >>> <artifactId>el-api</artifactId> >>> <version>${el.version}</version> >>> </dependency> >>> <dependency> >>> <groupId>com.sun.el</groupId> >>> <artifactId>el-ri</artifactId> >>> <version>${el.ri.version}</version> >>> </dependency> >>> ... >>> <!-- Testing dependency versions --> >>> ... >>> <el.version>1.0</el.version> >>> <el.ri.version>1.2</el.ri.version> >>> >>> And finally, the startup works!! >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/JSF-Modular---Starting-up-Apache-Tomcat-5.x---Problems-with-Eclipse-Europa---ExpressionFactory-tp17507020s2369p17507020.html >>> Sent from the AppFuse - User mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/JSF-Modular---Starting-up-Apache-Tomcat-5.x---Problems-with-Eclipse-Europa---ExpressionFactory-tp17507020s2369p17512037.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
