i think that might work. i havent played with ajax that much since the
latest request cycle refactorings, so i am only guessing. the only way
to find out is to give it a try :)
-Igor
On 12/28/05, R.J. Lorimer <[EMAIL PROTECTED]> wrote:
Igor,Thanks for your feedback. I'm certainly not a Wicket expe
Igor,
Thanks for your feedback. I'm certainly not a Wicket expert, so I'm
still trying to figure out the *right* approach to things - and the page
approach was based on feedback.
My previous approach was to try and use my existing panel control as the
content of the AJAX response (via a Comp
or put a placeholder panel with empty markup for comments, then in the
ajax handler replace it with an actual panel, render it, and replace it
back with the placeholder.
this might be even cleaner then having an invisible listview.
-Igor
On 12/28/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
imho,
imho,
i think this is the wrong approach because it will cause problems with
links and forms. if you do max_pages_in_pagemap ajax requests and then
click a link or submit a form that was not updated by ajax you will get
a page expired error. it also creates a sync issue because the page you
are loo
Just to update on my progress, switching to a new page object really
made everything work great. I now have the individual comment fields
being lazily built (using a LoadableModel) on the page that is passed in
to the handler. The handler sets the page as the request target when the
callback is
shh, of course. The response shouldn't just be the panel - it should be
an entire Page! That makes sense.
Thanks for your help, I'll keep my progress posted here.
Emergence Dinterstage wrote:
On 12/28/05, R.J. Lorimer <[EMAIL PROTECTED]> wrote:
ComponentRequestTarget re-renders components
On 12/28/05, R.J. Lorimer <[EMAIL PROTECTED]> wrote:
> >
> >
> > ComponentRequestTarget re-renders components which have already been
> > rendered during the full page render. We only recently fixed a bug to
> > allow Panel children to be re-rendered as well. Because you are
> > re-rendering a Pane
ComponentRequestTarget re-renders components which have already been
rendered during the full page render. We only recently fixed a bug to
allow Panel children to be re-rendered as well. Because you are
re-rendering a Panel that bug should not affect you, but because of
the change I'd still sugg
On 12/27/05, R.J. Lorimer <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've been working with the Wicket 1.2 snapshot to try and integrate some
> more complex DOJO Ajax code for my site.
>
> In short (to give you an idea of what I'm trying to accomplish), I have
> a weblog with entries and comments. Whe
