- This topic has 1 reply, 2 voices, and was last updated 19 years, 1 month ago by Riyad Kalla.
-
AuthorPosts
-
koslMemberHello,
I’m writing an application using myfaces, I tried to move to myfaces 1.1.1, but when I try to use it I get the following exception:
javax.servlet.ServletException: /admin/console.jsp(20,0) The absolute uri: http://myfaces.apache.org/extensions cannot be resolved in either web.xml or the jar files deployed with this application javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) root cause javax.faces.FacesException: /admin/console.jsp(20,0) The absolute uri: http://myfaces.apache.org/extensions cannot be resolved in either web.xml or the jar files deployed with this application org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:421) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
Does anybody know what might be the cause? I’m using the tomahawk.jar, and I guess there is something wrong in my web.xml or faces-config.xml..
Thanks in advice for any help..
Karol
Riyad KallaMemberKarol,
It looks like the URI of one of the taglibs you are using might have changed on you. Find the JAR that provides your myfaces extensions tags, and open it up, go into the META-INF dir and open one of the TLD files, look around the 5th line or so for a tag:
<url>blahblah</url>use whatever the blahlbha part is to update your web.xml <taglib> entries OR if you are using the default URI, update your <%@taglib%> entries in your JSP files.
-
AuthorPosts