[ http://issues.apache.org/jira/browse/BEEHIVE-637?page=all ] Krista Baker closed BEEHIVE-637: --------------------------------
Verified fixed at svn revision 169890. All tagIds in the html doc references have been updated for the default lookup scripts. > netui tag libraries documentation needs updated tagId attribute descriptions > ---------------------------------------------------------------------------- > > Key: BEEHIVE-637 > URL: http://issues.apache.org/jira/browse/BEEHIVE-637 > Project: Beehive > Type: Bug > Components: Documentation > Versions: V1 > Reporter: Krista Baker > Assignee: Krista Baker > Fix For: V1 > Attachments: tagdocpatch.txt > > The following netui tags contain the tagId attribute and the same (or > similar) tagId attribute descriptions in the documentation: > anchor, area, body, button, checkBox, checkBoxOption, divPanel, fileUpload, > form, hidden, image, imageAnchor, imageButton, label, radioButtonOption, > select, selectOption, span, textArea, textBox, tagId, and treeItem. > 1. The following lookup functions are considered "Legacy" and are not > generated without adding a "legacy" line in beehive-netui-config.xml: > getScopeId and getNetuiTagName. > In the first paragraph of the attribute description the last sentence says: > In this case, the real id rendered in the browser may be looked up through > the JavaScript function getNetuiTagName( tagId, tag ). This last function > name should be replaced by: lookupIdByTagId ( tagId, tag ). > These changes from getNetuiTagName to lookupIdByTagId should be replaced in > all occurences of the description in all tags that contain the tagId > attribute. > 2. The link at the end of the description says: For detailed information on > using the function ... see <a>Using JavaScript in Page Flow and Portal > Applications</a> This anchor links to the following page: > file:///C:/appbash/apache-beehive-incubating-20050510-svn169446/docs/apidocs/guide/netui/guide/conUsingJavaScript.html > which does not exist. > bash05102005 -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
