The following information will save mylife :) I do not know where I got it (therefore sorry for not referencing it), but it would be useful if you think to make your code as an standalone jar file, having lots of different types of external libraries.
Within JDeveloper 10g it doesn't seem to be obvious on how to deploy a JClient application within a monolithic Java archive file that then can be used to run the JClient application on the client using java -jar The assumption that is made by the default deployment setting is that all dependency libraries are part of the classpath on the deployment platform, which means that only the application specific classes need to be deployed in the application's archive file. This assumption makes sense if you have more than one ADF JClient application that runs on the local client. To deploy JClient application so they run stand alone out of a jar file, with no additional setup required on the client machine, you need to add all the dependency classes to the application deployment jar, which quickly can become 17 MB in size due to this. Do as follows:
1) In the ADF JClient project, create a new JAR File deployment profile.
2) In the profile settings, for the JAR options, specify the name of the runnable class (to make a runnable jar file)
3) Create a new "Dependency Analysis" File group.
4) Select all the libraries from the Libraries tab on the Contributors page.
5) Make sure "Include Contents in Output" is checked. Otherwise the jar files of this libraries will be added, which is of no help at runtime.
6) Deploy the application to the jar file
7) Run the jar file, e.g: java -jar archive1.jar
Within JDeveloper 10g it doesn't seem to be obvious on how to deploy a JClient application within a monolithic Java archive file that then can be used to run the JClient application on the client using java -jar The assumption that is made by the default deployment setting is that all dependency libraries are part of the classpath on the deployment platform, which means that only the application specific classes need to be deployed in the application's archive file. This assumption makes sense if you have more than one ADF JClient application that runs on the local client. To deploy JClient application so they run stand alone out of a jar file, with no additional setup required on the client machine, you need to add all the dependency classes to the application deployment jar, which quickly can become 17 MB in size due to this. Do as follows:
1) In the ADF JClient project, create a new JAR File deployment profile.
2) In the profile settings, for the JAR options, specify the name of the runnable class (to make a runnable jar file)
3) Create a new "Dependency Analysis" File group.
4) Select all the libraries from the Libraries tab on the Contributors page.
5) Make sure "Include Contents in Output" is checked. Otherwise the jar files of this libraries will be added, which is of no help at runtime.
6) Deploy the application to the jar file
7) Run the jar file, e.g: java -jar archive1.jar
Posts
0 comments:
Post a Comment