And how does this result in a different problem than it does with my use case?
Wicket's session is thread-safe while components are not.
You should stop clinging to your solution and start developing a better one.
How can we help you with that?
Sven
On 09/19/2013 12:13 PM, Rafael W. wrote:
And how does this result in a different problem than it does with my use
case?
2013/9/19 Martin Grigorov <[email protected]>
Because Session#error() also uses it. And you can have several requests
with the same session.
On Thu, Sep 19, 2013 at 10:03 AM, Rafael W. <[email protected]> wrote:
If this is not allowed at any circumstance: why is the method
synchronized?
