Yes, the rpc libraries were quite terrible at the time. +1 on using Jackson. 
The documentation is lacking in examples, but I can vouch for it being both 
reliable and fast.

/Janne

On Jan 13, 2013, at 16:18 , Andrew Jaquith <[email protected]> wrote:

> Two quick points:
> 
> 1. In the 3.0 branch I used Jackson, which worked pretty well and is fast
> 2. The Stripes interceptor in 3.0 includes code that automatically decodes 
> JSON (using Jackson) and dispatches to the correct action based on URL. It 
> essentially gets rid of the bridge.
> 
> On Jan 13, 2013, at 8:22 AM, "Harry Metske (JIRA)" <[email protected]> wrote:
> 
>> 
>>   [ 
>> https://issues.apache.org/jira/browse/JSPWIKI-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552196#comment-13552196
>>  ] 
>> 
>> Harry Metske commented on JSPWIKI-276:
>> --------------------------------------
>> 
>> Hmmm, jabsorb doesn't seem to be maintained either anymore now. Cannot find 
>> the UpgradeGuide, many Google searches end up in 
>> http://code.google.com/p/jabsorb where I don't find anything useful except 
>> the downloads.
>> 
>> Seems they continued again with json-rpc ?: 
>> http://code.google.com/p/json-rpc/ .
>> 
>> I personally do not have much knowledge or experience with json.
>> Does anyone else have a good suggestion where to go (or just leave it the 
>> way it is) ?
>> 
>>> 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, 2.9.1
>>>          Reporter: Jorge Ferrer
>>>          Assignee: Harry Metske
>>>          Priority: Trivial
>>>           Fix For: 3.0
>>> 
>>> 
>>> 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.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to