Well, that was the old dummyForm stuff we're trying to get rid of here.
Mario, there is no problem with that - if you can ensure that on postback, when the JSP is processed one more time, all components are found and not recreated from scratch. I'm worried about findComponent not working anymore if we just add a form somewhere in the view, as a form is a naming-container, right? A solution might be to have a special form component which isn't a naming container. That might be a solution ;) Ah, one more thing: when searching for a parent form, we should utilize the component-family, and not instanceof'ing UIForm, cause that won't work with ADF Faces then... regards, Martin On 5/17/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 5/17/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > 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. Seems like I remember that h:tabbedPane did this already -- creates a form if it's not already inside one.
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
