[
https://issues.apache.org/jira/browse/WICKET-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1542.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
we wont support this just like we do not support adding repeaters directly to
the ajax target. there is no way for us to know which components are inside the
transparent resolver as that information is known only at render time when the
markup is actually being parsed
> Transparent Resolvers as targets for Ajax requests
> --------------------------------------------------
>
> Key: WICKET-1542
> URL: https://issues.apache.org/jira/browse/WICKET-1542
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.3
> Environment: Any
> Reporter: Jan Kriesten
> Assignee: Igor Vaynberg
>
> As it is now, using Componants which are transparent resolvers as targets for
> Ajax requests don't lead to actually rerender their Markup-children.
> Now I have an urgent implementation issue with this where I want to have two
> table rows with a DataTable for certain rows, so I have to change the Markup
> hierarchy. To not break the functionality of the contained DataGrid, I have
> to use a transparent resolver:
> <wicket:container wicket:id="rows">
> <tr wicket:id="row"><td wicket:id="cells"><span
> wicket:id="cell">[cell]</span></td></tr>
> <tr wicket:id="action-row"><td wicket:id="action-cells"><span
> wicket:id="action-cell">[cell]</span></td></tr>
> </wicket:container>
> 'row' would be the transparent resolver in this case - and also a target for
> Ajax requests.
> This doesn't work at the moment, since the 'cells' aren't re-rendered on Ajax
> requests.
> Is there another solution to this problem I didn't think of? Or is there
> another solution to have the cells rerendered?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
