[
https://issues.apache.org/jira/browse/TRINIDAD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628445#action_12628445
]
Stephen Friedrich commented on TRINIDAD-1215:
---------------------------------------------
Now that you mentioned it, I remember that problem.
My workaround was to package the jsp-api.jar containing the JspIdConsumer in my
war file.
Quite ugly, but seems not to hurt: The app is happily in production for a
couple of month now (on Tomcat 5.5.17).
> org.apache.myfaces.trinidadinternal.menu.MenuNode has a dependency on
> javax.faces.webapp.UIComponentTag
> -------------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1215
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1215
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.9-core
> Environment: MyFaces 1.2.3, Trinidad 1.2.9, Facelets 1.1.14
> Reporter: Richard Yee
>
> A NoClassDefFoundError occurs when using a tr:commandNavigationItem inside a
> tr:navigationPane tag to render a
> org.apache.myfaces.trinidad.model.XMLMenuModel. when using Facelets in a
> non-JSP 2.1 container.
> This is the output from Facelets:
> /menu.xhtml @15,66 text="#{menuItem.label}":
> oracle.classloader.util.AnnotatedNoClassDefFoundError: Missing class:
> javax.servlet.jsp.tagext.JspIdConsumer Dependent class:
> javax.faces.webapp.UIComponentClassicTagBase Loader:
> current-workspace-app.web.faceletMenuDemo:0.0.0 Code-Source:
> /develop/java/jakarta/myfaces-core-1.2.3/lib/myfaces-api-1.2.3.jar
> Configuration: <classpath> in
> /Users/richard/sandbox/faceletMenuDemo/java/src/web The missing class is not
> available from any code-source or loader in the system.
> The result is that the Trinidad XMLMenuModel cannot be used with Facelets in
> a non JSP 2.1 appserver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
