JDBC/Classpath--Urgent!!!!!!!!!!!!!! SOS

[Sanjeev Verma]

Dear friends
We are facing a problem in porting our web site to the server. The following are the issues we are facing:
1. The development environment we are using is JDK1.2/Oracle thin driver (Type 4) for JDBC/JavaWebServer2.0 for deployment. The Server on which our site is to be hosted is not dedicated to us alone. It already hosts a site using JDK1.3 environment. When we ported our site to the server, the pages (JSPs')were not able to connect to the database. On check we found that it is throwing a java.Security.AccessControlException: Access denied (java.net.SocketPermission database resolve) when the statement DriverManager.getConnection(......) gets executed. The relevant Oracle classes we were using are: classes111.zip, nls_charset11.zip.
2. For debugging, we created the same environment internally and found that jdk1.3 creates this conflict.
Has anyone faced this before? Any solutions?
We are trying to approach this problem from two perspectives:
1. Search the right Oracle classes and deploy them. We downloaded classes12.zip and nls_charset12.zip and deployed them, using jdk1.3 environment. It didn't work.
2. Can two applications run on the same machine, using different path and classpath variables. If so, how.
Please respond ASAP.
Thanx in advance
Sanjeev

[Harish Kashyap]

hi
i haven't faced this problem before but i'm sure that if this problem is just due to the version conflict then it can be solved using the java's policytool.
try setting policies using policytool present in jdk/bin dir.
give permissions to your files
then try

let me know whether it works or not.
harish

[mohit joshi]

I have a few suggestions you can try, although I am not sure if these will work
a)In the Property file (not backup file)
JavaWebServer2.0\properties\server\adminserver\server.properties
change the following setting to false.
# Use servlet security manager?
server.security=true
b) in the following JDK file
D:\jdk1.2.2\jre\lib\security\java.policy

add these two lines in the end:
permission java.security.AllPermission "*", "read";
permission java.security.AllPermission "*", "write";
This as you can make out, would allow all read write permissions to every one, which could be a security hole. but you can try it.

I havent worked on 1.3 so I have no Idea why you might be having this problem with it.
at a time only one classpath is supported by the Operating system.
HOH
Mohit Joshi