Revisit "Facelet Taglibrary <tag><component> must contain exactly one of <component-type>, <resource-id>, or <handler-class>

[eclipse-faces-bot]

Part of the work for #599: compcomp via namespace+compname") includes this change:

The commit log message that made this change includes this text:

M jsf-api/doc/web-facelettaglibrary_2_2.xsd

Make it so a must have exactly one of ,
, or

Here is the rationale behind the above change: if you are going to specify a handler-class, it does not matter what the component-type is because the handler-class effectively can do whatever it wants to create the component. The component-type is only necessary if you want JSF to create the component for you.

Affected Versions

[2.2]

[eclipse-faces-bot]

@glassfishrobot Commented
Reported by @edburns

[eclipse-faces-bot]

@glassfishrobot Commented
Issue-Links:
is related to
JAVASERVERFACES-3762

[eclipse-faces-bot]

@glassfishrobot Commented
@edburns said:
The reporter for JAVASERVERFACES-3762 wants this decision to be revisited in light of this comment:

Yes, I understand that you can do that, but here's why I feel this should be reverted:

1. Requiring the component's handler-class to create the component-type couples them tightly together, removing the ability to re-use a handler-class for other components. I feel this fights against the original design, which encouraged the re-use of the 3 component parts: handler-class, component-type, and renderer-type.
2. The most typical use case of specifying a handler-class for a custom component is to add MetaRuleset rules by overriding createMetaRuleset(). In this case, delegating the creation of the component to JSF is the desired functionality. Requiring every custom handler-class to also create the component requires developers to add unnecessary code.
3. The current implementation in com.sun.faces.config.processor.FaceletTaglibConfigProcessor.java simply doesn't match the xsd. Currently, any of the following combinations can be defined in the taglib for a component:
   • handler-class (with optional component-type and/or renderer-type)
   • component-type (with optional renderer-type)
   • resource-id

[eclipse-faces-bot]

@glassfishrobot Commented
Marked as fixed on Monday, February 16th 2015, 10:24:30 am

[eclipse-faces-bot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-1362

[eclipse-faces-bot]

• Issue Imported From: Revisit "Facelet Taglibrary <tag><component> must contain exactly one of <component-type>, <resource-id>, or <handler-class> javaee/javaserverfaces-spec#1362
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: Unassigned
• Original Issue Closed By:@glassfishrobot