06, 2003 11:50 AM
Subject: Re: [Hibernate] Unit Testing With ThreadLocal Sessions
>
>
>
> > I don't close the session at all in any of my business logic methods. In
> > deployment, a servlet filter _always_ closes the session at the end of
the
>
> It looks lik
alized once, and that your
sessions are closed in some other way (like in the Junit tearDown()
method.
Eelco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Matthew E. Porter
Sent: woensdag 6 augustus 2003 15:59
To: Joseph Fifield
Cc: [EMAIL PROTECTED]
Su
My only concern with this is that the business logic component is now
coupled with the web tier. For this project (which is basically a
framework), we want to be able to use the components internal and
external to the servlet container. However, I do appreciate the
feedback! It helps con
I don't close the session at all in any of my business logic methods. In
deployment, a servlet filter _always_ closes the session at the end of the
request. For unit testing, I have a base test case class that does the same
thing in the tearDown() method. That way, each test case can execute in the
quests
per second without any real dips.
Hope that gives you confidence ;)
Eelco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Juozas
Baliuka
Sent: woensdag 6 augustus 2003 17:50
To: Joseph Fifield; [EMAIL PROTECTED]
Subject: Re: [Hibernate] Unit Te
PROTECTED]>
Sent: Wednesday, August 06, 2003 9:59 AM
Subject: Re: [Hibernate] Unit Testing With ThreadLocal Sessions
> My only concern with this is that the business logic component is now
> coupled with the web tier. For this project (which is basically a
> framework), we wan
> From: Juozas Baliuka [mailto:[EMAIL PROTECTED]
>
> > I don't close the session at all in any of my business logic
methods. In
> > deployment, a servlet filter _always_ closes the session at the end
of
> the
>
> It looks like not the good way for performance. As I understand
> "doFilter()" retu
> I don't close the session at all in any of my business logic methods. In
> deployment, a servlet filter _always_ closes the session at the end of the
It looks like not the good way for performance. As I understand
"doFilter()" returns after output is sent and
connection is open/locked too lo
