I'll let one of the developers go into more detail about the
documentation issue :)
Regarding security there are several sub projects for you to choose.
and i would like to refer to this page for an overview of the
differences
http://wicketstuff.org/confluence/display/STUFFWIKI/Security+Framework+Comparison
>From there you should be able to find more information although a good
place to look is also the old sourceforge mailinglist.
Maurice
On 8/9/07, Alexander Schatten <[EMAIL PROTECTED]> wrote:
> Greetings to all Wicket experts
>
> I try to get Wicket running for some rather simple web-application.
> First (no offense, but have to say that), Wicket has the worst
> documentation of an apparently good open source project I have seen in a
> long time; and this is really a pity, because it seems, that if one
> would know how to do it, many things can be performed quite easily.
>
> Now to my current issue: I want to add a loginpage to my project and
> protect some of the pages.
>
> My first thought was to make a base class (worked) and somehow hook into
> the lifecycle, check if the user is checked in (MySessio works) but this
> is not running at all. lot of redirection errors, incoherent
> documentation and so on. e.g.:
>
> Javadoc 1.3 of Page talks about "checkAccess()" method... however, this
> methdod can be found nowhere.
>
> Now I check the mailing list archive, only useful thing I find is a
> posting from 9.2.2006 suggesting:
>
> protected void init()
> {
> getSecuritySettings().setAuthorizationStrategy(new
> IAuthorizationStrategy()
> {
> public boolean authorizeAction(...) ...
> public boolean authorizeInstantiation(...) ...
> }
>
> starting with 1.2. Well, this interface is still here, but these methods
> are not available any longer.
>
> There is no documentation about this strategy I could find and the
> Javadoc (which is btw. not linked from the wicket website, and just this
> made me search for an hour) is very unconclusive.
>
>
> btw. another thing: when the documentation of a project is so bad, at
> least the javadoc should be accessible: I tried to build mvn site with
> wicket and got the error that you use a special template or somthing and
> it does not build, and this template is apparently not in the repository
> AAAAARRRGGHHH.
>
>
> sorry, but Wicket experience was far away from beeing pleasent. I am
> quite willing to check several sources, but this here is really bad.
> outdated information is not easy to distinguish from actual
> documentation, the reference to the component doc is nice, but component
> doc very incomplete and so on...
>
> Wicket seems to be a quite productive and powerful framework (one of the
> best I have seen so far, at least so it seems), but getting into it is a
> damn frustrating experience, I can tell you...
>
> (I did not even know where to start. happyily there is a maven archetype
> at the Jetty website which was helpful.)
>
>
>
> So, sorry for that outburst, but I was so frustrated...
>
>
> best greetings
>
>
> Alex
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
