Re: REVIEW - Issue 26 - Tightly Coupled Renderer Dependencies

From: Roger Kitain <Roger.Kitain_at_Sun.COM>
Date: Mon, 02 Aug 2004 18:26:27 -0400

Craig R. McClanahan wrote:

> In other words, the spec *requires* a mutual dependence, without
> specifying a portable mechanism for how "allow" is supposed to work?
> Yuck -- that is badly broken.
> It sounds like the only alternative I have (in the absence of a spec
> errata) is to completely re-implement what CommandLinkRenderer does,
> and tell people not to use the standard <h:commandLink> tag inside a
> Struts form.
> Craig
 From the CommandLinkRenderer spec:
/Allow the form renderer to output a single "input" element (for the
entire page, ...
/I'm not sure what the word "Allow" means here - does it really imply
a dependency on Form Renderer?

Can't we just implement an isolated scheme in FormRenderer that does what
the spec says - to render *one* hidden field per form (for one or more
link children)? Thinking out loud here.... Couldn't FormRenderer
determine this
from the commandLink children in the tree?