Greetings.
Trinidad only Works with Facelets? Because I have a jsp but the app is throwing a UnsopportedOperationException I have worked with MyFaces but I'm new with Trinidad <%...@page contentType="text/html" pageEncoding="UTF-8"%> <%...@taglib prefix="f" uri="http://java.sun.com/jsf/core"%> <%...@taglib prefix="h" uri="http://java.sun.com/jsf/html"%> <%...@taglib prefix="tr" uri="http://myfaces.apache.org/trinidad"%> <%...@taglib prefix="trh" uri="http://myfaces.apache.org/trinidad/html"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <%-- This file is an entry point for JavaServer Faces application. --%> <f:view> <tr:document> <h1><tr:outputText value="Hola Mundo" /></h1> <!-- Navbar or list --> <f:facet name="navigation3"> <tr:navigationPane var="foo" value="#{root_menu}" level="3" hint="list"> <f:facet name="nodeStamp"> <tr:commandNavigationItem text="#{foo.label}" action="#{foo.doAction}"/> </f:facet> </tr:navigationPane> </f:facet> <!-- Breadcrumbs --> <f:facet name="location"> <tr:breadCrumbs var="foo" value="#{root_menu}"> <f:facet name="nodeStamp"> <tr:commandNavigationItem text="#{foo.label}" action="#{foo.doAction}"/> </f:facet> </tr:breadCrumbs> </f:facet> </tr:document> </f:view> Faces-config.xml <?xml version='1.0' encoding='UTF-8'?> <!-- =========== FULL CONFIGURATION FILE ================================== --> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd";> <application> <default-render-kit-id>org.apache.myfaces.trinidad.core</default-render-kit- id> </application> <managed-bean> <managed-bean-name>root_menu</managed-bean-name> <managed-bean-class>org.apache.myfaces.trinidad.model.XMLMenuModel</managed- bean-class> <managed-bean-scope>request</managed-bean-scope> <managed-property> <property-name>source</property-name> <value>/WEB-INF/menu-metadata.xml</value> </managed-property> </managed-bean> </faces-config> Trinidad-config.xml <?xml version="1.0"?> <trinidad-config xmlns="http://myfaces.apache.org/trinidad/config";> <!-- Enable debug output --> <debug-output>false</debug-output> <accessibility-mode>default</accessibility-mode> <skin-family>simple</skin-family> </trinidad-config> Web.xml <?xml version="1.0" encoding="UTF-8"?> <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param> <!-- Trinidad also supports an optimized strategy for caching some view state at an application level, which significantly improves scalability. However, it makes it harder to develop (updates to pages will not be noticed until the server is restarted), and in some rare cases cannot be used for some pages (see Trinidad documentation for more information) --> <context-param> <param-name>org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE</param-na me> <param-value>false</param-value> </context-param> <!-- If this parameter is enabled, Trinidad will automatically check the modification date of your JSPs, and discard saved state when they change; this makes development easier, but adds overhead that should be avoided when your application is deployed --> <context-param> <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name> <param-value>false</param-value> </context-param> <!-- Enables Change Persistence at a session scope. By default, Change Persistence is entirely disabled. The ChangeManager is an API, which can persist component modifications (like, is a showDetail or tree expanded or collapsed). For providing a custom Change Persistence implementation inherit from the Trinidad API's ChangeManager class. As the value you have to use the fullqualified class name. --> <context-param> <param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name> <param-value>session</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.trinidad.resource.DEBUG</param-name> <param-value>true</param-value> </context-param> <filter> <filter-name>trinidad</filter-name> <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-clas s> </filter> <filter-mapping> <filter-name>trinidad</filter-name> <servlet-name>Faces Servlet</servlet-name> </filter-mapping> <!-- resource loader servlet --> <servlet> <servlet-name>resources</servlet-name> <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-c lass> </servlet> <servlet-mapping> <servlet-name>resources</servlet-name> <url-pattern>/adf/*</url-pattern> </servlet-mapping> <session-config> <session-timeout> 30 </session-timeout> </session-config> <welcome-file-list> <welcome-file>faces/welcomeJSF.jsp</welcome-file> </welcome-file-list> </web-app>
