This content has been marked as final.
Show 4 replies
-
1. Re: The best place for CDK tag description.
nbelaevski Jan 22, 2010 11:13 AM (in response to alexsmirnov)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
-
2. Re: The best place for CDK tag description.
abelevich Jan 23, 2010 10:06 AM (in response to nbelaevski)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.
-
3. Re: The best place for CDK tag description.
nbelaevski Jan 25, 2010 7:52 PM (in response to alexsmirnov)Just found this proposal in JSF 2 specification tracker: https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=594 -
4. Re: The best place for CDK tag description.
jbalunas Jan 29, 2010 11:00 AM (in response to nbelaevski)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 :-)