Re: Have a feature, want to contribute
Created https://issues.apache.org/jira/browse/WICKET-2170 to track /Gwyn On Mon, Mar 16, 2009 at 7:11 AM, Marat Radchenko 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 : >> >> 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
Re: Have a feature, want to contribute
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 : > > 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 > > wicketextras.tar.gz Description: GNU Zip compressed data wicketextras-1.5-SNAPSHOT.jar Description: application/java-archive - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Have a feature, want to contribute
Same here! Great idea Marat... I missed the original post. And I can use it right now... Antoine. On Fri, Mar 13, 2009 at 11:10 PM, Alex Objelean wrote: > > 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 > > -- We don't see things as they are, we see things as we are. - Anais Nin Whether you think you can or whether you think you can't, you're right. - Henry Ford
Re: Have a feature, want to contribute
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
Re: Have a feature, want to contribute
Sounds very useful ! -especially in development model. We've spent much time debugging and searching for the one "stateful" component/behavior - in our large page hierarchies ! 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-tp21079751p22496841.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
Re: Have a feature, want to contribute
And if you want to contribute something, it is often better to also attach it to a JIRA issue, since then it doesn't get lost in the archives. A jira issue can be assigned, tracked etc, whereas a message in the archives tend to get lost in the huge amount of traffic. It takes just one generics discussion to say bye bye to your questions :) Martijn On Sun, Mar 8, 2009 at 9:57 PM, Alex Objelean wrote: > > I usually read all threads from the forum, but somehow skipped this... (there > are too many less interesting threads). I find this feature really useful.. > > Alex > > > Marat Radchenko-2 wrote: >> >> If community was interested, it would say something in 3 months, uh? >> :) I'll post it on tuesday. >> >> 2009/3/8, Alex Objelean : >>> >>> I think community would be interested in this feature. Could you post >>> the >>> code? >>> >>> >>> >>> 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-tp21079751p22400634.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 >> >> >> > > -- > View this message in context: > http://www.nabble.com/Have-a-feature%2C-want-to-contribute-tp21079751p22402882.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 > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Have a feature, want to contribute
I usually read all threads from the forum, but somehow skipped this... (there are too many less interesting threads). I find this feature really useful.. Alex Marat Radchenko-2 wrote: > > If community was interested, it would say something in 3 months, uh? > :) I'll post it on tuesday. > > 2009/3/8, Alex Objelean : >> >> I think community would be interested in this feature. Could you post >> the >> code? >> >> >> >> 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-tp21079751p22400634.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 > > > -- View this message in context: http://www.nabble.com/Have-a-feature%2C-want-to-contribute-tp21079751p22402882.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
Re: Have a feature, want to contribute
If community was interested, it would say something in 3 months, uh? :) I'll post it on tuesday. 2009/3/8, Alex Objelean : > > I think community would be interested in this feature. Could you post the > code? > > > > 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-tp21079751p22400634.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
Re: Have a feature, want to contribute
I think community would be interested in this feature. Could you post the code? 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-tp21079751p22400634.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
Re: Have a feature, want to contribute
Marat, It doesn't look like you received any response. I'd be happy to look at it. Could you file it as a patch on JIRA? Thanks, Jeremy Thomerson http://www.wickettraining.com On Thu, Dec 18, 2008 at 1:52 PM, Marat Radchenko < slonopotamusor...@gmail.com> 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 > >
Have a feature, want to contribute
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
