[ 
https://issues.apache.org/jira/browse/WICKET-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495791
 ] 

Johan Compagner commented on WICKET-558:
----------------------------------------

the current code does do this..

piece of Component.renderComponent :

                               beforeRender(); <<<<<<<<<<<<<<
                              
                                // SOME code SKIPPED

                                // Render the component and all its children
                                render(markupStream);
                        }
                        finally
                        {
                                // Make sure the original markup stream is back 
in place
                                parent.setMarkupStream(originalMarkupStream);
                                afterRender(); <<<<<<<<<<<<<<<<<<<<<<

> New attach->beforeRender refactor breaks ajax updating of list views
> --------------------------------------------------------------------
>
>                 Key: WICKET-558
>                 URL: https://issues.apache.org/jira/browse/WICKET-558
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0
>            Reporter: Jonathan Locke
>         Assigned To: Johan Compagner
>            Priority: Blocker
>
> Because components are created in onBeforeRender in list views (it calls 
> populateItem then), it is necessary for AJAX renderings now to call 
> beforeRender on every component to be updated before proceeding with the 
> render.  Since the current code does not do this, you get a NPE when 
> rendering happens since the item was never populated.
> It looks like AjaxRequestTarget.respondComponent should call before render on 
> the component tree (similar to how it does in Page) just before it's about to 
> render.  But I'm unsure if this is the right place to make the change.  
> Johan can you look at this since you were doing this refactor and probably 
> know all the details?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to