Hi,
I'm trying to develop JSF 2.0 applications with IBM's "RAD8 and WAS7.0.0.0".
When I deployed the application via RAD 8 IDE, the application configuration options were disabled so that I could not change anything such as "class loader policy" and adding "shared library references".
Once I deployed manually an exported EAR file (using server admin console), those options are available, but class loader policy changes are ignored by the server. Even if I changed it to "parent last" mode, it loads default JSF 1.2 (server) library at the application start.
Once I deployed the same EAR file manually (using server admin console), and assigned the JSF 2.0 library as a shared library and added references to my application, it loads JSF 2.0 library on the application start, but still the server doesn't compile the JSF mark up into html/xhtml mark up. It shows all the JSF source code with component tags like
<h:outputText value="#{userBean.id}"/>With all the steps that I mentioned in point 3 above, I added JSF jar files in to WEB_INF/lib folder, and then I got the expected output.
If someone has done a JSF2.0 deployment on as 7.0.0.0 just using the Shared library, please help me advising me how to do a successful deployment without doing these type of things. I just could managed to run it, but according to the theory; we don't want to put the same jar files within 3 places at the same time.
- WEB-INF/lib
- java build path of the web application
- As a shared library on the server
Thanks in advance!