2 design questions:
i develop a webapp trying to keep it mvc clean. so, there are business beans and data access classes responsible for those beans-to-database relations (loading, storing, etc).
1. i've seen that some folks make the methods of the data access classes static and some others don't. what is the better solution? does static in this case means thread safe?
2. there is a chance that in the code i'll need a number of those data access methods in a sequence. taking in account that i use a connection pooling, would you make those methods receive a Connection object from outside (this way a number of methods will be executed with the same connection, but i'll have to leave all connection.close() bla bla bla stuff
out of the method scope) or would you put all of the db connection logic inside the methods (this way i'll have to take a new connection from the pool for each method and method...) ?
and, if you are in the "let's help this guy" mood, take a look at this : https://coderanch.com/t/358009/Servlets/java/architecure-dbcp
may be you'll give me a cool advice.