Mike bad news, actually not really, I also gave jetty 5.1.4 a testrun, I got the same results as in Tomcat, apparently the jenia popup demo nowadays uses myfaces as their base jsf implementation.
Your problems might be resolved by upgrading to a later jetty. 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. > > The relevent snippet from > jenia4faces-popup.jar:META-INF/faces-config.xml looks like this: > ================== > <!ENTITY popup SYSTEM "jenia-popup-config.xml"> > ]> > <faces-config xmlns="http://java.sun.com/JSF/Configuration";> > &popup; > </faces-config> > ================== > And "jenia-popup-config.xml" exists as > jenia4faces-popup.jar:META-INF/jenia-popup-config.xml > > I posted the same issue to the jenia4Face mailing list at this > location, but we haven't come up with a solution, and it's not really > a jenia4Faces issue. > > https://sourceforge.net/forum/forum.php?thread_id=1360538&forum_id=488135 >
