>>>> On Fri, 29 Oct 2010 13:02:10 +0200, Jakob Korherr
<jakob.korherr(a)gmail.com> said:
JK> Hi,
JK> Thinking more of it and trying out some prototypes, I now think
JK> Leonardo's approach is the way to go. Of course, it would somehow be
JK> possible to circumvent the problems mentioned before (like multiple
JK> action listeners or the missing f: tag for client behaviors), but
JK> after reading the vdldocs again, I think it's much more consistent
JK> with what we have right now.
JK> Consider the current facet solution: The user can provide facets for
JK> the composite component and the author of the composite component can
JK> add them to implementation-components via cc:insertFacet. And this is
JK> exactly what we need for cc:actionSource, cc:valueHolder,
JK> cc:editableValueHolder and cc:clientBehavior.
JK> Thus I would propose the following new tags (from Leonardo's original
proposal):
JK> <cc:insertActionSource name="XXX" />
JK> <cc:insertEditableValueHolder name="XXX"/>
JK> <cc:insertValueHolder name="XXX" />
JK> <cc:insertClientBehavior name="XXX" />
Seems reasonable. I'd like to see a prototype.
--
| edward.burns(a)oracle.com | office: +1 407 458 0017
| homepage: |
http://ridingthecrest.com/
| 8 work days until German Oracle User's Group Conference