[ https://issues.apache.org/jira/browse/JSPWIKI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291284#comment-14291284 ]
brushed commented on JSPWIKI-566: --------------------------------- And for the HTML, it may look something like this: {noformat} ajaxHtmlCall:function(url,method,responseId,loading){ var update = document.getElementById(responseId); if (update){ update.innerHTML = loading||'Loading...'; } new Request.HTML({ url: this.JsonUrl+url, method:method, //defaults to 'POST' update: update }).send(); } {noformat} > AJAX server-side rewrite > ------------------------ > > Key: JSPWIKI-566 > URL: https://issues.apache.org/jira/browse/JSPWIKI-566 > Project: JSPWiki > Issue Type: Improvement > Components: Core & storage > Affects Versions: 2.10.1 > Reporter: Janne Jalkanen > Assignee: David Vittor > Attachments: ajaxDispatchServlet.patch, ajaxFunctions.patch, > ajaxFunctions.patch, ajaxFunctions.patch, ajaxFunctions.patch, test.html > > > The AJAX library we're currently using is a bit problematic, as it stores > non-serializable stuff in the HttpSession (causing all sorts of nasty > exception reports in default configurations of Tomcat, and preventing > clustering). It does provide a very nice, reflection-based interface so that > we can expose any class/method as a JSON endpoint, but this does not really > work well with our auth system. > We should replace the jabsorb stuff with a Stripes-native solution (possibly > with some extensions to allow particular beans to expose methods as if we > were using jabsorb). -- This message was sent by Atlassian JIRA (v6.3.4#6332)