[ https://issues.apache.org/jira/browse/WICKET-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwyn Evans updated WICKET-2170: ------------------------------- Attachment: wicketextras.tar.gz wicketextras-1.5-SNAPSHOT.jar http://www.nabble.com/Re%3A-Have-a-feature%2C-want-to-contribute-p22532836.html (Need an explicit OK for licence or is the comment in the frst email sufficient?) > @StatelessComponent contribution by Marat Radchenko > --------------------------------------------------- > > Key: WICKET-2170 > URL: https://issues.apache.org/jira/browse/WICKET-2170 > Project: Wicket > Issue Type: New Feature > Components: wicket > Reporter: Gwyn Evans > Priority: Minor > Attachments: wicketextras-1.5-SNAPSHOT.jar, wicketextras.tar.gz > > > From mailing list - > http://www.nabble.com/Have-a-feature,-want-to-contribute-td21079751.html > "Wicket pages/components can be either stateful or stateless. Wicket > manages hem transparently and it is very easy to write any complex > page you want. Stateful pages are much more powerful than stateless. > However that comes at a cost of using page store for their state. On > highload sites it is usually desired to minimize session-scope data, > and move it to request-scope. That's when Wicket users approach a task > of making stateful pages stateless. However stateless state (sic!) is > very fragile, if you add a single stateful component to a page, it > instantly becomes stateful (and you even might not notice that if your > other page content can work in both modes. And here comes my lovely > feature - @StatelessComponent. It is an annotation that you should put > on components which you want to be stateless. It doesn't do any magic, > it simply uses postComponentOnBeforeRender to assert that annotated > component (and all its children) are stateless. If it doesn't, an > exception is thrown, indicating what component tries to be stateful. > This feature isn't large enough to be put in a separate project (just > one annotation and one listener) but wee find it extremely useful on > our project. > I'd be happy to give it to Wicket project (or wicketstuff?) at > absolutely no cost (tests included) under same license as wicket > itself, if Wicket developers are interested in it." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.