On 21 December 2011 14:59, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > On 21 December 2011 13:50, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: >> Ok, >> >> first side peeve is that I have to use >> >> <listener> >> >> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> >> </listener> >> >> with jetty 8... > > Ok, not my main problem, but the issue with the above is that for some > reason Jetty is initializing the faces servlet before calling the > context listener.... yet the javadoc for servletcontextlistener says: > > "Notification that the web application initialization process is > starting. All ServletContextListeners are notified of context > initialization before any filter or servlet in the web application is > initialized." > > So that looks like jetty 8 has the sequencing incorrect... > >> >> but that is not my issue (though it could be related) >> >> my issue is that as soon as >> com.sun.jersey.server.impl.container.servlet.JerseyServletContainerInitializer >> is on the classpath for the webapp, jetty 8 picks up the >> /META-INF/services/ reference to it... and then, for some reason, >> MyFaces fails to initialize, suggesting that I should add the >> <listener> config THAT I ALREADY HAVE ADDED. >> >> Now it could be a bug in jetty that it parses the /META-INF/services >> even though my web.xml is saying 2.5 spec webapp... but still >> >> Anyone any ideas? > > Still stuck with this
I had <load-on-startup>1</load-on-startup> on the faces servlet... removing that seems to have fixed the issue > >> >> -Stephen
