CODEWITHSUNDEEP
jsfjbossweblogicwebsphere
tasel
tasel

Reputation: 639

JSF 2 Issues in Application Servers?

I am familiar with the classloading trouble when using JSF 2 in Websphere 7. I'd like to know if there are similar problems on other fullstack application servers. What about JBoss 5+, WebLogi 10+, etc? Are there any known issues with JSF 2 and if so, what needs to be done to get JSF 2 running on these servers?

Thx

Upvotes: 4

Views: 8291

Answers (3)

Markus Eisele
Markus Eisele

Reputation: 722

Here is a brief how-to for the library concept Jeff mentioned. http://blog.eisele.net/2009/07/jsf-20-beta-1-on-oracle-weblogic-10gr3.html

Seeing the latest WLS 12c it still is in place but AFAIK you will end up having to revert the web-app classloader in the future in favor of this concept.

Upvotes: 0

BalusC
BalusC

Reputation: 1108732

On WebSphere 5.x up to with the current 8.x you need to set the WAR and EAR classloader to PARENT_LAST in the WAS admin console whenever you want to bundle and use your own JSF impl in /WEB-INF/lib.

On JBoss 4.x up to with the current 6.x it's sufficient to add the following context param to /WEB-INF/web.xml to suppress JBoss' builtin JSF deployer.

<context-param>
    <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
    <param-value>true</param-value>
</context-param>

On Glassfish 2.x up to with the current 3.x you need to add the following entries to the /WEB-INF/sun-web.xml (Eclipse with Glassfish plugin should autogenerate the template file if you create a web project with target runtime set to Glassfish).

<class-loader delegate="false" />
<property name="useBundledJsf" value="true" />

On Weblogic, sorry I have no idea, I have never used it.

Upvotes: 5

Jeff West
Jeff West

Reputation: 1563

In WebLogic there is a shared Java EE library that is included with WebLogic for JSF 2.0. It is easy to use and referenced through a deployment descriptor.

Upvotes: 0

Related Questions