Re: applicability of static methods in web applications?
Arne Vajh?j wrote:
vishist wrote:
Things are working at our end (though it might be absurd). The
variables declared in static method fall under thread scope right?.
The DB Connection, statement, resultset all fall in the same static
method.
public static List getMyResultSet(){
Connection conn = getConnection();
PreparedStatement pStatement = conn.prepareStatement();
ResultSet rSet = pStatement.executeQuery();
List resultSetObjectList = new ArrayList();
...................
...................//Populating resultSetObjectList here
...................
return resultSetObjectList;
}
this is how our code is written and is working now. We invoke these
methods statically from the servlet prefixing the Class name. I know
that this is not a good style. Infact that was my question:
----isn't there any steadfast rule that says you shouldn't create
static methods that has business logic in them?.
That use of static is fine.
I am no aware of any rule that prohibits business logic
in static methods.
But even if there were then the code above is not business
logic !
The code is very similar to code in MS DAAB.
Arne
The thing is that as the past posts explain, they are introducing kind
of tight coupling across the system. Now, I saw another application that
they are using patterns to get an instance of the object and then use it
to save/update/delete in the client object. I know that its a personal
flavor thing to choose the path of implementation. But then when so much
is going on Patterns, abstractness why is that its being implemented
like this? Is there any good reason for this?
vishist.