myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeanne Waldman (JIRA)" <...@myfaces.apache.org>
Subject [jira] Resolved: (TRINIDAD-987) add 'scoped-id-holder' and 'multi-scoped-id-holder' to transform.xsl and transform12.xsl
Date Tue, 04 Mar 2008 23:13:44 GMT

     [ https://issues.apache.org/jira/browse/TRINIDAD-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeanne Waldman resolved TRINIDAD-987.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.7-plugins

> add 'scoped-id-holder' and 'multi-scoped-id-holder' to transform.xsl and transform12.xsl
> ----------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-987
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-987
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>    Affects Versions:  1.2.6-plugins
>            Reporter: Jeanne Waldman
>            Assignee: Jeanne Waldman
>             Fix For: 1.2.7-plugins
>
>
> I need to add mfp:scoped-id-holder and mfp:multi-scoped-id-holder to the transform xsl
files so that our development tool (JDeveloper) can prompt the user if an attribute is a scoped-id-holder
(like chooseId) or multi-scoped-id-holder (like partialTriggers).
> 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 
> This will go into our plugin code. Once that is done, we'll be able to add the meta-data
to our component's xml files (this will be another JIRA issue) and when we build we'll see
the meta-data in built faces-config.xml file for each of 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.


Mime
View raw message