[jboss-user] [JBoss Seam] - Re: integration with Trinidad (ADF)

[lle]

Hi,
Yes, I followed the example on wiki and still got the exception.  I checked my faces-config.xml many times and very sure there's no configuration of the view handler there, only in web.xml.  Still got the exception...

Here is my 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">
  |  <display-name>Risk Application</display-name>
  |  
  |  <context-param>
  |   <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
  |   <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value>
  |  </context-param>
  | 
  |  <!-- Facelets with Trinidad configuration-->
  |  <context-param>
  |   <param-name>org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER</param-name>
  |   <param-value>com.sun.facelets.FaceletViewHandler</param-value>
  |  </context-param> 
  |  <!-- Use documents saved as *.xhtml -->
  |  <context-param>
  |   <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
  |   <param-value>.xhtml</param-value>
  |  </context-param> 
  | 
  | <!-- Use client-side state saving.  In Trinidad, it is an
  |        optimized, token-based mechanism that is almost always a
  |        better choice than the standard JSF server-side state saving. -->
  |   <context-param>
  |     <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
  |     <param-value>client</param-value>
  |     <!--param-value>server</param-value-->
  |   </context-param>
  | 
  |   <!-- Trinidad by default uses an optimized client-side state saving
  |        mechanism. To disable that, uncomment the following -->
  |   <!--context-param>
  |     <param-name>org.apache.myfaces.trinidad.CLIENT_STATE_METHOD</param-name>
  |     <param-value>all</param-value>
  |   </context-param-->
  | 
  |   <context-param>
  | 	<param-name>org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE</param-name>
  |     <param-value>false</param-value>
  |   </context-param>
  | 
  |   <context-param>
  |     <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
  |     <param-value>true</param-value>
  |   </context-param>
  | 
  |  <!-- <context-param>
  |     <param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name>
  |     <param-value>session</param-value>
  |   </context-param> -->
  |  
  |  <!-- Special Debug Output for Development -->
  |  <context-param>
  |   <param-name>facelets.DEVELOPMENT</param-name>
  |   <param-value>true</param-value>
  |  </context-param>
  | 
  |  <context-param>
  |   <description>If true, rendered HTML code will be formatted, so that it is "human readable".
  |   i.e. additional line separators and whitespace will be written, that do not
  |   influence the HTML code.
  |   Default: "true"</description>
  |   <param-name>org.apache.myfaces.PRETTY_HTML</param-name>
  |   <param-value>true</param-value>
  |  </context-param>
  |  <context-param>
  |   <description>If true, a javascript function will be rendered that is able to restore the
  |   former vertical scroll on every request. Convenient feature if you have pages
  |   with long lists and you do not want the browser page to always jump to the top
  |   if you trigger a link or button action that stays on the same page.
  |   Default: "false"</description>
  |   <param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
  |   <param-value>true</param-value>
  |  </context-param>
  | 
  |  <!-- ajax4jsf filter - must be before any other filter -->
  |  <filter>
  |   <display-name>Ajax4jsf Filter</display-name>
  |   <filter-name>ajax4jsf</filter-name>
  |   <filter-class>org.ajax4jsf.Filter</filter-class>
  |  </filter> 
  | <!-- trinidad -->
  |  <filter>
  |   <filter-name>trinidad</filter-name>
  |   <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
  |  </filter> 
  |  <!-- Propagate conversations across redirects -->
  |  <filter>
  |   <filter-name>Seam Redirect Filter</filter-name>
  |   <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
  |  </filter>
  |  <!-- Needed to ensure safe tx cleanup when using Seam-managed sessions/persistence contexts -->
  |  <filter>
  |   <filter-name>Seam Exception Filter</filter-name>
  |   <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
  |  </filter> 
  |  <filter-mapping>
  |   <filter-name>trinidad</filter-name>
  |   <servlet-name>Faces Servlet</servlet-name>
  |  </filter-mapping>
  |  <filter-mapping>
  |   <filter-name>ajax4jsf</filter-name>
  |   <url-pattern>*.jsf</url-pattern>
  |  </filter-mapping>
  |  <filter-mapping>
  |   <filter-name>Seam Redirect Filter</filter-name>
  |   <url-pattern>*.jsf</url-pattern>
  |  </filter-mapping>
  |  <filter-mapping>
  |   <filter-name>Seam Exception Filter</filter-name>
  |   <url-pattern>*.jsf</url-pattern>
  |  </filter-mapping>
  |  <!-- Seam -->
  |  <listener>
  |   <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
  |  </listener>
  |  <!-- MyFaces -->
  |  <listener>
  |   <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
  |  </listener>
  |  <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>*.jsf</url-pattern>
  |  </servlet-mapping>
  |  
  |  <!--  trinidad resources servlet -->
  |  <servlet>
  |   <servlet-name>resources</servlet-name>
  |   <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
  |  </servlet>
  | 
  | <!-- This cannot be configured currently -->
  | <servlet-mapping>
  |     <servlet-name>resources</servlet-name>
  |     <url-pattern>/adf/*</url-pattern>
  | </servlet-mapping>
  |  
  |  <!-- only allow developers to have access to the xhtml files -->
  |  <security-constraint>
  |   <display-name>Restrict XHTML Documents</display-name>
  |   <web-resource-collection>
  |    <web-resource-name>XHTML</web-resource-name>
  |    <url-pattern>*.xhtml</url-pattern>
  |   </web-resource-collection>
  |   <auth-constraint>
  |    <description>Only Let 'developer's access XHTML pages</description>
  |    <role-name>developer</role-name>
  |   </auth-constraint>
  |  </security-constraint>
  |  <login-config>
  |   <auth-method>BASIC</auth-method>
  |  </login-config>
  | </web-app>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995090#3995090

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995090