Hi Sam, > I took a look at AjaxRequestTarget and its inner classes to check how wicket > renders components on ajax requests. > These components always have parent pages and the rendering process looks > something like this: > page.startComponentRender(comp) -> comp.renderComponenet() -> > page.endComponentRender(comp) > then the response from request cycle is set to be the ajax response so the > html is directed to it. >
I just gave it a try during weekend and I have managed to render "arbitrary" Wicket components as cells of the grid (so, you could use a panel with link and so on as you needed). My current solution is still a bit "hacky" and I would like clean it up before making it "public". I write "arbitrary" because there will be some limitations on the cell contents, e.g. they will not work if they contribute JavaScript code to page, but that could be considered as a minor limitation. I used the idea I mentioned before... Best, Ernesto --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
