(Not So) Stupid Questions 21: All Statics
Editor's note: Sometimes the most interesting discussions begin when someone says, "This may be a stupid question, but ...." If the person asking the question has taken the time to think about the problem before asking, the question is often not stupid at all. The uncertainty points out an ambiguity in the specs, holes in the docs, or a search for how more experienced programmers might address a particular problem. From time to time, we will print one of the "(Not So) Stupid Questions" we receive and invite our readers to answer the question in the feedback section.
Remember that new people are joining the Java community all the time and may be looking for help from those with more experience. Also, those who began with Java as their first language can benefit from those coming to the community with experience in other languages. As always, answer the questions with kindness. You are also welcome to submit your questions to
This may be a stupid question, but ... "Is it a bad idea to make all our methods
I have a question that I am very confused about, and I don't know how it is affecting my application. We have one application that uses Struts.
In the DAO, where we write the business logic, we made all the methods
By definition, statics are called by their class name, so in our Action and DAO classes, we just call these static methods.
is this a good approach? If not, what would work better?
|width="1" height="1" border="0" alt=" " />|