[jira] [Commented] (TRINIDAD-2397) Provide API to discover location of document that contains tag definition for a given component

["Jeanne Waldman (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735219#comment-13735219 ] 

Jeanne Waldman commented on TRINIDAD-2397:
------------------------------------------

/myfaces/trinidad/trunk/trinidad-api/src/main/java/org/apache/myfaces/trinidad/util/ClassLoaderUtils.java
/myfaces/trinidad/trunk/trinidad-api/src/main/java/org/apache/myfaces/trinidad/util/ComponentUtils.java
svn 1507065
                
> Provide API to discover location of document that contains tag definition for a given component
> -----------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2397
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2397
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 2.0.1-core
>            Reporter: Prakash Udupa
>         Attachments: TRINIDAD-2397_patch_over_trunk.patch
>
>
> There are custom tags and components that insert other dynamic contents (i.e subtree of components) into the component tree. The tags for such dynamically added components come from a document fragment that is different from where the inserting component / tags come from. For example in Oracle's ADF component library, there are "region", "pageTemplates" and "declarativeComponent" that does such dynamic includes.
> There is often a need to know the document where the corresponding tag is defined for a given component. A couple of usecases are:
> 1. Browser based "page editor" or "Designtime @ Runtime" kind of products where they will need to change the tags in the document when a component is customized / edited at runtime.
> 2. Ability to store any runtime customizations for components against the document where its tag belongs. (For example. when the columns of dynamically added table is reordered)
> The inserting tags / components and the inserted components would be used best to determine the location of the fragment document that they include / or where they came from. We need to provide some hooks where the authors of such tags / component are able to provide the URL for the documents given the components.
> This enhancement asks for providing an API that provides URL for such documents, and also to publish the necessary hooks that tag / component authors can implement when then the URL providing API can use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira