the usecase in the target resolver is a user clicking a link multiple times quickly, just giving some context-Igor
On 6/28/06, Johan Compagner <[EMAIL PROTECTED]
> wrote:
Currently it has to be synced on sessionBecause it the rest (for example the get(int,int) method for a page) is also synced on s
Currently it has to be synced on sessionBecause it the rest (for example the get(int,int) method for a page) is also synced on sessionBut only through a session.That method is special because it is the only one currently i believe that can be access that doesn't go through the session
So thats why
I don't see why in PageMap.removeEntry:
public final void removeEntry(final IPageMapEntry entry)
{
// Remove entry from session
synchronized (session)
{
session.removeAttribute(attributeForId(entry.getNumericI