U may get stuck even after using the right drivers, once the applet is viewed over the web, by users outside ur immediate network. This may happen simply because the firewalls are likely to block any kind of traffic other than http.
The best solution for applet database communication in these cases would be to use http calls from applet code to invoke servlets that wud do the job for connecting to the database , getting the results and returning them, which ur applet can display.
Of course if ur applet is always going to run within your intranet where firewall restrictions may not apply using the right driver will do ur job. In case of Oracle db u wud go for Oracle thin driver (a type 4 driver.)
Main Topics
Browse All Topics





by: objectsPosted on 2003-02-10 at 18:06:19ID: 7922387
the default permissions of an applet only allow it to use type 3 or 4 drivers.
By the looks of it you are using the odbc-jdbc bridge which is not of type 3 or 4.
To fix it you need to either use a different (type 3/4) driver, or sign the applet to allow the user to grant required permissions.