[Myfaces Wiki] Update of "Websphere_Installation" by StephenKenna

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "Websphere_Installation" page has been changed by StephenKenna:
http://wiki.apache.org/myfaces/Websphere_Installation?action=diff&rev1=15&rev2=16

+ = Websphere 8.0 Installation Guide =
+ ''MyFaces 2.0 is now the default implementation with WebSphere Application Server v8 and is supported out of the box - no extra configuration needed.  WAS v8 still comes with the JSF Reference Implementation(RI) version 1.2 that can be configured using admin commands or directly from the admin console.  Both MyFaces 2.0 and the JSF 1.2 RI are supported as first class OSGi runtime bundles.  You can package your own user-supplied version of MyFaces as a Shared Library or add the jars directly to your WEB-INF/lib, as stated in the WebSphere v7.0 instructions.''
+ 
  = Websphere 7.0 Installation Guide =
- ''Starting with Websphere 7.0, both the JSF Sun RI and a version of Myfaces are both shipped as part of the WAS runtime, with the ability provided to choose which implementation to use for your application after installation.  ''The following steps will detail how to use the implementation shipped with WAS.  It is still possible to use a user-supplied version of the MyFaces bundles by following the same steps outlined below for WebSphere 6.1.
+ ''Starting with Websphere 7.0, both the JSF Sun RI and a version of Myfaces are both shipped as part of the WAS runtime, with the ability provided to choose which implementation to use for your application after installation.  The following steps will detail how to use the implementation shipped with WAS.  It is still possible to use a user-supplied version of the MyFaces bundles.  If you are trying to use a user-supplied version of MyFaces 2.0, there are special steps that need to be taken for annotation and injection support.  Please see the section on using ''Using a user-supplied version of MyFaces 2.0.x with WebSphere Application Server v7.0.''
  
+ == Using the WebSphere Application Server v7.0 supported MyFaces implementations ==
- == 1. Deploy the web application on WAS. ==
+ === 1. Deploy the web application on WAS. ===
- == 2. Execute the command to change the runtime from Sun RI to MyFaces. ==
+ === 2. Execute the command to change the runtime from Sun RI to MyFaces. ===
  This can be done either via the [[http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tweb_jsf.html|WAS admin console]] or through a [[http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/txml_7jsf.html|wsadmin command]].
+ === 3. Start your application. ===
  
- If an application will be using a different version of Myfaces than the one shipped with WAS, do not execute this command and refer to the instructions below for WAS 6.1.
- 
- == 3. Start your application. ==
+ == Using a user-supplied version of MyFaces 2.0.x with WebSphere Application Server v7.0 ==
+ As of WebSphere Application Server 7.0.0.19, MyFaces 2.0 annotation providers are included as part of the WAS optionalLibraries.  A developerWorks article will be available soon with instructions on how to configure these providers.
+ ----
  = Websphere 6.1 Installation Guide =
  ''Unlike Websphere 6.0, in Websphere 6.1 the JSF Sun RI is bundled together with several other WAS libraries in com.ibm.ws.webcontainer_2.0.0.jar, so removing the webspheres JSF API jars is not an option. The procedure below describes how to use MyFaces, TOMAHAWK (and even Tiles) on Websphere 6.1 by altering the module classloader policy to load classes using the application class loader first (thereby loading the MyFaces jars before the Sun RI jars). This procedure has been tested with MyFaces 1.1.3, TOMAHAWK 1.1.3, and Websphere 6.1.0.2.''
  
@@ -23, +28 @@

  == 4. Start your application. ==
  If the extension-Filter does not work properly, it might help to set the property '''com.ibm.ws.webcontainer.invokefilterscompatibility=true'''. Instructions can be found at [[http://www-1.ibm.com/support/docview.wss?uid=swg24014758|this]] IBM support site.
  
+ ----
  = Websphere 6.0 Installation Guide =
  ****Please note that removing any of the jars from the WebSphere lib directory as described in these instructions is unsupported by IBM.  If you wish to maintain support you can use the alternate WebSphere 6.0 instructions below that do not remove the IBM jars ****
  
@@ -59, +65 @@

  
  '''Attention:''' Do not copy a myfaces-impl to AppServer/lib dir that depends on the old myfaces-commons library.<<BR>> Reason: Classloader problems may show up, when MyFaces-Impl and MyFaces-Tomahawk reference different myfaces-commons.jar versions.<<BR>> In MyFaces 1.1.2 the commons project was refactored and is now called shared.<<BR>> The shared classes are part of both myfaces-impl and myfaces-tomahawk. To avoid classloader problems due to different versions of shared classes the package names are  different for impl and tomahawk. <<BR>>
  
+ ----
  = Websphere 6.0 Installation Guide (without removing IBM jars) =
  ''This is a simple procedure to use MyFaces, TOMAHAWK (and even ADF Faces) on a Websphere 6 webapp just using its "PARENT_LAST" property.  This procedure is being tested without any problem until now on a Websphere BASE 6.0.0.0 o0444.14. This requires access to the internet, because the ibm implementation of JSF tries to resolve the faces-config.xml dtd'' This, however, can be circumvented by replacing all references to ''web-facesconfig_1_1.dtd'' with a reference to ''web-facesconfig_1_0.dtd''. For example, a faces config like this:
  
@@ -109, +116 @@

  == 2. Deploy web application on WAS ==
  Use Classloader option "Parent last"
  
+ ----
  = Websphere 5.1.X  Installation Guide =
  == 1. Use Classloader option "Parent last" ==
  == 2. List of files in WAR's lib, some files may not be needed, but it works for me. ==