[ http://issues.apache.org/jira/browse/BEEHIVE-1027?page=comments#action_12361790 ]
Carlin Rogers commented on BEEHIVE-1027: ---------------------------------------- Here are some other thoughts about what might be done to fix the NetUI Tree XmlHttpRequest... The initial registered URLRewriter should be implemented such that it recognizes and handles "*.xhr". Then, we need to use a rewritten URL in the JavaScript for the tree so that the netui_tree.js routines can build a rewritten URL on the client side for the expand/collapse commands to the XHR servlet. Then on the server side, the servlet filter to register the desired/required URLRewriter (mentioned in the bug description) for the portal container would only register the specific rewriter for a scoped XHR request. Also, the netui_tree.js needs to support a scoped map of the information used to write/construct the rewritten URLs so that it can support multiple portlets/trees in the page. > NetUI Tree XmlHttpRequest support does not properly perform URL rewriting > ------------------------------------------------------------------------- > > Key: BEEHIVE-1027 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1027 > Project: Beehive > Type: Bug > Components: NetUI > Versions: V1 > Reporter: Carlin Rogers > Assignee: Carlin Rogers > Fix For: 1.1 > > The NetUI Tree XmlHttpRequest implementation does not support URL rewriting > correctly. The tree XHR is broken in a scoped environment such as a portal > when using a tree with runAtClient="true" because of this issue. > The javascript for client side NetUI Tree support is not implemented to > handle rewriting URLs. For the initial page of HTML containing a tree, the > server will write the tree node(s) with the expandPath attribute set to the > specific page flow controller with the tree. Then on the client side the > javascript routine getTreeCommandUrl() uses that along with the webAppName > (also written to the initial page) to construct the URL. This URL is not > rewritten. > In addition, the application in this scenario also needs to write a servlet > filter to register the desired/required URLRewriters with the > URLRewriterService before any XHR calls to the XmlHttpServlet. Otherwise, the > URLs used for the HTML of the nodes rendered via the TreeCRI will also be > incorrect. -- 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
