well that is just horrible then.
A Weblogic domain is similar to a JBoss server configuration - it is a self contained server instance.
I was going to suggest creating a new domain for the other apps that use a different of JSF library, but apparently the JAR must reside in the
domains sharedlibrary which sounds like is equivalent to the %JBOSS_HOME%\lib directory.
It sounds like there are several problems/issues with JSF/Seam and Weblogic unfortunately, according the Seam 2.1.x ref doc...
When you say
other third party ears using different JSF componentswhat does that mean exactly?
Different implementation of JSF? (like MyFaces instead of Sun RI?)
When I say
other third party ears using different JSF components, I'm talking about a third party ear that I need to deploy on the same weblogic cluster as my Seam application and which uses a different version of JSF (1.1 in that case). And I cannot simply open that third party ear and modify the war to use JSF 1.2 because it is a third party ear not maintained by me.
The latest Seam uses JSF 1.2. Apparently I could use JSF 1.1 in my Seam application but that would affect my middle tier which relies on EJBs now. So I'm not considering this option.
What is annoying is that jar file (javax jsf 126.96.36.199.jar) that needs to sit on the domain shared lib.