Thanks for taking a look, Werner! I've had a couple of other Jetty issues (like no listeners in tld files), so it doesn't come as a complete surprise. On the other hand, the ease of using JettyLauncher under Eclipse over the tomcat sysdeo launcher will probably keep working with jetty for a while longer. Guess it's time to file some bug reports on jetty :)
On 10/3/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Hi Mike, I gave it a testrun, > just dumped the jenia jsps and the jena4faces into the latest > 1.1.1sandbox build, added the missing web.xml entries, > added the jsps css and the images and started it and gave the jsps from > jenia a testrun, worked out of the box > on a plain tomcat in the 1.1.1x myfaces sandbox for me... > > the problem probably is jetty related respectively related to the jetty > classloader. > Tomcat usually loads the classes from the WEB-INF/lib first and if not found > from > the tomcat itself, this is also how the later servlet specs to my knowlegde > want the servlet runners classloader to behave. > > Jetty might break this... > > Werner > > > > > Mike Kienenberger wrote: > > This is mostly directed at Werner now that he's a committer and since > > he's hit a similar error with Jenia4Faces popups and documented it on > > the wiki. :) But maybe someone else more familiar with web > > containers and/or myfaces configuration loading can comment. > > > > There's something wrong with the path configuration when using Jetty > > 5.1.3 and MyFaces (nightlies included). > > > > It's unclear to me whether it's a MyFaces path configuration issue or > > a web container (Jetty 5.1.3 issue). I'm guessing the former since > > Werner's posted error differs from mine, implying a different > > container. > > > >
