Re: applicability of static methods in web applications?

From:

"Daniel Pitts" <googlegroupie@coloraura.com>

Newsgroups:

comp.lang.java.programmer

Date:

5 Apr 2007 17:02:16 -0700

Message-ID:

<1175817736.523238.267450@n59g2000hsh.googlegroups.com>

On Apr 5, 1:34 pm, "vishist" <vishi...@gmail.com> wrote:

Hi,
For my project, I see that some people use static methods for the
web-application in DB layer.

eg:

public static List getId(){
return list;

}

Now, I know that this method works in a threaded environment since all
these methods fall in thread scope. But coding like this defeats the
whole purpose of choosing a object oriented language. I'm confused
here whether it is a good style or not.

You comments are really appreciated..

V.

I personally think its quite bad style. There are, however, some
limitations with standard servlets, it is often easier to have static
utility methods.

I've actually gone as far personally to create a wrapper object when
contains a request, and all sorts of other information, and have that
object handle the business logic. Only in a couple Tag classes (where
its unavoidable) do I access anything static or at an application
scope. and in those cases its usually to access a factory object
which has been configured through Spring (IoC is the way to be)