1 of 1 people found this helpful
2.1.7-jbossorg-2 ist the name of the file, the version shown on startup is 2.1.7-jbossorg-1.
It's a 2.1.7.x. The base is mojarra 2.1.7, some bugifxes where added to it.
But as far as I know, only bugfixes, no features or changes which break the compability or APIs of mojarra.
So a downgrade, why ever, should be feasible.
Packaging the jars with your application is possibly not feasible with this version.
As far as I remember there were some problems which got fixed later.
IIRC, the JBoss specific changes related to certain classloading fixes in that impl. I think there was even a patch that Jason submitted to the Mojarra team for this. Although, I'm not 100% sure whether it was for JSF impl or xerces (or both).
Thanks for the info, do you know where the bugfixes could be viewed? Are they filed under JBAS or JBossWeb?
The customization we made was in response to this bug:
As you can see, that bug was fixed in 2.1.8. So going forward from there, the only changes we make are:
- Break Mojarra into API and IMPL modules
- Adjust the version number shown during initialization
For the build, we also add an ant task called "split-impl" that does the break between API and IMPL.