This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Adding external jars to java.class.path (IA classpath )
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 21, 2014
11:32 AM
Adding external jars to java.class.path (IA classpath )
Hi,
I am facing a problem of including jaxb jars in the installer classpath during runtime with java 1.5.
In pre-install section I am executing a custom plugin which uses jaxb. The code fails because it does not find the dependent jaxb jars
I am trying to find out if there is a way to add external jar path (and bundle alongwith the installer resources).
When I run the code I get the following exception.
Loading externalized properties
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 1 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 2 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 1 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 2 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
I tried using IA_CLASSPATH as well, but I am not able to bundle the jars with the resources so that it is available for use.
I want my console output to look like the following, where the jaxb jars are directly available under InstallerData
No Arguments
java.class.path:
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-api.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-impl.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\IAClasses.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\Execute.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData
C:\Documents and Settings\Administrator\Local Settings\Temp\I1400606464\Windows\InstallerData
ZGUtil.CLASS_PATH:
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-api.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-impl.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\IAClasses.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\Execute.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData
Is there any other way to add to the "lax.class.path" and make the jars available at runtime.
I am facing a problem of including jaxb jars in the installer classpath during runtime with java 1.5.
In pre-install section I am executing a custom plugin which uses jaxb. The code fails because it does not find the dependent jaxb jars
I am trying to find out if there is a way to add external jar path (and bundle alongwith the installer resources).
When I run the code I get the following exception.
Loading externalized properties
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 1 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 2 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 1 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
Execute Custom Code
java.lang.ClassNotFoundException: com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction 2 class com.installer.ia.action.ddinstallregistryxml.DDInstallRegistryXMLAction unavailable.
I tried using IA_CLASSPATH as well, but I am not able to bundle the jars with the resources so that it is available for use.
I want my console output to look like the following, where the jaxb jars are directly available under InstallerData
No Arguments
java.class.path:
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-api.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-impl.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\IAClasses.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\Execute.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData
C:\Documents and Settings\Administrator\Local Settings\Temp\I1400606464\Windows\InstallerData
ZGUtil.CLASS_PATH:
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-api.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\jaxb-impl.jar
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\IAClasses.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData\Execute.zip
C:\Documents and Settings\Administrator\Desktop\installer\InstallerData
Is there any other way to add to the "lax.class.path" and make the jars available at runtime.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 27, 2014
06:15 AM
Hi,
I think adding the jaxb jars to the dependencies list of the customcode action in installer IDE may resolve this issue.
- Usha.
I think adding the jaxb jars to the dependencies list of the customcode action in installer IDE may resolve this issue.
- Usha.