Mailing-List: contact cactus-user-help@jakarta.apache.org; run by ezmlm
From: "Magnus Mickelsson" <magnus.mickelsson@telia.com>
To: "Cactus Users List" <cactus-user@jakarta.apache.org>
Subject: Always execute a end method on the client-side?
Date: Tue, 2 Sep 2003 18:46:22 +0200
Message-ID: <HMEIJNMIMJPMHBHCGBPCAENECAAA.magnus.mickelsson@telia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <C1D129D481EED511A1CA0002A5AD623902E8BB54@avenue>

Hi guys,
first off - sorry for the spam mail. I was too tired whan I read the
message. (DOH!)

Now to my point. I sent this to the list before, but was for some reason
refused by the moderator. Here goes again (this thing is really important to
me, so I'd be really grateful for any hints :-)
------

I just wanted to know if there is some way to guarantee that either the
end(WebResponse) or endXXX(WebResponse) method in Cactus 1.5 is always
executed (or similar functionality), regardless of assertion failure or
exceptions?

My problem is that I set up test data using DBUnit on the client in the
begin(WebRequest) method, and then want to clean it up after the test has
run, regardless of it has failed or not. I do not want the DBUnit JARs,
test-data etc. transported to the server unless I absolutely _have to_. :-)

Any ideas?

Thanks in advance!

/Magnus

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 2003-08-19