I figure I might as well jump in with both feet. At a minimum I might get a
lesson in basic transaction control.
The obvious problem with long transactions in a web environment is that
UserTransaction only deals with the current thread, but TransactionManager
has getTransaction and resume methods
Tim,
I was purposely vague in an attempt to hide the fact that I don't know what
I am talking about. I was thinking of something earlier in the request
handling process. The ContextFilter gets specified in the web.xml file and I
thought maybe something could be done in a custom filter to keep tra
Wouldn't we have to mirror everything going on in the controller
files to do that? And, since I'm ignorant on this topic, how do we
get the transactions to span all the services that would be caused by
each of the calls?
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o
What if we went as far as to send all testing requests thru a custom
controller or handler - is there anything along those lines that could be
done?
-Al
On 1/9/07, Tim Ruppert <[EMAIL PROTECTED]> wrote:
As far as I know, there is nothing that you can do from the outside
that turns off your int
As far as I know, there is nothing that you can do from the outside
that turns off your internal transaction management. SOA apps are
not the easiest to test :)
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Jan 9, 2007, at 2:20 PM, Al
I was just thinking about testing and thought I would ask this question - is
there a way to incorporate long transactions or some other mechanism so that
multiple requests could be made within the context of a single WebTest and
have all those transactions rolled back at the end? That seems to be
