Re: transaction tokens

[Adam Hardy]

I was thinking there might be a way of controlling transactions by 
saving all tokens in the session once they are used, and then if it 
crops up again, not allowing the execution.

Would be simple to implement with a hashmap I think.

What's the likelihood of 2 transaction tokens being identical, over the 
course of a user session?

(Theoretically you could apply the same principle to action forms,saving 
them against a transaction token and then sorting it out in a base class 
during form.reset() (exceptionally seat-of-pants thinking))

Andrew Hill wrote:
oops, yep. Should have specified that. Only for a session mapped actionform
will there be a problem. The request ones are of course not affected by the
problem.
-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 6 August 2003 17:56
To: Struts Users Mailing List
Subject: Re: transaction tokens
Andrew Hill wrote:

I dont believe so. :-(

<btw>
Likewise for multiple actionforms (for the same mapping) when you have >1
windows open (such as you might want for editing several records selected
from a list in the main window...)
</btw>


what's the problem with that? You mean you have the action form in the
session?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]