Ian,
With this symptom I would guess that the Acegi filter is not installed
on all URLs that the Wicket application is handling. It is not likely a
Wicket problem as your code goes directly to Acegi's threadlocal.
If you're deploying to a clustered environment a lot of interesting
session mechanics are active too. But that all depends on your environment.
Regards,
Erik.
Ian Godman wrote:
It appears to me that it is ether a session issue with Wicket or that some
where the thread local used by Acegi is not being updated by the listener (not
had that problem before) or that a different thread is calling my code.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
