[
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 All,
It's done. The updated patch file here, is a complete working version without
the jsonrpc required. (mostly commented out)
I've tested:
* Quick Search
* Large file upload (progress bar)
* Page suggestions on edit "[pagelink"
* Custom plugins using ajax
* Firefox, Chrome and IE.
Not tested:
* Admin UserManagement.jsp (users search - not sure how to get there).
I've also found that Gson should be fine
1. Gson = https://code.google.com/p/google-gson/ = apache license
I'm happy to check this in, but would like someone to verify the work done.
If someone is just willing to volunteer to test I'll check it in.
> 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, 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)
