jar conflict causing post-installation failure of contributor interface?
I've noticed several threads regarding new installations getting a blank page on the contributor interface!
The standard response has been to add a PRE_CLASSPATH statement with commons-lang-2.4.jar, which also appears in Oracle Support 1468392.1, but it is not working.
From what I've seen the following JARs are required to get the system started:
commons-lang-2.4.jar; log4j-1.2.16.jar; quartz-1.5.2.jar; jstl-1.1.2.jar; MSXML.jar
HOWEVER there seems to be an issue with the jstl-1.1.2 file. Without it the server always responds with 500 error, but when it is included the contribution interface doesn't render. Does anyone know more about it?