[
https://issues.apache.org/jira/browse/JSPWIKI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134312#comment-14134312
]
Harry Metske commented on JSPWIKI-566:
--------------------------------------
Looking at the initial description (created by Janne 5 years ago :-) ), this
issue is about rewriting the complete Ajax handling stuff, at least that's my
view.
I just linked JSPWIKI-659 which has a long story about the problems with other
AJAX related functions, most importantly Search and the
NotSerializableExceptions.
Will this patch have the potential (or is it intended) to completely replace
the current implementation (like JSONRPCManager) ? That would be nice.
For now it looks an addition to the existing code, but let us know what you
think .
thanks for all you efforts in any case !
regards,
Harry
> 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: 3.0
> Reporter: Janne Jalkanen
> Attachments: ajaxDispatchServlet.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)
