Re: REVIEW - Issue 26 - Tightly Coupled Renderer Dependencies

From: Roger Kitain <Roger.Kitain_at_Sun.COM>
Date: Tue, 03 Aug 2004 08:15:26 -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
For now, this is probably what you are going to have to do. We cannot
get the
spec fixed for 1.1_01, so it will have to be fixed in 1.2. But to me it
more sense for the spec to place the responsibility on FormRenderer to
locate it's child commandLink components, and make sure only one hidden
field gets rendered. So, the spec would not imply a "joint" responsibility
(or dependency - whatever..) between FormRenderer/CommandLinkRenderer.
I'll add an issue for this for 1.2.


To unsubscribe, e-mail:
For additional commands, e-mail: