[3.2.4] jchemstreams.war problem

I'm encountering jchemstreams.war problem when I test the connection to Oracle. I've used the jchemstreams.war from version 3.2.3 and every is OK. Libraries are 3.2.4 but jchemstreams.war is 3.2.3.

I assume you want to upgrade from 3.2.3 to 3.2.4.





Have you replaced the jchem.jar in Tomcat as well?

Upgraded everything in both database and tomcat with 3.2.4 but using jchemstreams.war from 3.2.3.

Do you mean that when running the test.sh script you do not get something like:

Code:

18:46:28 SQL> JCHEM_CORE_PKG.GETENVIRONMENT() -------------------------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi PL/SQL Release 10.2.0.1.0 - Production CORE    10.2.0.1.0      Production TNS for HPUX: Version 10.2.0.1.0 - Production NLSRTL Version 10.2.0.1.0 - Production NLSRTL Version 10.2.0.1.0 - Production JChem version in the database: 3.2.4 JChem version in the Tomcat server: 3.2.4 java.vm.version: 1.5.0.05 jinteg:10.17.06-10:03 IA64W java.vm.vendor: Hewlett-Packard Company Apache Tomcat/5.5.20 JCHEM_CORE_PKG.GETENVIRONMENT() -------------------------------------------------------------------------------- Major JDBC version in Tomcat: 10 Minor JDBC version in Tomcat: 2

?


Instead, you get error message similar to the following:

Code:

INCONSISTENT JCHEM VERSIONS: JChem version in Oracle: 3.2.4 JChem version in servlet: 3.2.3

Is this correct?

The problem I encountering is with the jchemstreams war file. After deploying the 3.2.4 jchemstreams.war file to tomcat and then updating the security access setting in the web.xml. I called the configure JChem page on the web. I put my connection information into the configuration web page and attempt to test the connection. This throws and exception and is displayed on the web.





The jchem libraries are the same on tomcat and the database. This is solely a jchemstreams problem that I'm encountering. I've overcome this problem by using the jchemstreams.war file from 3.2.3 release and my problems go away.

indeed

The problem is with the connect.jsp page. I uploaded a fixed version.





I also uploaded an improved version of edit.jsp as well (for improved navigation).





The fixed versions will be included in the next release.