Skip to main content

J2ME Database Handling

I am developing a J2ME application and have no idea how to connect it with the database. I tried it doing, as given in some books but was unsuccessful. I included the following code in the constructor of MIDLET class

String url = "jdbc:odbc:db1";
String userID = "cse1";
String password = "jss";
Statement DataRequest;
ResultSet Results;
Connection Db;
try {
Class.forName( "sun.jdbc.odbc.JdbcOdbcDriver");
Db = DriverManager.getConnection(url,userID,password);
}
catch (ClassNotFoundException error) {
System.err.println("Unable to load the JDBC/ODBC bridge." +
error);
System.exit(1);
}
catch (SQLException error) {
System.err.println("Cannot connect to the database." + error);
System.exit(2);
}
try {
String query = "SELECT * FROM login";
DataRequest = Db.createStatement();
Results = DataRequest.executeQuery (query);
//Place code here to interact with the ResultSet
DataRequest.close();
}
catch ( SQLException error ){
System.err.println("SQL error." + error);
System.exit(3);
}
Db.close();

I included the "javax.sql" package also, but the emulator does not recognise this package and an error message saying that "this package does not exist" .

I would also like to know the use of TOMCAT server while developing a mobile connection or while accessing the database.

plzzz help as soon as possible.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

You seem to be having a bit of an architectural issue more so than a java/jdbc problem.

If you do have a JDBC driver and a DB running on the device, you can connect to it... It's unlikely to be a JDBC-ODBC bridge, however. If you have a remote DB, the JDBC connection is probably an expensive way to connect from your device to the DB. Regardless, you have to have at least the database's driver installed on your device.

As far as tomcat: what are you trying to do? Are you trying to create a web application that you can surf on your cell phone? Then, from tomcat's viewpoint, it's the same as developing any other web application, except, when you write your markup, it may not be HTML, but WML or CHTML, or some other markup generated by your JSPs/Servlets. Your web application will be connecting to the DB.

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol