ah, ok... so if there is no form in the parent-tree - you just render a form around the link itself?
that might work. I really don't like the dummyForm stuff at all anymore. At the end, I want to find a solution where we dynamically add a form to the component tree if that is necessary... regards, Martin On 5/17/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
Started a new topic to concentrate the post "DummyForm stuff" and "TOMAHAWK-416" in one place. How can we make the DummyForm stuff RI compatible (given that we still think we need it) Well, we have to override the renderer, but cant count on anything else than encodeBegin/encodeEnd/encodeChildren So what can we do. One idea could be, to render a form AROUND the component. The pro is, that we then no longer have to rely on the ExtensionsFilter to have this work. And it will work with ANY JSF implementation. The con is, that - especially with client-side state saving - this will greatly bloat the generated html, though, the user can easily workaround this limitation by adding a h:form manually. So if nobody objects, I'll try this out. Ciao, Mario
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
