*Grrrr* >> so if there is no form in the parent-tree - you just render a form >> around the link itself? >> > yes. > It turns out that this wont work too.
I tried to lookup the h:form renderer (through context.getRenderKit().getRenderer) and the original link/button renderer using reflection (configurable through web.xml for sure) and call its encodeBegin/encodeEnd to render all the stuff. You will get the form, but decode wont work as there is no form (which is a naming container) in the view - so the command link/button cant find its hidden field. Anything else will require some more assumptions of how the form/link/button stuff works. So we have to come to this solution: >> At the end, I want to find a solution where we dynamically add a form >> to the component tree if that is necessary... >> > I know (or I think I know ;-) ) , you dont like to instrument the view > tree, but in an custom view handler this can easily be done. > e.g. you can take the children of the f:view component and feed them > into an h:form which is then the only child of f:view > But okay, lets discuss this when its time :-) > So maybe its time NOW. What do we think about such a special ViewHandler? I'll start to see if there is any other downside, though, if there is any objection please come up as soon as possible ;-) Ciao, Mario
