> Another concern I have is that the Clay jsp tag is using the jsfid > attribute to specify the clayJsfId propertie. I understand that since > you are already using the Clay tag, it should be obvious you are > working with the clay component and so the jsfid attribute refers to > the component definition Clay should use (the clayJsfId property). > > But it is pretty confusing at first because all the other approaches > are using the jsfid for identifying the Clay component and then > specify the clayJsfId to refer to the component Clay should use. I > think you should aim to use uniform names accross the approaches even > if it's not totally *right* semantically. It would be a lot easier to > use in my opinion. Just my two cents. >
The clayJsfid should only be used with the HTML views. Consider the following: <span jsfid="clay" clayJsfid="baseAddress"/> The span tag has to be associated with a JSF component. If you are using the vanilla clay component without a XML subclass definition, you need to be able to specify the root of the tree. If you don't like this approach, simply take the time to create an XML definition. The example above gives the option for creating pages that use the HTML views only (no extra XML configs). <component jsfid="addressPanel" extends="baseAddress"/> <span jsfid="addressPanel" /> Gary --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
