Thanks Ken, now I know what you meant by a QUERY_STRING. I added this
to our code and it fixes the problem.
Thanks,
mark
Ken Paulsen wrote:
>
> Yes, it would be invisible. You should be able to see examples of
> this in many of the other dynamicTreeNode components. For example:
>
>
> childURL="applications/enterpriseApplicationsEdit.jsf?appName=#{$this{valueBinding}.text}"
>
>
> Yours may be as simple as folder=SA or folder=Comp... you don't need
> yours to be dynamic like the one above. However, if there is
> navigation that occurs to that node from anywhere other than the tree,
> you will need to match this URL in order for it to correctly find the
> treeNode to highlight it.
>
> Ken
>
> Mark Saunders wrote:
>> Yes they do represent the same object. How do you add a QUERY_STRING
>> parameter to a dynamic tree node? Would this be invisible to the
>> user, that is the text in the tree would not be altered?
>>
>> -mark
>>
>> Ken Paulsen wrote:
>>>
>>> Hi Mark,
>>>
>>> Do both "ant_test_binding_1_asa1" nodes represent the same object?
>>> If yes, is there any way you can distinguish them from each other by
>>> adding a QUERY_STRING parameter like "x=1" and "x=2"? This would
>>> help be able to distinguish the 2. Otherwise the first one will be
>>> highlighted.
>>>
>>> Ken
>>>
>>> Mark Saunders wrote:
>>>> Ken, we are running into an issue with breadcrumbs and
>>>> tree-highlighting. The problem appears when we have two leaf nodes
>>>> that have the same text. It is appearing now, because we are
>>>> listing SU's under the Service Assembly node as well as under the
>>>> Component node. Is there a way we can work around this problem?
>>>> It would be fine with us to have both nodes highlighted, or just
>>>> the one we clicked on.
>>>>
>>>> I've attached a jpg to help better describe the problem.
>>>>
>>>> -mark
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>