[
https://issues.apache.org/jira/browse/JSPWIKI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Vittor updated JSPWIKI-566:
---------------------------------
Attachment: ajaxFunctions.patch
Hi Harry,
Once again thanks for the feedback. Most were small bugs and are fixed with
this latest patch. The java exception baffles me, and I don't know how it was
introduced, but I have added code to remove it, so admin pages work again.
Dirk, I've been looking into the Ajax calls you mentioned, and they are
available in both Prototype and Mootools:
* http://prototypejs.org/learn/json
* http://mootools.net/core/docs/1.5.1/Request/Request.JSON
I know jQuery, however I'm not currently confident enough with either of these
to make these changes. Would you be interested in working on top of this patch
to update this?
Let me know if you think this patch is worth commiting to the trunk, or what
you would like to do with it.
> 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)
