Well, you can get more than one *created*, but only one will actually be stored as a session attribute if the attribute name is the same. Synchronizing the session.setAttribute() method would be pointless; the container guarantees that this won't break anything. So, exactly what portion of the code would you propose to synchronize?
One will overwrite the other in the session, yes, but the RequestProcessor doesn't pull it back out of the session. It uses the instance it created, so both could be used concurrently.
Feel free to submit a patch, but I'm betting the performance cost of implementing it will be horrendous. If you're concerned about multiple simultaneous requests, you should really be using request scope form beans anyway.
The performance cost will be nothing. All this will do is prevent concurrent requests within the scope of an action form instance. I'm worried about unexpected browser behavior leading to incosistent state and weird synchronization errors; probably not a problem with posts, but definitely an issue with gets. I can't think of a valid use case where two request should be able to modify the same session-scoped action form
Bob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
