[ http://issues.apache.org/jira/browse/BEEHIVE-166?page=history ]
Daryl Olander resolved BEEHIVE-166:
-----------------------------------
Assign To: Julie Zhuo (was: Daryl Olander)
Resolution: Invalid
This is "by design". The way tree creation works is that the tree is only
created when the property bound to is null. If the property bound to is not,
then the Tree tag ignores it's body tag content and just renders the existing
tree. If the property is null, the tree is built by processing the contained
JSP TreeItem tags to construct the original version.
This is what you see in this example, you build the tree on the first page and
then display it again on the second page. This is because both pages are bound
to the same underlying tree instance.
I created a new BVT (bugs.J166) that demonstrates this behavior (and verifies
it).
> netui tree tag html output does not get re-freshed when differnces occurs in
> tagId being set/not set in the treeItem
> --------------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-166
> URL: http://issues.apache.org/jira/browse/BEEHIVE-166
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Julie Zhuo
> Assignee: Julie Zhuo
> Priority: Minor
>
> Repro:
> 1. Have a jsp that includes
> <netui:tree dataSource="pageFlow.tree" selectionAction="back"
> tagId="t2">
> <netui:treeItem expanded="true">Item1</netui:treeItem>
> </netui:tree>
> 2. Have another jsp that includes
> <netui:tree dataSource="pageFlow.tree" selectionAction="back"
> tagId="t1">
> <netui:treeItem expanded="true"
> tagId="ti1">Item1</netui:treeItem>
> </netui:tree>
> 3. Note the difference is the tagID being set in #2 and not being set in #1.
> But the trees point to the same data source in the page flow -- same tree.
> 4. Launch the page flow and visit the #1 page first. Do view source see the
> following
> <div>
> <div>
> <img
> src="/JavaScriptWeb/resources/beehive/version1/images/linelastnode.gif"
> style="vertical-align:middle;" border="0" alt="">
> <a
> href="/JavaScriptWeb/outputTest/back.do?netui_treeselected=0&netui_treeid=t2"> <img
> src="/JavaScriptWeb/resources/beehive/version1/images/folder_16_pad.gif"
> style="vertical-align:middle" border="0" alt="Tree Node"> Item1 </a>
> </div>
> </div>
> 5 Back and visit #2 page, notice it still generates the same result as above.
> But I am expecting the id lookup scipts since the treeItem got tagId set
> 6. Close the browser and launch the browser again. Visit the #2 page first
> and view source, we see the following output which is correct now.
> <div>
> <div id="ti1">
> <img
> src="/JavaScriptWeb/resources/beehive/version1/images/linelastnode.gif"
> style="vertical-align:middle;" border="0" alt="">
> <a
> href="/JavaScriptWeb/outputTest/back.do?netui_treeselected=0&netui_treeid=t1"> <img
> src="/JavaScriptWeb/resources/beehive/version1/images/folder_16_pad.gif"
> style="vertical-align:middle" border="0" alt="Tree Node"> Item1 </a>
> </div>
> </div>
> 7. Back and visit the #1 page and view source, notice it generates the same
> result as in #6. It does not matter when it has extra things in it, but it
> does matter when it needs the tagId info and its associated scripts and they
> are not there.
> Don't know how much of use case this is, just got there and thought need to
> log it anyway for tracking purpose.
--
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
