beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <>
Subject [jira] Resolved: (BEEHIVE-1166) DivPanel JavaScript support requires legacy setting
Date Tue, 19 Dec 2006 17:48:21 GMT
     [ ]

Carlin Rogers resolved BEEHIVE-1166.

    Resolution: Fixed
      Assignee: Alejandro Ramirez  (was: Carlin Rogers)

Resolved with SVN revision 488735.

Note, since this is an issue with the client side JavaScript support for DivPanel, it should
be tested manually. To reproduce, use one of the DivPanel tests in the NetUI coreWeb web app.
Make sure that the <id-javascript>legacy</id-javascript> element is removed from
the <jsp-tag-config> in the beehive-netui-config.xml file so that you are not running
with the legacy JavaScript support. 

With the old version of the netui-tree.js, a browser should indicate a JavaScript error that
getScopeId() is not defined on line 610. This is in the DivPanel JavaScript init routines.
Since the DivPanel init fails to execute correctly the page will also display incorrectly.
Now, with the changes to call lookupIdScope() rather than getScopeId() in netui-tree.js, the
error messages should not appear and page should display and function correctly and no longer
requires the legacy setting in the NetUI configuration.

> DivPanel JavaScript support requires legacy setting
> ---------------------------------------------------
>                 Key: BEEHIVE-1166
>                 URL:
>             Project: Beehive
>          Issue Type: Bug
>          Components: NetUI
>    Affects Versions: 1.0.1, 1.0.2, V.Next
>            Reporter: Carlin Rogers
>         Assigned To: Alejandro Ramirez
>             Fix For: V.Next
> The current DivPanel JavaScript support in netui-tree.js uses an old legacy routine,
getScopeId() rather than the desired lookupIdScope(), requiring a legacy setting. This means
that apps using <netui:divPanel> will not work without the legacy JavaScript setting
in the beehive NetUI configuration.
> The fix for this should just be to update the netui-tree.js file in the resources directory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message