On 5/18/07, mchack <[EMAIL PROTECTED]> wrote:
> Thanks for the help. Makes sense. I am trying to come to grips with using
> Wicket for a fairly large project and am trying to come up to speed as quick
> as possible and at the same time try and figure out where I may get burned.
It is always good t
Thanks for the help. Makes sense. I am trying to come to grips with using
Wicket for a fairly large project and am trying to come up to speed as quick
as possible and at the same time try and figure out where I may get burned.
Johan Compagner wrote:
>
> youre page will be statefull anyway
> and
youre page will be statefull anyway
and then to try to conserve a few links would seem foolish to me that will
not save you much anyway.
If there is in the markup 5 links with wicket:id then you need 5 unique
components (you can reuse it)
and you need the wicket:id anyway because if you want to c
Johan, thanks for the response. It still appears that I will be instantiating
multiple AjaxLink(s), one for each unique link. In a stateful page these
would be stored in the session. By moving some state to the client it
appears that it might be possible to reduce the number of server side
objects
you can use one anonymous innerclass just fine for multiply ajax links
just give the seperate instances the state you want on the server side
why push that to the client?
AjaxLink link1 = AjaxLink("link1", new Model(mystate1))
AjaxLink link2 = AjaxLink("link2", new Model(mystate2))
onClick()
{
S
Would it be possible or reasonable to extend an AjaxLink to include
additional request parameters. My reason is that I would like to include
multiple AjaxLinks in a page and would like to only define one anonymous
inner class to handle the requests, using unique request parameters to
distinguish b
