[jsr-314-open] Composite component metadata runtime behavior
Andy Schwartz
andy.schwartz at Oracle.com
Wed Feb 2 14:40:07 EST 2011
Gang -
I recently triaged a bug that complained that the "type" attribute of
<cc:attribute> was not behaving correctly. The user expected the
following attribute specification:
<cc:attribute name="foo" type="java.lang.Integer"/>
To result in a warning/error when used as follows:
<comp:bar foo="MostDefinitelyNotAnInteger"/>
This seems like a reasonable expectation. An equivalent test case
using, for example, JSP tag files does result in an error.
This raises a few questions:
1. Should JSF implementations be making use of composite component
metadata (like "type") at runtime to enforce the intentions of the
composite component author?
2. Should this behavior be specified?
3. Are there other places where we have similar metadata (eg. Facelets
taglib.xml files) that we should review as well?
Andy
More information about the jsr-314-open-mirror
mailing list