Java, JSP, Servlet, JDBC - Back To The Basics Part 2

By Angsuman Chakraborty, Gaea News Network
Monday, January 9, 2006

I informed in my previous post that I have decided to shun all java frameworks for my current project and develop with basic Java / J2SE components instead. Here is a synopsis of my journey as it is unfolding.

Today I was working with JDBC, doing the simple job of fetching certain data from the web and dumping them in the database. I have to tell you that Hibernate or at least iBatis sounded very alluring. But I have decided - no framework. So I wrote some simple code to fetch data from the web, parsed it and dumped in using plain old JDBC (JDBC 1.0). I was thinking of using connection pooling from JDBC 2.0, but frankly for my fetch and dump operation, it appeared to be overkill.

I got lot of work done today. The only dragging force was the constant temptation to use some framework or other. I resisted. It was refreshing. Hopefully from the next post I will start posting few bits and pieces of code, but frankly I have not using anything spectacular today - just plain old JDBC. Only thing worth noting was that I used a Proxy to allow me to login the database statements. I am using HSQLDB for this project. It can currently handle 8GB of data which is good enough for my needs.

March 6, 2009: 5:50 pm

i need the lectural material of jsp,servlet ,jdbc

Jim Bennett
March 1, 2006: 10:24 am

Not using a pre-made framework simply means that you are creating your own ad-hoc framework as you write your application. Either that, or you are coding the same idiom over and over. For example, sticking with the JDBC-only approach is fine when you’re accessing only one database table, but as soon as you have to access a second table, you’re writing essentially the same code again. Refactor out the common code into a reusable class, you say? Then you’re on your way to inventing your own framework.

January 11, 2006: 7:30 am

Just pay attention to some web components like
our (of course :-) Coldtags suite:

will not be displayed