I find the idea great. The other places where I've usage of this are xml
heavy frameworks like hibernate. You can then replace all the nasty xml
configurations with annotations.
However I don't see how that currently fit wicket? We just dont have a
lot of settings outside our javaclasses. Might just be good design:)
Only place where wicket has an xml setting right now are web.xml.
-my 2 cents
Martijn Dashorst wrote:
We've tried annotations for lifecycle methods and that didn't work
out. But I think other parts of our API can benefit from annotations.
I suggest we take a look at annotations for:
* the mount with a page
* ........
Martijn
--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
