Web start fires up the installer twice

Question

All
We are seeing some issues where java web start is invoking the installer twice for some reason instead of once.
When we install the application using the installer it installs correctly and everything looks good .But whenever the user clicks on the shortcut icon it tries to install the application again by downloading all the jar files and gets the installer screen again .This happens twice but im not sure why.
I tried this on two JRE .14 and .15 and both had same problems.
Im pasting the two JNLP files we are using . The first JNLP is the main jnlp file which refers to the installer jnlp using the extension tag.
-----------------------------------------------------------Main JNLP-----------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<jnlp codebase="$$context/CCA" href="$$context/CCA/AuthoringLaunch.jnlp">
<information>
     <title>Sample Learning Studio</title>
     <vendor>Sample Corporation</vendor>
     <description>Sample</description>
     <icon href="$$context/CCA/resources/images/desktopIcon.png"/>
     <icon kind="splash" href="$$context/CCA/resources/images/splash-screen.png"/>
     <offline-allowed/>
     <shortcut>
               <desktop/>
               <menu submenu="Sample Learning Studio"/>
     </shortcut>
</information>
<security>
<all-permissions/>
</security>
<update check="always" policy="prompt-update"/>
<resources os="Windows" arch="x86">
     <nativelib href="$$context/CCA/lib/swt-3.5M1-win32-win32-x86.jar" download="eager"/>
     </resources>
<resources>
     <j2se version="1.6+"/>
     <jar href="$$context/CCA/lib/jna_WindowUtils.jar" download="eager"/>
     <jar href="$$context/CCA/lib/jna-3.0.7.jar" download="eager"/>
          <jar href="$$context/CCA/lib/MozillaInterfaces-1.8.1.3.jar" download="eager"/>
          <jar href="$$context/CCA/lib/derby.jar" download="eager"/>
          <jar href="$$context/CCA/lib/ibatis-2.3.0.677.jar" download="eager"/>
          <jar href="$$context/CCA/lib/xml.jar" download="eager"/>
          <jar href="$$context/CCA/lib/activation.jar" download="eager"/>
          <jar href="$$context/CCA/lib/mail.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringBuisnessObjects.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringBrowser.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringCore.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringCourse.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringCommands.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringComponents.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringDataObjects.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringDb.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringExceptions.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringLogger.jar" download="eager"/>
     <jar href="$$context/CCA/lib/AuthoringLicense.jar" download="eager"/>
     <jar href="$$context/CCA/lib/AuthoringMain.jar" main="true" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringRequestBeans.jar" download="eager"/>
     <jar href="$$context/CCA/lib/AuthoringUtils.jar" download="eager"/>
     <jar href="$$context/CCA/lib/resources.jar" download="eager"/>
          <extension name="AuthoringInstaller" href="$$context/CCA/lib/AuthoringInstaller.jnlp"/>
     <property name="application.context" value="$$context"/>
</resources>
     <application-desc main-class="com.sample.authoring.main.ApplicationMainLaunch"/>
</jnlp>
-----------------------------------------------------------Main JNLP-----------------------------------------------------
Here is the installer JNLP file
--------------------------------------------------------------Installer JNLP-----------------------------------------------------
<jnlp codebase="$$context/CCA/lib" href="$$context/CCA/lib/AuthoringInstaller.jnlp">
<information>
<title>Sample Learning Studio</title>
<vendor>Sample Corporation</vendor>
<description>Installer</description>
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<resources>
     <j2se version="1.6+"/>
<jar href="$$context/CCA/lib/resources.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringExceptions.jar" download="eager"/>
          <jar href="$$context/CCA/lib/AuthoringLogger.jar" download="eager"/>
     <jar href="$$context/CCA/lib/AuthoringUtils.jar" download="eager"/>
<jar href="$$context/CCA/lib/AuthoringInstaller.jar" main="true"/>
<property name="deployer.context" value="$$context"/>
<property name="deployer.codeBase" value="CCA"/>
<property name="deployer.configFile" value="deploy.xml"/>
<property name="deployer.configDir" value="conf"/>
</resources>
<installer-desc main-class="com.sample.authoring.installer.InstallationWizad"/>
</jnlp>
--------------------------------------------------------------Installer JNLP-----------------------------------------------------
I'm not sure why the installer was getting fired twice .
To solve this problem i tried to update      <shortcut> tag to have a online attribute <shortcut online="false">
By doing this it prevented the installer from firing up twice but it alerts the user with another alert which tells "The application has requested to go online ".
Can someone let me know why this would happen.
Also let me know if there is a way to have java web start application always launch offline and check for updates?
Thanks
Chetan

Answer 1

In this very same forum BenGlacy said he got there (no online launch and check for update) by removing the jnlp href attribute.
Anyway there's something that doen't make sense in your post
Chetan_Loves_Java wrote:
When we install the application using the installer it installs correctly and everything looks good You don't install using an installer, it's meant to execute una-tantum tasks before app's first launch. If your installer does anything different, that could be the reason of your problems. By the way, in Java Web Start you don't install (period), you launch.
If you, instead, mean the javaws -install option, please check all hrefs in JNLPs and look for 'twin' entries in your cache (javaws -viewer), resources are chached by URL, even the slightest difference can make them appear like 2 different voices.
Application tries to go online 'cause it has an absolute href (instead of one relative to the codebase), althought, I gotta say, you may find in this forum that absolute href happened sometime to solve some problems. About this, why are you using absolute path (repeating codebase) on every resource (afaik, this never solved any probleam)?
Bye.