[seam-issues] [JBoss JIRA] (JBSEAM-4967) seam-messages fails with "The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application"

Marek Novotny (JIRA) jira-events at lists.jboss.org
Sat May 26 15:19:17 EDT 2012


     [ https://issues.jboss.org/browse/JBSEAM-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny resolved JBSEAM-4967.
-----------------------------------

    Resolution: Done


migrated to JSF facelets page
                
> seam-messages fails with "The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4967
>                 URL: https://issues.jboss.org/browse/JBSEAM-4967
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0.BETA2
>         Environment: AS 7.1.2.Final
>            Reporter: Marek Schmidt
>            Assignee: Marek Novotny
>              Labels: messages
>             Fix For: 2.3.0.CR1
>
>
> seam-messages fails with
> {noformat}
> org.apache.jasper.JasperException: The absolute uri: http://jboss.com/products/seam/taglib cannot be resolved in either web.xml or the jar files deployed with this application
> 	org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
> 	org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
> 	org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
> 	org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:239)
> 	org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:152)
> 	org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:386)
> 	org.apache.jasper.compiler.Parser.parseDirective(Parser.java:448)
> 	org.apache.jasper.compiler.Parser.parseElements(Parser.java:1398)
> 	org.apache.jasper.compiler.Parser.parse(Parser.java:130)
> 	org.apache.jasper.compiler.ParserController.doParse(ParserController.java:255)
> 	org.apache.jasper.compiler.ParserController.parse(ParserController.java:103)
> 	org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:194)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
> 	org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
> 	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> 	com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:546)
> 	javax.faces.context.ExternalContextWrapper.dispatch(ExternalContextWrapper.java:93)
> 	com.sun.faces.application.view.JspViewHandlingStrategy.executePageToBuildView(JspViewHandlingStrategy.java:364)
> 	com.sun.faces.application.view.JspViewHandlingStrategy.buildView(JspViewHandlingStrategy.java:154)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list