1 Reply Latest reply on Jan 2, 2007 5:04 AM by Stefan Seidel

    JSF Integration with JBoss Portal

    Vikash Anand Newbie

      Dear All;
      I am new to JBoss Portal. I have a sample JSF Application which is running fine. I want that application to run under JBoss Portal. I have configured XML files. these files are:
      1. faces-config.xml
      2. jboss-app.xml
      3. jboss-portlet.xml
      4. portlet-object.xml
      5. portlet.xml
      6. web.xml

      Whenever i am starting my JBoss server it gives following error:
      17:47:09,938 WARN [ExtensionsFilter] Please adjust your web.xml to use org.apache.myfaces.webapp.filter.ExtensionsFilter

      I have included all jar files in WEB-INF and server/default/lib. Please let me know where i am making mistake.

      Snapshot of web.xml

      <web-app>
      
       <context-param>
      <param-name>javax.faces.CONFIG_FILES</param-name>
      <param-value>
       /WEB-INF/examples-config.xml
       </param-value>
      
       <description>
      
       Comma separated list of URIs of (additional) faces config files.
       (e.g. /WEB-INF/my-config.xml)
       See JSF 1.0 PRD2, 10.3.2
      
      </description>
      </context-param>
      
       <context-param>
      <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
      <param-value>server</param-value>
      
       <description>
      
       State saving method: "client" or "server" (= default)
       See JSF Specification 2.5.2
      
      </description>
      </context-param>
      
       <context-param>
      <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
      <param-value>true</param-value>
      
       <description>
      
       This parameter tells MyFaces if javascript code should be allowed in the
       rendered HTML output.
       If javascript is allowed, command_link anchors will have javascript code
       that submits the corresponding form.
       If javascript is not allowed, the state saving info and nested parameters
       will be added as url parameters.
       Default: "true"
      
      </description>
      </context-param>
      
       <context-param>
      <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name>
      <param-value>false</param-value>
      
       <description>
      
       This parameter tells MyFaces if javascript code should be allowed in the
       rendered HTML output.
       If javascript is allowed, command_link anchors will have javascript code
       that submits the corresponding form.
       If javascript is not allowed, the state saving info and nested parameters
       will be added as url parameters.
       Default: "false"
      
       Setting this param to true should be combined with STATE_SAVING_METHOD "server" for
       best results.
      
       This is an EXPERIMENTAL feature. You also have to enable the detector filter/filter mapping below to get
       JavaScript detection working.
      
      </description>
      </context-param>
      
       <context-param>
      <param-name>org.apache.myfaces.PRETTY_HTML</param-name>
      <param-value>true</param-value>
      
       <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>
      </context-param>
      
       <context-param>
      <param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
      <param-value>true</param-value>
      
       <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>
      </context-param>
      <!-- WelcomeFile Filter -->
      
       <!--
      
       <filter>
       <filter-name>WelcomeFile Filter</filter-name>
       <filter-class>org.apache.myfaces.webapp.filter.WelcomeFileFilter</filter-class>
       <description>
       Due to the manner in which the JSP / servlet lifecycle
       functions, it is not currently possible to specify default
       welcome files for a web application and map them to the
       MyFacesServlet. Normally they will be mapped to the
       default servlet for the JSP container. To offset this
       shortcoming, we utilize a servlet Filter which examines
       the URI of all incoming requests.
       </description>
       </filter>
      
      -->
      <!-- JavaScriptDetector Filter -->
      <!-- <filter>-->
      
       <!--
       <filter-name>javascriptDetector</filter-name>
      -->
      
       <!--
       <filter-class>org.apache.myfaces.webapp.filter.JavaScriptDetectorFilter</filter-class>
      -->
      <!-- </filter>-->
      <!-- Extensions Filter -->
      
       <filter>
      <filter-name>extensionsFilter</filter-name>
      
       <filter-class>
      org.apache.myfaces.component.html.util.ExtensionsFilter
      </filter-class>
      
       <init-param>
      <param-name>uploadMaxFileSize</param-name>
      <param-value>100m</param-value>
      
       <description>
      Set the size limit for uploaded files.
       Format: 10 - 10 bytes
       10k - 10 KB
       10m - 10 MB
       1g - 1 GB
      
      </description>
      </init-param>
      
       <init-param>
      <param-name>uploadThresholdSize</param-name>
      <param-value>100k</param-value>
      
       <description>
      Set the threshold size - files
       below this limit are stored in memory, files above
       this limit are stored on disk.
      
       Format: 10 - 10 bytes
       10k - 10 KB
       10m - 10 MB
       1g - 1 GB
      
      </description>
      </init-param>
      
       <!--
       <init-param>
       <param-name>uploadRepositoryPath</param-name>
       <param-value>/temp</param-value>
       <description>Set the path where the intermediary files will be stored.
       </description>
       </init-param>
      -->
      </filter>
      <!-- Filter Mappings -->
      <!-- see MyFaces Filter above for a description -->
      
       <!--
      
       <filter-mapping>
       <filter-name>WelcomeFile Filter</filter-name>
       <url-pattern>/*</url-pattern>
       </filter-mapping>
      
      -->
      <!-- <filter-mapping>-->
      
       <!--
       <filter-name>javascriptDetector</filter-name>
      -->
      
       <!--
       <url-pattern>/_javascriptDetector_</url-pattern>
      -->
      <!-- </filter-mapping>-->
      
       <filter-mapping>
      <filter-name>extensionsFilter</filter-name>
      <url-pattern>*.jsf</url-pattern>
      </filter-mapping>
      
       <filter-mapping>
      <filter-name>extensionsFilter</filter-name>
      <url-pattern>/faces/*</url-pattern>
      </filter-mapping>
      
       <!--
       Listener, that does all the startup work (configuration, init).
      -->
      
       <listener>
      
       <listener-class>
      org.apache.myfaces.webapp.StartupServletContextListener
      </listener-class>
      </listener>
      <!-- Faces Servlet -->
      
       <servlet>
      <servlet-name>Faces Servlet</servlet-name>
      <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
      </servlet>
      <!-- Faces Servlet Mapping -->
      <!-- virtual path mapping -->
      
       <!--
      
       <servlet-mapping>
       <servlet-name>Faces Servlet</servlet-name>
       <url-pattern>/faces/*</url-pattern>
       </servlet-mapping>
      
      -->
      <!-- extension mapping -->
      
       <servlet-mapping>
      <servlet-name>Faces Servlet</servlet-name>
      <url-pattern>*.jsf</url-pattern>
      </servlet-mapping>
      <!-- Welcome files -->
      
       <welcome-file-list>
       <welcome-file>index.html</welcome-file>
       <welcome-file>index.htm</welcome-file>
       <welcome-file>index.jsp</welcome-file>
       <welcome-file>default.html</welcome-file>
       <welcome-file>default.htm</welcome-file>
       <welcome-file>default.jsp</welcome-file>
      </welcome-file-list>
      </web-app>
      


      Thanks in advance for your help;
      Regards;
      Vikash Anand

        • 1. Re: JSF Integration with JBoss Portal
          Stefan Seidel Newbie

           

          "vikash.anand" wrote:

          Whenever i am starting my JBoss server it gives following error:
          17:47:09,938 WARN [ExtensionsFilter] Please adjust your web.xml to use org.apache.myfaces.webapp.filter.ExtensionsFilter

          <web-app>
          <!-- Extensions Filter -->
          
           <filter>
          <filter-name>extensionsFilter</filter-name>
          
           <filter-class>
          org.apache.myfaces.component.html.util.ExtensionsFilter
          </filter-class>
          
          

          N.B.: WARN != ERROR
          Replace org.apache.myfaces.component.html.util.ExtensionsFilter with org.apache.myfaces.webapp.filter.ExtensionsFilter as suggested by the warning.

          Stefan