On 5/11/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 5/11/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> Also, is it possible to lock the server-side bean on a framework
> level, so it would be guaranteed that the bean won't get second
> request until the first one is serviced and responded to? Will a
> simple "synchronized" do?
Synchronizing might work *if* you were talking about the same instance of
the backing bean -- but that is not going to be effective if you are using
request scoped backing beans. In Struts terms, it would be like trying to
synchronize on a property setter of a request-scoped ActionForm -- that will
not catch the "duplicate submit" scenario because each request woud get its
own instance.
Yep, I meant session-scoped beans. JSF is more tolerant to
session-scoped beans than Struts, or even prefers them over request
scoped. So this might work.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
