My team is in the process of building a web application. Currently the Controller Servlet calls the appropriate Action Class. This Action Class does what ever is necessary (update data, query, validate, etc.) and stores the information that needs to be displayed in JavaBeans. When completed the Action class returns the location of the JSP page to be displayed. My problem is all my database access goes through one singleton class, which uses connection pooling. The run-time performance of this class is fine, but with multiple developers everyone want to access this file at the same time. :(
My question is how do others transfer information between a database and JavaBeans. Some topics I have run across while surfing and my thoughts. ** Enterprise Java Beans - no in-house knowledge, so we would be learning from the ground up. Do we need a server? Are they tough to code? How to get info from there to JavaBean for use in JSP? ** Placing function in each JavaBean to retrieve information from the database and save info to the database. - Some questions on using the connection pooling, but I think I could work through this. Is it still a JavaBean if I do this (add a populate and commit methods). ** Others but nothing that I can think of right now. I am open for suggestions. Actually what I would really like is a location online where I can research this a bit more. Thanks, ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
