[jira] Resolved: (BEEHIVE-480) tagId naming doesn't work inside of .tag files

["Daryl Olander (JIRA)" <be...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/BEEHIVE-480?page=history ]
     
Daryl Olander resolved BEEHIVE-480:
-----------------------------------

     Assign To: Krista Baker  (was: Daryl Olander)
    Resolution: Fixed

The issue here was that to construct the name of the tag (id) we walked the tag hiearchy looking for the script containers.  This doesn't work when a tag file is used because the tag doesn't get put into the tag hiearchy.  The result was that we didn't create the same name for the HTML element on the server and on the client. 

The fix is to move support for naming into the request.  

BVT: coreweb/bugs/j480

> tagId naming doesn't work inside of .tag files
> ----------------------------------------------
>
>          Key: BEEHIVE-480
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-480
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Daryl Olander
>     Assignee: Krista Baker
>      Fix For: V1

>
> DESCRIPTION:
> The suggested way for reusing UI in PageFlow web applications is to use .tag files. A problem exists with the netui:scriptContainer, tagId attribute, and lookupTagById mechanism that make this difficult in cases where JavaScript is used. Also see attached repro.
> Repro:
> 1) Create a .tag file that contains a hidden field with an id of foo inside a script container.
> 2) Create a jsp that references the .tag file.
> 3) Locate the .tag file reference in the jsp and surround that with a script container.
> 4) Create a Script method in the .tag file that uses the lookupTagById function to find the hidden field by it's tagId attribute value.
> Result:
> The hidden field cannot be found because it's tagId is generated incorrectly with an id of n1.foo when it should be n0.n1.foo, representing it's place in the script container hierarchy. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira