RE: WebSphere 6.0 JSF implementation change for MyFaces

[Gary VanMatre]

The only success I've had is to remove the "jsf-api.jar" and "ws-jsf.jar" from the $WAS_INSTALL_ROOT/lib directory.  I agree that seems like a hack to have to remove a jar from the WAS 6 base install but I think it's the only way to prevent the "/META-INF/faces-config.xml" in the "ws-jsf.jar" from being loaded.  Even if you changed the loader policy, there is not a predefined order that the auto loading of the "/META-INF/faces-configs.xml" are processed.  You would still have a mix of RI and myfaces JSF runtimes. 

 

Gary

 

 

 

 

-------------- Original message --------------
From: "CONNER, BRENDAN (SBCSI)" <[EMAIL PROTECTED]>

I'd be interested in that as well.  The "official" way that IBM seems to recommend is to use PARENT_LAST class-loading, which will cause the server to look at the classes within the application JAR files before those in the server JAR files.  However, this causes other problems with our application, because we only want to override the JSF implementation classes, not *all* of the classes.

 

For now, we're just deleting the two JAR files you mentioned from the server's path, which seems like kind of a kluge.

 

- Brendan

 

-----Original Message-----
From: Pavel Vybiral [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 04, 2006 4:39 AM
To: users@myfaces.apache.org
Subject: WebSphere 6.0 JSF implementation change for MyFaces

Is there an official way how to change JSF implementation (IBM) in Websphere 6.0.0.0 for MyFaces one. I know that WS6 comes with its own implementation but I would like to disable loading of JSF classes from the shipped jar file (jsf-api.jar and ws-jsf.jar) to avoid class path clash and use MyFaces implementation instead.  Thanks.