Specify scoped-id meta data in the generated faces-config.xml file to be used
by Design Time tools
--------------------------------------------------------------------------------------------------
Key: TRINIDAD-991
URL: https://issues.apache.org/jira/browse/TRINIDAD-991
Project: MyFaces Trinidad
Issue Type: Improvement
Affects Versions: 1.2.6-core, 1.0.6-core
Reporter: Jeanne Waldman
Assignee: Jeanne Waldman
Now that TRINIDAD-987 "add 'scoped-id-holder' and 'multi-scoped-id-holder' to
transform.xsl and transform12.xsl" is implemented, we need to go through all
the component xml files and add the meta-data to the appropriate attributes.
scoped-id-holder: Used for cases where an attribute points to a single
relative component using scoped ids. e.g. defaultCommand, chooseId
multi-scoped-id-holder: Used for cases where an attribute points to multiple
relative components, where the scoped ids are space deliminated.
eg:partialTriggers
When we build using jdev:jdev we'll see the meta-data in built faces-config.xml
file for each of these attributes. Then JDeveloper will be able to write code
to help pick the component ids for these attributes.
This is very similar to what I did for issue 776 "add 'translatable' meta-data
to all the component properties that are translatable"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
