The one in the JBoss 7 modules is the MyFaces implementation though, not Mojarra, right? In any case, it still has the com.sun.faces classes in it, so I don't see what the problem would be. Also, assuming Stefan is deploying a war, it should already include that module by default. For modules that aren't included by default, I think you just need the module name from the module.xml file. I have something like this in my pom.xml for the war build:
I don't actually have that dependency since for me, it's already implicitly there. I have other modules referenced though.
Peter Johnson wrote:They should be in modules\com\sun\jsf-impl\main\jsf-impl-2.1.3-b02-jbossorg-2.jar
Hmm, that file doesn't include a POM, so I'd have to dig further if you want the Maven coordinate...
The Maven co-ordinate is com.sun.faces:jsf-impl:2.1.3-b02-jbossorg-2. The reason why we had to have this JBoss specific version is because, late into the AS7 release cycle we ran into a bug in the JSF impl which would result in the (very common) xerces classcast exceptions if you had your own version of xerces packaged in a JSF2 application. The fix had to be done in the JSF impl and a patch has been provided to that project http://java.net/jira/browse/JAVASERVERFACES-2156. In the meantime, till that's integrated and released by that project, we had to use our own version of that library.
Stefan Ramirez
Greenhorn
Joined: Jul 10, 2011
Posts: 11
posted
0
That did the trick... thanks for the quick help!
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
