Beginning with Sun Identity Manager Version 7.1, a sealing violation exception occurs in the application server log when you use Waveset with Oracle 10g on Sun Java System Application Server Enterprise Edition 8.2.
This exception generally occurs if you are using more than one Java Archive file (JAR file) containing Oracle JDBC drivers.
To prevent this problem, be sure the CLASSPATH contains only one JDBC driver JAR file, and that you use the ojdbc14_g.jar provided with Oracle 10g. In addition, you must use the ojdbc14_g.jar provided by the Oracle 10g installation to ensure correct operation.
Waveset depends on, and includes, some jar files that may also be provided by the application server, which can cause a conflict.
For example, an error can result when you deploy:
Sun Identity Manager 8.1 on jBoss
Sun Identity Manager 7.0 on Apache Tomcat 4.1
Tomcat ships with a commons-logging jar file in $TOMCAT_HOME/server/lib/commons-logging-1.1.jar and Identity Manager 7.0 ships with a commons-logging file in $TOMCAT_HOME/webapps/idm/WEB-INF/lib/commons-logging.jar.
The version of the jar file provided by the application server must be newer than the one provided by Waveset. To determine which jar file is newer, inspect the Specification-Version and Implementation-Version meta tags in the META-INF/MANIFEST.MF file.
If you deploy Waveset on certain application servers and errors result, you can remove the Waveset commons-*.jar files from the Waveset WEB-INF/lib directory to fix the problem.