Web Application Server support

> > > >

Apache Tomcat™ 7.0.72 is the reference Web application server shipped with Rogue Wave® JViews.

Other application servers have been tested, including

The following sections give useful information you might need when you deploy JViews Web applications to one of these supported servers.

JBoss Application Server 5.1.0.GA

JBoss® AS 5.1.0.GA includes a JSF implementation. To avoid conflicts, do not include JSF jars in your .war file when deploying JViews Web applications or, to disable the built-in JSF, add the following code to your web.xml:
```
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param> 
```
Replace the xercesImpl.jar in the <JBoss_HOME>/lib/endorsed folder with xercesImpl-2.9.1.jar in your demo .war file.
JBoss AS 5.1.0.GA does not support multipattern <servlet-mapping> elements in web.xml. Use multiple <servlet-mapping> elements with separate patterns.

IBM WebSphere Application Server Network Deployment 7.0

WebSphere® Application Server Network Deployment (WAS ND) 7.0 includes a JSF implementation. You can choose to use it or not based on your Web application requirements.
JViews Web Applications can run with the integrated JSF implementation. In this case, when you build JViews Web application .war files, you must exclude any JSF implementation. For example, you must not include either the jsf-api-1.2_07-b03-FCS.jar or the jsf-impl-1.2_07-b03-FCS.jar in your .war files.
The WebSphere Application Server (WAS) AdminConsole offers a configuration step to select either Sun™ JSF 1.2 or MyFaces 1.2 for registering the appropriate listener class with the container. In this way, you do not have to define the listener class in the web.xml file associated with the application, see IBM InfoCenter for additional information.
The integrated JSF implementation can be replaced by a Sun JSF implementation that is included in your Web application .war file.
You must change the schema of your web.xml to 2.5 .
Some known issues apply to the deployment of ICEfaces applications to WebSphere. See http://jira.icefaces.org/browse/ICE-2330 and http://jira.icefaces.org/browse/ICE-3684.

Oracle WebLogic Server 10.3

You must change the schema of your web.xml to 2.5.
For the exception “The deferred EL expression is not allowed because deferredSyntaxAllowedAsLiteral is false ”, you must add <%@ page deferredSyntaxAllowedAsLiteral="true" %> in the JSP page.
For Trinidad demos with invalid PPR responses, the problem is caused by an invalid XML response; for more details, see JIRA issue https://issues.apache.org/jira/browse/TRINIDAD-1170.

Web Application Server Community Edition 2.1.1.3

Web Application Server Community Edition (WAS CE) is shipped with a MyFaces JSF implementation. You can choose to enable or disable the MyFaces JSF module in WAS CE based on the requirements of your JViews Web applications.

JViews Web applications can run with the integrated MyFaces implementation. In this case, you do not need to disable the integrated MyFaces module. However, when you build JViews Web application .war files, you must exclude any JSF implementation. For example, you must not include either jsf-api-1.2_07-b03-FCS.jar or jsf-impl-1.2_07-b03-FCS.jar in your .war files.

The integrated MyFaces implementation can be disabled and replaced by a Sun JSF implementation that is included in your Web application .war file. WAS CE might have issues with some specific Sun JSF implementations.

To disable the MyFaces JSF module in WAS CE:

Log on to the WAS CE administrative console.
Go to System Modules.
Check the option Expert User.
Stop the following modules:
- org.apache.geronimo.configs/myfaces/2.1.4/car
- org.apache.geronimo.configs/myfaces-deployer/2.1.4/car

To deploy a .war file on the WAS CE server:

(Optional) Create a WEB-INF/geronimo-web.xml deployment plan file with the following content:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<web:web-app xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0" xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0" xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2" xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2" xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2" xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2" xmlns:pers="http://java.sun.com/xml/ns/persistence" xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1" xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0" xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
    <dep:environment>
        <dep:moduleId>
            <dep:groupId>default</dep:groupId>
            <dep:artifactId>jsf-framework-code-fragments</dep:artifactId>
            <dep:version>1.0</dep:version>
            <dep:type>car</dep:type>
        </dep:moduleId>
    </dep:environment>
    <web:context-root>/jsf-framework-code-fragments</web:context-root>
</web:web-app>

Build the .war file using build.bat in demo folder.
Copy the .war file to the %WASCEDIRECTORY%\deploy folder.
Start the server and wait for WAS CE to deploy the application.

Current section

Interoperability with third party Web technologies