It seems like an entity resolver or servlet contect resolve issue, the loader of this class seems to fail to load the xml file:
All I can say mike, is push this down the spring mailing list and check for answers it definitely is somewhere on the spring side... I assume you use the spring internal jsf-spring bindings, all I can say is, do not use them they are too limited in my experience, go for the http://jsf-spring.sourceforge.net/ library you can find config files for that stuff ripped straight out of my last project here: http://wiki.apache.org/myfaces/JSF_Spring_Config they are for myfaces 1.0.9 but should be easy to alter for 1.1.x The reason why I think it might help is that the lib might use a different loading mechanism for the xml config files. Werner Mike Kienenberger wrote: > Well, that'd really be good news. I had read the release notes for > 5.1.4 and even 5.1.5 rc1, but there no mention of a fix. > > I'm still seeing the same behavior under 5.1.5rc1, so the problem is > possibly in Spring. I've tried running it directly in jetty skipping > the JettyLauncher, and also see the same problem, so if you had it > running under 5.1.4, I don't see any other option than to blame > Spring. In fact, I'm getting the same error under Tomcat 5.0.30 as > well. That seems to rule out a container issue. > > java.io.FileNotFoundException: Could not open ServletContext resource > [/jenia-popup-config.xml] > at > org.springframework.web.context.support.ServletContextResource.getInputStream(ServletContextResource.java:92) > at > org.springframework.context.support.ResourceEntityResolver.resolveEntity(ResourceEntityResolver.java:84) > at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown > Source) > > > > On 10/3/05, Werner Punz <[EMAIL PROTECTED]> wrote: > >>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 >>> >> >> >
