So people are probably going to tell me this is a bad idea, but I\'d like to at least give it a go.
EDIT The intention of this app is that it can o
:) yes, I'm one that'll tell u it is a "bad" idea. IMHO, given that Android apps are intended to run on mobiles where connectivity might be an issue or be lost temporarily, I claim each good app should have some degree of offline capabilities. So you'd implement some very basic sync mechanism - as for instance demonstrated with the SampleSyncAdapter - which synchronizes with the apps local SQLite db.
I think this is the best way to go (also for the user experience).
Oracle has a product that provides both data sync with Oracle DB as well as offline capabilities; it's called Mobile Server
They way it works is, you just store your data in SQLite, and the Oracle client will handle sync. Of course you have to install and configure mobile server, and each new device will need to be provisioned, but once that is done, it "just works!"
There is a download tab in the link above, you can download and try it out of you like.
I hope that helps. Good luck with your problem.
Regards
Eric, Oracle PM
Have you added in the AndroidManifest.xml the
uses-permission android:name="android.permission.INTERNET"
I've to create an app with the same constraint of connectivity and database. I've done this, and I've a lot of Exception (ArrayIndexOutOfBound during the connexion to the database.)
I use ojdbc14.jar for that. So, I "just have to" fix the Exception I have, and it would be OK...
For more information, see this topic
Another and much easier approach is to use a Virtual JDBC Driver that relies on a secure three-tier architecture: your JDBC code is sent through HTTP to a remote Servlet that filters the JDBC code (configuration & security) before passing it to the Oracle JDBC Driver. The result is sent you back through HTTP.
There are some free software that use this technique. Just Google "Android JDBC Driver over HTTP".
Sorry to revive an old thread but I had this problem for a long time and finally fixed it. Just run eclipse or whatever you're developing in "as administrator" and the error will go away.