Probelm Description:
---------------------
Using Java Web start and when using 1.3
do not have any problems but when using 1.4 it
works fine for the first time as all the necessary jar files
are getting downloaded to the machine, but when trying to
execute it second time it throws an error saying
Java Web Start 1.2 Console, started Thu Nov 07 14:37:11 EST 2002
Java 2 Runtime Environment: Version 1.4.1_01 by Sun Microsystems Inc.
javax.xml.soap.SOAPException: Unable to create SOAP connection factory: Provider com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at com.tepin.st.conn.Connection.<clinit>(Connection.java:232)
at com.tepin.st.client.SOAPEventProcessor.<init>(SOAPEventProcessor.java:110)
at com.fmrco.gett.fdr.gui.LoginDialog$1.actionPerformed(LoginDialog.java:246)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
.....
We are currently using Java 1.3.1_02 on the server side and 1.4.0 on the client side.
The following problem is related to the client side:
It happens with any 1.4 JRE and later.
Test case file is available at
http://surveyor.red.iplanet.com/users/vk119745/publish/fidelity/63257192/
the file name is jnlp.tar.gz, Install Tomcat 4.0.6 on a machine and
extract the tar.gz file under webapps directory.
You have to modify the conf/web.xml and also this particular
applications xml file to include the following lines
<mime-mapping>
<extension>jnlp</extension>
<mime-type>application/x-java-jnlp-file</mime-type>
</mime-mapping>
You are all set with the application. Now install webstart on your local
machine and try accessing the file with the following link
http://<webserver>:8080/webstart/fdr-4.1.1.jnlp
I did get it to work (as a hack) by including the following files in my JRE lib/ext directory:
activation-1.1.jar
commons-logging-1.1.jar
jaxm-api-1.1.jar
jaxm-dom4j-1.1.jar
mail-1.1.jar
saaj-api-1.1.jar
saaj-ri-1.1.jar
If any one of these files isn't present, the app won't work. The exception is when the cache is cleared out and you launch again to reinstall the jars. Apparently the classpath that is used is different than when run the 2nd and later times.