Created https://issues.apache.org/jira/browse/WICKET-2170 to track /Gwyn
On Mon, Mar 16, 2009 at 7:11 AM, Marat Radchenko <slonopotamusor...@gmail.com> wrote: > Sorry, was busy at work last week. > > Please find attached sources and jar with compiled classes. > > Usage is extremely simple: add ru.pronto.wicketextras.StatelessChecker > to postComponentOnBeforeRenderListener list and add > @StatelessComponent to any components you want to guarantee be > stateless. If any of them will become statefull (either directly or > because of any child) then exception will be thrown with explanation > what component is to blame. > > 2009/3/13 Alex Objelean <alexandru.objel...@isdc.ro>: >> >> Marat, as you can see people are interested.... and waiting for this feature >> to be published somewhere >> >> Alex >> >> >> Marat Radchenko-2 wrote: >>> >>> 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. >>> >>> I'll file a feature request with a patch, if Wicket team finds this >>> useful in Wicket core. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Have-a-feature%2C-want-to-contribute-tp21079751p22498471.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
