FYI: Deploying Infobus Applet

Question

This is a response to multiple posts on problems with deploying
the Infobus Applet tutorial.
When you create your applet.jar file, here are some explicit
steps to follow when using the Deployment wizard, followed by
some general notes on deploying applets:
1. Select Project->Deploy->New Profile from the menu.
2. Click Next to get past the Welcome page, then accept the
default 'Deploy to Simple Archive' and click Next.
3. On the Rules page, click << to shuttle all the rules back to
the left. We won't use the rules, but will explictly select
which source files to include from our project on the next page.
Click Next.
4. On the Sources page, select your HTML file, XML file, and
Applet java file and click > to shuttle them over to the right.
Click Next.
5. Here is where things get tricky in the deployment phase. For
this specific tutorial. You do NOT want to include dependency
classes in your archive since you will deploy those separately.
Therefore, you want to ADD the oracle.dacf, oracle.jbo and javax
packages to the list of packages to EXCLUDE from the archive:
a. Click the Exclude button to display a list of packages.
b. Expand the oracle node and select the dacf subnode.
c. Click OK. Notice that oracle.dacf is added to the list of
packages to exclude from your archive.
d. Repeate a-c for oracle.jbo and javax.
e. The exclusions list on the Dependencies page should now
include oracle.dacf, oracle.jbo and javax (in addition to the
original default values)
f. Click the Preview button to show what will be included in
your archive. It should ONLY show your .class, .xml and .html
files from your project, a connection.properties file and the
manifest.
6. Click Next.
7. Enter a name for your archive jar file and click Finish to
generate it. Click Yes when prompted if you want to deploy now.
Copy the .jar file and each of the .jar/zip files listed in the
tutorial to your webserver. If the .jars will reside in a
different directory than the HTML file that calls the applet,
then you need to set the CODEBASE tag accordingly (relative path
from the HTML file to the archives).
Most of the archives you need to deploy are in the redist
directory. The classes111.zip file you deploy depends on which
driver you used, but by default will be in jdbc/lib/oracle8.1.5.
Basically, you want your applet archive file to contain ONLY the
class and xml files for your applet, and you want to deploy all
other 'referenced' archives separately (and list each of them in
the ARCHIVE tag of your applet's HTML file). This provides a few
benefits:
* your applet archive is much smaller because it doesn't
include all referenced class files
* if you have multiple Infobus applets, you only have to deploy
the commonly referenced archives once, not package them with each
applet and deploy them over and over which takes up space on the
server
As a side affect of the above deployment strategy, you have to
explictly tell the deployment wizard to EXCLUDE these referenced
packages that it would normally try to include in your archive.
That is accomplished on the Dependencies page of the wizard as
described above.
The Preview button will show you what is included. From there,
you can determine which packages to Exlcude. Keep checking the
Preview list to make sure you have stripped it down to the bare
minimum.
Hope this helps some.
L
null

Answer 1

Hong,
Are you using an internationalized operating system and/or
Browser? This appears to be related to a Resource file which
contains translated strings.
L
Hong (guest) wrote:
: Hi,
: I did the same way as you mention below. I get this following
: error message. I guess it couldn't find this class. I don't
even
: know where I can find this class.
: Thanks
: Hong
: These are the error message:
: Opening
http://web/java/oracle/dacf/dataset/ResTable_en_US.class
: no proxy
: java.lang.ClassFormatError: oracle/dacf/dataset/ResTable_en_US
: (Bad magic number)
: at java.lang.ClassLoader.defineClass0(Native Method)
: at java.lang.ClassLoader.defineClass
: (ClassLoader.java:403)
: at java.security.SecureClassLoader.defineClass
: (SecureClassLoader.java:101)
: at sun.applet.AppletClassLoader.findClass
: (AppletClassLoader.java:144)
: at java.lang.ClassLoader.loadClass(Compiled Code)
: at sun.applet.AppletClassLoader.loadClass(Compiled Code)
: at java.lang.ClassLoader.loadClass(Compiled Code)
: at java.util.ResourceBundle.findBundle(Compiled Code)
: at java.util.ResourceBundle.getBundle(Compiled Code)
: at java.util.ResourceBundle.getBundle
: (ResourceBundle.java:334)
: at oracle.dacf.dataset.Res.<clinit>(Res.java:16)
: at oracle.dacf.dataset.SessionInfo.<clinit>
: (SessionInfo.java:59)
: at package1.Applet1.<init>(Applet1.java:207)
: at java.lang.Class.newInstance0(Native Method)
: at java.lang.Class.newInstance(Compiled Code)
: at sun.applet.AppletPanel.createApplet
: (AppletPanel.java:532)
: at sun.plugin.AppletViewer.createApplet
: (AppletViewer.java:759)
: at sun.applet.AppletPanel.runLoader(AppletPanel.java:468)
: at sun.applet.AppletPanel.run(Compiled Code)
: at java.lang.Thread.run(Thread.java:479)
: JDeveloper Team (guest) wrote:
: : This is a response to multiple posts on problems with
: deploying
: : the Infobus Applet tutorial.
: : When you create your applet.jar file, here are some explicit
: : steps to follow when using the Deployment wizard, followed by
: : some general notes on deploying applets:
: : 1. Select Project->Deploy->New Profile from the menu.
: : 2. Click Next to get past the Welcome page, then accept the
: : default 'Deploy to Simple Archive' and click Next.
: : 3. On the Rules page, click << to shuttle all the rules back
: to
: : the left. We won't use the rules, but will explictly select
: : which source files to include from our project on the next
: page.
: : Click Next.
: : 4. On the Sources page, select your HTML file, XML file, and
: : Applet java file and click > to shuttle them over to the
: right.
: : Click Next.
: : 5. Here is where things get tricky in the deployment phase.
: For
: : this specific tutorial. You do NOT want to include
dependency
: : classes in your archive since you will deploy those
: separately.
: : Therefore, you want to ADD the oracle.dacf, oracle.jbo and
: javax
: : packages to the list of packages to EXCLUDE from the archive:
: : a. Click the Exclude button to display a list of packages.
: : b. Expand the oracle node and select the dacf subnode.
: : c. Click OK. Notice that oracle.dacf is added to the list
: of
: : packages to exclude from your archive.
: : d. Repeate a-c for oracle.jbo and javax.
: : e. The exclusions list on the Dependencies page should now
: : include oracle.dacf, oracle.jbo and javax (in addition to the
: : original default values)
: : f. Click the Preview button to show what will be included
in
: : your archive. It should ONLY show your .class, .xml and
.html
: : files from your project, a connection.properties file and the
: : manifest.
: : 6. Click Next.
: : 7. Enter a name for your archive jar file and click Finish to
: : generate it. Click Yes when prompted if you want to deploy
: now.
: : Copy the .jar file and each of the .jar/zip files listed in
: the
: : tutorial to your webserver. If the .jars will reside in a
: : different directory than the HTML file that calls the applet,
: : then you need to set the CODEBASE tag accordingly (relative
: path
: : from the HTML file to the archives).
: : Most of the archives you need to deploy are in the redist
: : directory. The classes111.zip file you deploy depends on
: which
: : driver you used, but by default will be in
: jdbc/lib/oracle8.1.5.
: : Basically, you want your applet archive file to contain ONLY
: the
: : class and xml files for your applet, and you want to deploy
: all
: : other 'referenced' archives separately (and list each of them
: in
: : the ARCHIVE tag of your applet's HTML file). This provides a
: few
: : benefits:
: : * your applet archive is much smaller because it doesn't
: : include all referenced class files
: : * if you have multiple Infobus applets, you only have to
: deploy
: : the commonly referenced archives once, not package them with
: each
: : applet and deploy them over and over which takes up space on
: the
: : server
: : As a side affect of the above deployment strategy, you have
to
: : explictly tell the deployment wizard to EXCLUDE these
: referenced
: : packages that it would normally try to include in your
: archive.
: : That is accomplished on the Dependencies page of the wizard
as
: : described above.
: : The Preview button will show you what is included. From
: there,
: : you can determine which packages to Exlcude. Keep checking
: the
: : Preview list to make sure you have stripped it down to the
: bare
: : minimum.
: : Hope this helps some.
: : L
null