+1
Ari S.
- Original Message -
From: "Martijn Dashorst" <[EMAIL PROTECTED]>
To: "Wicket Development" <[EMAIL PROTECTED]>; "Wicket Users"
Sent: Monday, March 17, 2008 10:13 AM
Subject: [vote] Release 1.4 with only generics and stop support for 1.3
This thread is for voting only.
Hi,
This seems to occur at us and I have been able to reproduce it
with standard tomcat 6.0 installation.
I added some comments to:
https://issues.apache.org/jira/browse/WICKET-1184
Ari S.
-
To unsubscribe, e-mail: [EM
ng the next request, but this means keeping
> additional state for no good reason.
>
> -Matej
>
> On 10/17/07, Ari Suutari <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>>> I'm afraid you dont' really get what IComponentResolver is for. The
>>> p
state for no good reason.
I think for our case this could be perfect solution. We don't need
the state after the render, the application is dependend on it
only during it.
Thanks,
Ari S.
-Matej
On 10/17/07, Ari Suutari <[EMAIL PROTECTED]> wrote:
Hi,
>
state for no good reason.
I think for our case this could be perfect solution. We don't need
the state after the render, the application is dependend on it
only during it.
Thanks,
Ari S.
-Matej
On 10/17/07, Ari Suutari <[EMAIL PROTECTED]> wrote:
Hi,
>
ch is not a problem for someone who writes
a smaller web applications with just a couple of pages. But for someone
who does larger ones, it's not so nice.
Ari S.
On 10/17/07, Ari Suutari <[EMAIL PROTECTED]> wrote:
Hi,
But it looks like that in this case the v
Hi,
But it looks like that in this case the visitChilder is performed during
render, and it still won't find stuff added by autoAdd.
It is not a very robust design if the behaviour of autoAdd/visitChilder
would require some kind of component-hierarchy fine-tuning. This kind
of approach might w
