Velocity has a dependency on jakarta-commons-collections and jakarta-commons-lang. Bug #658926 added the dependency on jakarta-commons-lang but the same patch removed jakarta-commons-collections as an explicitly enabled jar in the web instance class loader because jakarata-commons-collections was being loaded by tomcat6 via the container class loader, it was felt this was redundant. The tomcat6 version of jakarta-commons-collections worked fine on Fedora because it was a current version. But on RHEL 6 the version of jakarta-commons-collections loaded by the container class loader is an older version (from tomcat5?). Velocity is loaded by the web app instance, the system version of jakarta-commons-collections should be available to the same class loader and not depend on the container class loader. The fix is add back the symlink to jakarta-commons-collections to the web app library directory. However, as per bug #665388 it's not sufficient to set up links to jakarta-commons-collections because the jar names have been renamed in F14 and above. Therefore the link creation logic in pkicreate needs to follow the model for other jakarata-commmons-* jars.
Created attachment 480262 [details] setup links to {jakarta,apache}-commons-collection.jar
Sending base/setup/pkicreate Transmitting file data . Committed revision 1863.