Harry,
We are using straight ajax calls with cover the rpc protocol based on
the mootools library.
Look at the jsonrpc function in jspwiki-common.js, who does all the work.
The call is something like this:
Wiki.jsonrpc('rpc.name', [param1,param2], caalbackfunction);
dirk
On Tue, Oct 7, 2008 at 6:58 PM, Harry Metske (JIRA) <[EMAIL PROTECTED]> wrote:
>
> [
> https://issues.apache.org/jira/browse/JSPWIKI-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637550#action_12637550
> ]
>
> Harry Metske commented on JSPWIKI-276:
> --------------------------------------
>
> Well, according to http://oss.metaparadigm.com/jsonrpc/ it is indeed "end of
> the line" and has moved to jabsorb.
> I did some local experiments and followed the migration instructions from
> http://jabsorb.org/UpgradeGuide.
> There is only one thing where I get stuck, and that's because I can't find a
> jsonrpc.js in JSPWiki that should be replaced with the jabsorb version.
>
> Completing all other steps and building (with slf4j and slf4j-log4j) goes
> fine, it passes all tests and all webtests.
> Running it on my test server however I don't get instant search results from
> the Quick Navigation field top right. Pressing enter gives me proper results,
> and also using the Search page works fine.
> Do I need some javascript guru here.....
>
>> Use jabsorb instead of jsonrpc
>> ------------------------------
>>
>> Key: JSPWIKI-276
>> URL: https://issues.apache.org/jira/browse/JSPWIKI-276
>> Project: JSPWiki
>> Issue Type: Improvement
>> Affects Versions: 2.6.2
>> Reporter: Jorge Ferrer
>> Priority: Trivial
>>
>> jsonrpc seems to be unmaintained and jabsorb (http://jabsorb.org/) seems to
>> be the new fork of that project. Migrating should to be quite simple.
>> Besides the new features added to jabsorb, a very good reason to migrate is
>> because this type library is sensitive to security related bugs so it's very
>> desired to use one that is well maintained. Just in case.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
