Prakash Udupa created TRINIDAD-2499: ---------------------------------------
Summary: ChangeManager provides incorrect document location for dynamic components Key: TRINIDAD-2499 URL: https://issues.apache.org/jira/browse/TRINIDAD-2499 Project: MyFaces Trinidad Issue Type: Bug Components: Archetype Affects Versions: 2.1.0-core Reporter: Prakash Udupa In TRINIDAD-2397, enhancement was provided to obtain the document location of components are are dynamically added. There is a bug in this code that in some cases the location is not provided correctly, as explained in the following example: Consider this page structure: <jsp:root> <foo:three> <foo:insertingComponent> <= Step #2: This subtree is inserted from fragment2.jsff <jsp:root> <foo:dynamicLayout> <foo:two> <= Step #1: defined in fargment1.jsff <foo:one> <= Customization target, this inserted component is defined in fragment1.jsff In this example, the search for location is expected to stop at step #1 and location returned as 'fragment1.jsff', instead the look up extends until step #2 and returns incorrect location 'fragment2.jsff'. This causes the wrong document being searched for the customization target here, customization failed therefore. The bug is in org.apache.myfaces.trinidad.util.ComponentUtils.getDocumentLocationForComponent() Will provide a fix patch soon. -- This message was sent by Atlassian JIRA (v6.2#6252)