Java Server Faces (JSF)

From OpenCms Wiki
Revision as of 04:15, 8 July 2008 by Thowland (Talk | contribs)
Jump to: navigation, search

Integrating OpenCms with JavaServer Faces 1.1 is possible. JSF 1.2 seems not to work with up to OpenCms 7.0.4. This articles lists all the work that has to be done to use JSF within OpenCms.

Contents

Prerequisites

Before you start you have to decide on the software versions you want to use. On the Apache website there is a compatibility list for Apache's software stack (Tomcat, MyFaces).

The following combinations are known to work (please extend!):
Java RuntimeOpenCmsServlet Container/Application ServerJSF Implementation
1.57.0.1 (WebApp 2.4)Tomcat 6.0.14Sun RI 1.1_02
1.57.0.1 (WebApp 2.4)Tomcat 5.5.23Sun RI 1.1_02
1.57.0.1 (WebApp 2.4)Tomcat 5.5.23MyFaces 1.1.5
1.56.2.3 (WebApp 2.3)Tomcat 6.0.14Sun RI 1.1_02
1.57.0.2 (WebApp 2.4)Tomcat 6.0.14Sun RI 1.1_02
1.67.0.4 (WebApp 2.4)Tomcat 5.5.26MyFaces 1.1.5
The following seem to NOT work:
  • JSF 1.2 in general. Tested with Sun's RI (Mojara) and Apache Myfaces.
  • With Mojara the JSF page ist rendered, but output of JSF tags is out of order and partially overwriting JSP output. In addition to this the output is truncated, depending on the <f:view>-tag's content size.
  • With Apache MyFaces the output of the JSF page is incomplete. Non-JSF output seems to be missing completely.


Integrating OpenCms and Java Server Faces

Copy JSF Libraries

First, get the JSF implementation of your choice. Unzip the distribution and search for the JAR files named jsf-api.jar and jsf-impl.jar (usually in the lib directory). Copy these two archives to WEB-INF/lib in your OpenCms installation directory.

Adapt Webapplication Descriptor

Next you have to configure the servlet mapping in WEB-INF/web.xml. Add the following sections: 

   <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>

Note that it has been reported, that suffix-mapping (e.g, *.jsf) should work as well but I couldn't get it to work, so I used prefix mapping, i.e. "/faces/*", instead.

Create Faces Configuration

Next you can create a JSF configuration file in WEB-INF/faces-config.xml like this: 

<?xml version="1.0"?>
<faces-config 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"
        version="1.2">
   <navigation-rule>
      <from-view-id>/opencms/jsf-example.jsp</from-view-id>
      <navigation-case>
         <from-outcome>login</from-outcome>
         <to-view-id>/opencms/jsf-example2.jsp</to-view-id>
      </navigation-case>
   </navigation-rule>

   <managed-bean>
      <managed-bean-name>user</managed-bean-name>
      <managed-bean-class>com.corejsf.UserBean</managed-bean-class>
      <managed-bean-scope>session</managed-bean-scope>
   </managed-bean>
</faces-config>

Add Bean Classes

Add bean classes as you need them to WEB-INF/classes or in a JAR file, as you like.

Restart Servlet Container

Restart your servlet container.

Use your JSF pages with the correct URLs

Create you JSF pages and access them with the correct URLs. There is nothing special in creating JSF pages. Just go to OpenCms' workplace, click on "New", select "JSP" as the type for you new JSF page and insert your code.

When you want to access a JSF page use the base URL http://myhost:8080/opencms/faces/opencms/ with the path of the file in workplace appended. For example if you have a file jsf-example.jsp in your root-folder of the /sites/default site, access it via the URL http://myhost:8080/opencms/faces/opencms/jsf-example.jsp.

Here's a simple servlet filter that rewrites any pages ending with ".jsf" to /opencms/faces/opencms . This way, you can click on the JSF pages within the editor and get the preview to work correctly. You'll need to name all your JSF pages ".jsf" for this to work. The filter requires the Apache Commons Lang libraries:

Invalid language.

You need to specify a language like this: <source lang="html">...</source>

Supported languages for syntax highlighting:

actionscript, ada, apache, applescript, asm, asp, autoit, bash, blitzbasic, bnf, c, c_mac, caddcl, cadlisp, cfdg, cfm, cpp, cpp-qt, csharp, css, d, delphi, diff, div, dos, eiffel, fortran, freebasic, gml, groovy, html4strict, idl, ini, inno, io, java, java5, javascript, latex, lisp, lua, matlab, mirc, mpasm, mysql, nsis, objc, ocaml, ocaml-brief, oobas, oracle8, pascal, perl, php, php-brief, plsql, python, qbasic, reg, robots, ruby, sas, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vb, vbnet, vhdl, visualfoxpro, winbatch, xml, z80


You'll also need to map it in web.xml:

Invalid language.

You need to specify a language like this: <source lang="html">...</source>

Supported languages for syntax highlighting:

actionscript, ada, apache, applescript, asm, asp, autoit, bash, blitzbasic, bnf, c, c_mac, caddcl, cadlisp, cfdg, cfm, cpp, cpp-qt, csharp, css, d, delphi, diff, div, dos, eiffel, fortran, freebasic, gml, groovy, html4strict, idl, ini, inno, io, java, java5, javascript, latex, lisp, lua, matlab, mirc, mpasm, mysql, nsis, objc, ocaml, ocaml-brief, oobas, oracle8, pascal, perl, php, php-brief, plsql, python, qbasic, reg, robots, ruby, sas, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vb, vbnet, vhdl, visualfoxpro, winbatch, xml, z80

Usefull Links

Retrieved from "http://www.opencms-wiki.org/index.php?title=Java_Server_Faces_(JSF)&oldid=3189"
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox