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
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
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
alexandru.objel...@isdc.rowrote:
Marat, as you can see people are interested and waiting for this
feature
to be published somewhere
Alex
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
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.
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
If community was interested, it would say something in 3 months, uh?
:) I'll post it on tuesday.
2009/3/8, Alex Objelean alexandru.objel...@isdc.ro:
I think community would be interested in this feature. Could you post the
code?
Marat Radchenko-2 wrote:
Wicket pages/components can
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
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
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
10 matches
Mail list logo