type 4 JDBC driver, intranet, 1.3 plug-in, is policy file required?

[rr]

Hello Associates,
I need some advice. Your help would be most appreciated.
I am trying to test an applet. I am running an oracle thin JDBC driver
classes111.zip, running jre1.3 plug-in to Netscape and Opera, intranet,
all classes jar'd and downloaded by the applet from the intranet web
site, which is the same machine running the database. I am registering
the driver correctly.
However, I am getting a AccessSecurityException -- unknown source
(output below). If a policy file is required, can one side step this
issue by using IIOP or CORBA?, or would one not want to (why)? Does
everyone install the plug-in or every browser and install a policy file
for every user under the browser to use JDBC on 1.3? Does anyone have
any other suggestions?
Rachel Rainey

detailed output of exception:

Java(TM) Plug-in: Version 1.3.0_01
Using JRE version 1.3.0_01 Java HotSpot(TM) Client VM
User home directory = C:\WINDOWS\Profiles\oracle

Proxy Configuration: no proxy

java.security.AccessControlException: access denied
(java.lang.RuntimePermission modifyThreadGroup)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at sun.applet.AppletSecurity.checkAccess(Unknown Source)
at java.lang.ThreadGroup.checkAccess(Unknown Source)
at java.lang.Thread.init(Unknown Source)

[JAG]

Editing the policy file maybe the easiest thing to do for testing an applet.
Going beyond the test phase, you have to consider the effort to support your
applet users.

Something to consider: if you have access to the web server, convert the
applet to a Java servlet. This will elminate the policy issue and not
require interaction with your users. Servlets that access databases and
produce HTML results are pretty straightforward.

Regards,
Frank

[rr]

Unfortunately, I need to stick with an applet to display the results, as this
applet will probably be incorporated with another existing applet at a later
stage. It also displays elaborate swing tabsets of results.

Maybe I have set up something incorrectly. I have the drivers, swing classes and
applet classes jar'd and sitting in the html directory where the html file sits
under the httpd directory on the server. If I have something wrong here, maybe
that is the solution, which would be better in the short term.

Otherwise if IIOP or an ORB solution would work, I would be interested in trying
that. I am not sure but I think that if the Oracle database was moved to another
location, or possibly even if the oracle tables were links to another Oracle
database on another machine other than the web server, problems with JDBC may
arise.

Thanks,
Rachel