Use rich argument marshaling for Java API eval and invoke

[sammefford]

XDBC protocol is tricky but allows specification of types, whereas REST API eval has a simpler API which accepts a JSON payload. Since the types are inferred in the REST API it does not have all the functionality of the XDBC protocol. This is not an issue for REST eval nor Node.js eval which is primarily intended to be used with JSON data payloads. However, the goal for the Java Client API is to eventually replace XCC, including all capabilities with XML and XQuery. To do that we will use XDBC as transport protocol to have all the features available to XCC.

[grechaw]

What is the gap? Do you see a future path whereby there is no more xdbc protocol? If indeed the Java Client API does end up replacing XCC, does that mean there is no more need for an XDBC protocol? I guess it just sounds like there are implications for this; and then the Java Client API no longer is a consumer of REST eval.

I'm not asking for any action, and I know you've already gone over this with folks, but it still seems like I'd like to understand the intentions for the future.

[sammefford]

Charles, I'm hoping #268 helps somewhat to answer your question. I've completed the implementation for this and I'm just waiting on a dependency in the server layer to push my changes. Now that my head is back in this I can see clearly that this change unlocks the ability to do #268.