After updating the JSON-RPC reference to use the Jabsorb client to make remote invocations, the results are being returned as Beans (e.g array of items). This seems to work fine if the JSON-RPC reference binding provider sets the databinding to JSON and if JAXB databinding is available on the classpath. The issue I'm having is that, when running applications that exclude JAXB databinding (e.g in a app engine environment) I get exceptions complaining it can't transform String to JSON. I want to go ahead and remove the databinding reset in the JSON-RPC reference binding provider, which make things working in both environment, but want to see if people see any side effects on this.
-- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
