Hi Mario, Dummy Form is used by some of the custom navigation menus such as NavigationMenu2, JsCookMenu, etc.
The rationale is as follows: Since JSF is heavily dependent on POST, the menu has to be nested within a form. During the render phase, the renderer checks for a parent form in the component heirarchy. If no parent form is found, instead of reporting an error, the renderer sets an attribute in the RequestMap. The Extensions filter (I think) checks for this attribute, and if found, renders the dummy form. In this way, the component will continue to function even without a parent form element. --- Mario Ivankovits <[EMAIL PROTECTED]> wrote: > Hi! > > As you might know I moved the dummyForm stuff out of > shared to tomahawk > due to some problems we had with it after > introducing the shared_* stuff. > > To still have the same functionality I installed the > custom renderers > (for commandLink/commandButton) in tomahawks > faces-config.xml > > Now it turns out that this will break a installation > if one simply would > like to use tomahawk with JSF-RI. > > Given what happened lately (JBoss and others using > JSF-RI for their > app-servers) we should try hard to make tomahawk > more RI friendly. > > So I propose to remove the renderers from > faces-config.xml from tomahawk > and add to the documentation who to enable the > dummyForm stuff again (by > adding the renderer to your own faces-config.xml). > Still it will only > work if one uses the myfaces impl. I see no way how > to enable it for > myfaces and JSF-RI as we have to know how the > renderer work. > (I already expressed my wish that the standard > renderers also have a > standardized internal api so we can safely inherit > from them) > > Said this, I would like to know who really use the > dummyForm stuff (and > why)? > > Ciao, > Mario > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
