Differences between revisions 4 and 5
Revision 4 as of 2005-06-02 14:24:33
Size: 1007
Comment:
Revision 5 as of 2009-09-20 23:01:27
Size: 1009
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
You need this setup because of myfaces being initialized twice in 1.0.9 and classloader hierarchy in Orion. To read more about how classloading works in Orion check: [http://kb.atlassian.com/content/atlassian/howto/classloaders.jsp] You need this setup because of myfaces being initialized twice in 1.0.9 and classloader hierarchy in Orion. To read more about how classloading works in Orion check: [[http://kb.atlassian.com/content/atlassian/howto/classloaders.jsp]]

Installing myfaces in Orion

To make it work you need to do the following:

Copy to Orion/lib (NOTE: myfaces.jar is NOT in this list):

 commons-beanutils-1.6.1.jar
 commons-codec-1.2.jar
 commons-collections-3.0.jar
 commons-digester-1.5.jar
 commons-el.jar
 commons-fileupload-1.0.jar
 commons-logging.jar
 commons-validator.jar
 jakarta-oro.jar
 jsp-2.0.jar
 jstl.jar
 myfaces-extensions.jar
 myfaces-jsf-api.jar
 standard-1.0.jar

And make sure in your application.xml file you have the path:

  • <library path="../lib;" />

Setup a new webmodule or application, and copy into WEB-INF/lib:

 myfaces.jar

After you load your new application in Orion you will get several INFO messages and should be able to use myfaces

You need this setup because of myfaces being initialized twice in 1.0.9 and classloader hierarchy in Orion. To read more about how classloading works in Orion check: http://kb.atlassian.com/content/atlassian/howto/classloaders.jsp

Make_it_work_with_Orion_application_server (last edited 2009-09-20 23:01:27 by localhost)