[
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
I've managed to achieve this. And it prevents the start up errors that we are
getting. I've done it using an AJAX with simple HttpServlets and a rest based
implemenation for parameters and methods (See SearchManager).
Patch is attached, although it's not 100% there. The UI is still not processing
the results correctly, so there is still something wrong with the Javascript,
but the backend ajax is processing correctly (as my logs).
However there are a few general comments.
1. I've added GSON to the project - I'm assuming this is ok
2. Although in the Java backend its possible to be backwards compatible (i,e.
use both RPC and AJAX (done by extends HttpServlet and implements RPCCallable),
this is not so easy in the javascript). So it's kind of all or nothing.
3. Do I remove the old code from SVN (once this works), or do we comment it
out, or do we somehow mark it as deprecated?
If someone could review this patch and let me know if there are any issues
(e.g. security concerns, etc), would be good to address these early.
> 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, 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)
