Hi Ichiro,

I was not aware about the change of the jsonrpc java implementation.
It seems that the upgrade would be the right thing to do , not clear what
the improvements really are -- I suggest to log an improvement ticket in
JIRA.


>From the error message, it seems the the jsonrpc server cannot map the
method onto the right RPCCallable java class.
Which json-rpc command is being send to the server ?



dirk


On Tue, Feb 4, 2014 at 12:07 PM, Ichiro Furusato
<ichiro.furus...@gmail.com>wrote:

> Hi Dirk,
>
> Apparently the com.metaparadigm.jsonrpc code is no longer current, replaced
> by
> a newly-named JAbsorb package, available from Google Code:
>
>   http://code.google.com/p/jabsorb/
>
> This looks to be written by the same author and represents a package name
> change and some minor changes.
>
> In looking into the hooks in JSPWiki it seems that the only requirement
> would
> be to alter the servlet package name in web.xml and change the imports in
> the
> JSONRPCManager from:
>
>   import com.metaparadigm.jsonrpc.InvocationCallback; (API)
>   import com.metaparadigm.jsonrpc.JSONRPCBridge;
>
> to
>
>   import org.jabsorb.callback.InvocationCallback;
>   import org.jabsorb.JSONRPCBridge;
>
> I've not been able to determine if the bridge has changed in any
> significant way from
> the JavaScript side of things, but ostensibily the method calls used seem
> the same,
> though the new implementation is missing the setDebug() method.
> registerCallback()
> and registerObject() are the same.
>
> I was just wondering if you already knew about this change and/or if you
> knew of
> any plans to update to this new package.
>
> Thanks,
>
> Ichiro
>
> [PS. and BTW, despite quite a bit of digging into the JSON RPC code,
> including a
> fair bit of debugging, I've not yet been able to successfully register a
> non JSPWiki
> object and get the bridge to respond with anything except a
> {"id":10000,"error":{"code":591,"msg":"method not found (session may have
> timed out)"}}
> But I keep digging... didn't think this would be so difficult...]
>

Reply via email to