Re: Wicket security

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: Wicket security

Mr Mean
I think it has to do with your wicket version. Only recently they made
that method public.
If you are using the snapshot version of wicket, try updating it. Note
that some versions of maven have a problem updating snapshots so go
into your local repository and delete wicket from it. then you should
have no problem updating to the latest snapshot.
Alternatively the beta2 version should also work.
Or if you can not upgrade to the latest wicket i suggest downloading
wasp and swarm here It is a
slightly older version but the only changes between this version and
the snapshots are the clustering changes (which is causing your
problem), some code restructuring, some apidoc changes and i changed
the eclipse project settings to eclipse 3.3.

Just let me know if this does not solve your problem.


On 7/5/07, [hidden email] <[hidden email]> wrote:

> Hi
> First off, I really like where wicket security is heading, the JAAS smell of it is just fantastic! :)
> I've been trying to experiment with wicket security and I've hit a wall. I'm pretty sure I got the configuration right, I get redirected to the login page and when I press login I get this exception:
> java.lang.IllegalAccessError: tried to access method org.apache.wicket.Session.dirty()V from class
>      at
>      at
>      at
>      at is.sja.pages.auth.LoginPage$2.signIn(
> I was hoping you would have some idea what's happening there since my searches turned up almost moot on how to fix this. I'm running this on wicket 1.3-beta2 and wicket-security 0.1-SNAPSHOT through maven.
> Regards,
> Arni Hermann Reynisson

This email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
Wicket-user mailing list
[hidden email]