Have You tried making a server level custom classloader and then make a shared library with your JSF jars in it and use that shared lib with the custom classloader? That was the only way I could avoid the problems with WAS built-in JSF impl.
Z -----Original Message----- From: Martin Ahrer [mailto:[EMAIL PROTECTED] Sent: 11. elokuuta 2008 14:58 To: [email protected] Subject: Re: [Tomahawk] - Both MyFaces and the RI are on your classpath Simon, I'm trying to do something (probably) similar: Porting a JBoss Seam JSF RI 1.2 app to WebSphere 6.1. I have been running into many problems. Now I'm stuck with an exception at startup java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:164) For this I actually created a fresh JSF 1.2 appplication with no other dependencies than JSF 1.2 (It starts and works on Tomcat 6.x). I have pretty much come to the conclusion that it would not be wise to use WebSphere 6.1 + JSF 1.2 at all. The built-in JSF is in com.ibm.ws.webcontainer_2.0.0.jar which contains other ibm packages as well. I haven't yet tried to remove the built-in JSF impl 1.1 from my WebSphere installation - I don't think that one would get support from IBM if they would do so in a production environment. I find it strange that JBoss is describing a WebSphere deployment for it's Seam framework in http://docs.jboss.org/seam/2.0.3.CR1/reference/en-US/html/websphere.html Chapter 35 when it seems to cause major troubles. Since there have been a few months sÃnce this posting I'm corious if somebody has been successful with this one! Thanks, Martin [EMAIL PROTECTED] wrote: > > [EMAIL PROTECTED] schrieb: >> Hi, >> I'm using Tomahawk 1.1.6 on WebSphere 6.1 and does work correctly. But >> on the log I found: >> "Both MyFaces and the RI are on your classpath. Please make sure to use >> only one of the two JSF-implementations." >> I know that WAS has a JSF 1.1 implementation (Sun implementation) and my >> application classloader policy is PARENT-LAST. The question is: >> The log has an "ERROR" severity, so can this cause some problem? >> > > Having both on the classpath *is* a serious problem. You do need to > resolve this. > > Setting the classloader policy cannot solve this problem; that can > change which is *first*, but cannot make one of them invisible. So you > will need to either remove the websphere implementation, or overwrite it > with the myfaces one, or use some websphere-specific feature (if one > exists) to make the "built-in" lib invisible. > > There is some information on the wiki about configuring various > containers. The wiki can be found here: > http://wiki.apache.org/myfaces/ > > Regards, > Simon > > > ----- http://www.martinahrer.at/blog http://www.martinahrer.at/blog -- View this message in context: http://www.nabble.com/-Tomahawk----Both-MyFaces-and-the-RI-are-on-your-classpath-tp17340912p18924370.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
