I have been playing with wicket for the last week. I must agree with what Alexander says. The documentation is rather lacking and quite frustrating. To bad because wicket is cool. So +1 for better docs. As a newbie to wicket I can't help in writing it but I can tell you what I find frustrating:
The javadocs is not linked from the wicket site, it was hard to find even using google. The component reference is not complete. The examples have a link to 'view source' but it does not say which files to look at for a given example. It would be helpful if the component reference said which component belonged in which jar-file (wicket or wicket-extension). Personally I think that tapestrys component reference is helpful (http://tapestry.apache.org/tapestry4.1/components/index.html) Perhaps there could evolve some kind of javadoc convention or other documentation-convention for components that describes the component, the parameters, the css-classes the component renders and so on. Oh yeah, the component reference app is stateful so I constantly get session expired when looking at the examples, I can't for the life of me figure out why :-) It was a bit hard to find a reference to the wicket-tags, at least it is linked from wiki, but a schema-file would be helpful to get command completion in the HTML-editor. Cheers, Johan 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]
