The best place for CDK tag description.

[alexsmirnov]

I have some concern about proper place for JSF tag definition. Because tag uses both component and renderer refferences, there are three possible places to define it:

1) In the component's configuration ( as the special @Tag annotation or cdk: elements in the faces-config component-extention http://community.jboss.org/wiki/RichFacesCDKfaces-configextensions . Because JSF allows to have more then one renderer per component, CDK should sullort more then one renderer/tag pair.

2) In the renderer configuration. Once again, it would be @Tag annotation for a Renderer class, or special XML elements in the faces-config or renderer template.

3) Separate cdk:tag element in the faces-config extension. For the later case, it's har do defane proper place for annotation.

Please, take a look for proposed configuration.

[nbelaevski]

I think we should support this at least at component's configuration for the following reasons:

• In most cases we don't need to use several renderers for the component. Also there are components that require tags, but don't have renderer (e.g. rich:column)
• @Tag annotation is also handy for converters/validators/behaviors, so placing it on the component looks consistent with this approach

[abelevich]

nbelaevski wrote:

I think we should support this at least at component's configuration for the following reasons:

• In most cases we don't need to use several renderers for the component. Also there are components that require tags, but don't have renderer (e.g. rich:column)
• @Tag annotation is also handy for converters/validators/behaviors, so placing it on the component looks consistent with this approach

     Agree with Nick. Component's configuration is the right place for this.

[nbelaevski]

Just found this proposal in JSF 2 specification tracker: https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=594

[jbalunas]

I also agree with Nick and Anton here.  Having it in the component configuration seems the best place.

Would this be configurable anywhere else as well?  Usually I prefer to have one ( maybe two) places where things like this can be declared.  Too many makes it too confusing.

This can be another area where RichFaces is prototyping behavior for spec :-)