[ 
https://issues.apache.org/jira/browse/JSPWIKI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134558#comment-14134558
 ] 

David Vittor commented on JSPWIKI-566:
--------------------------------------

Hi Harry,

The idea here was that this is a framework for writing AJAX. It can co-exist in 
parallel with the current JSONRPCManager, and should be able to do everything 
it can do. By having this framework available, we can then start deprecating 
the any existing json-rcp code and moving it to this new framework (and 
hopefully the migration should be pretty quick). But I was kind of hoping to 
distribute that part amongst the community :)

However I will try and write a guide on how to migrate from json-rcp to ajax, 
and might use one of the existing functions as an example. We'd need that for 
the release notes anyway.

The other things I was considering, is I'm not sure how much the json-rcp is 
used in the community, so maybe for the next release we can mark it deprecated, 
and then remove it at a later release, giving people time to transition. Either 
code provides for both frameworks to be available, and gives us something to 
move json-rcp to.


> 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)

Reply via email to