Hi Ahamed, can you please be a little more specific? What do you mean "this" open source project? Do you mean that you have read or heard of an open souce project for JDBC involving javabeans? Sorry, but your question is dificult to understand. -Barry
Hi Barry, Actually I have to develope java beans componenets to communicate with data base server. So I need how java beans communicate with Data Base so I think i should use JDBC API for communicating with that. or Connecter/J for JDBC driver??. So I am looking any open source project concerning this task or any links. This components will serve as a web services later part.
I am using Tomcat with Axis , OS MS2000, MySQL DB. Thanks, Fyrose.
Originally posted by Barry Gaunt: Hi Ahamed, can you please be a little more specific? What do you mean "this" open source project? Do you mean that you have read or heard of an open souce project for JDBC involving javabeans? Sorry, but your question is dificult to understand. -Barry
Ahamed, I recommend checking out the Spring application framework at http://www.springframework.org This collection of frameworks provides a nice JavaBean container and some really handy stuff that greatly simplifies using JDBC. It also has a lots more stuff for working with J2EE including an excellent web application MVC framework. kktec SCJP1.4 & SCWCD BTW, I answered this post in the Java in General (advanced) forum. It's best to avoid cross-posting.
kktec<br />SCJP, SCWCD, SCJD<br />"What we observe is not nature itself, but nature exposed to our method of questioning." - Werner Heisenberg
May I ask why you need JavaBeans? The software products you describe are completely independent of JavaBeans, so I guess there must be some other reason. If it is your choice to use JavaBeans, please be clear about what they are good at, and what they are not. JavaBeans is a component technology with two main aims: To allow a "bean container" to automatically provide a user interface for customising objects after they have been created, and to allow these objects to be serialized to some sort of offline storage (a disk, a database, another machine, whatever). Typical database-backed web applications have little or no use for these features, and the overhead required to conform to the JavaBeans "patterns" simply gets in the way. If your task is actually to write a JavaBean class which provides database access functionality in someone else's bean container, you will surely need to use JDBC. I can't see that Tomcat or Axis have anything to do with the task, though. If you can clarify your need any more I'm sure we would be able to be more help.