OK, this member of the community will bite :-)
Now that we have released 1.0, we should not break compatibility with
user applications or user extensions without a very good reason.
We should always try to deprecate previously supported APIs and keep
them working rather than disabling them. Is
I've had a quick look and i think should be possible to support both
approaches, i'll go give it a try. Once the sca.js approach is working and
the old scaDomain.js is used we could log a warning message saying its
scaDomain.js is deprecated.
...ant
On 10/25/07, Simon Nash [EMAIL PROTECTED]
I managed to get the scaDomain working for the JSON-RPC again. I have
also updated the helloworld-jsonrpc-webapp to use that, instead of a
local json.js proxy.
On 10/25/07, ant elder [EMAIL PROTECTED] wrote:
I've had a quick look and i think should be possible to support both
approaches, i'll
On 10/22/07, Luciano Resende [EMAIL PROTECTED] wrote:
The upgrade process is very harmless, two line of code, one for the js
reference and another for the reference declaration. Also, seems like
there are some bugs on the scaDomain.js [1] that would not happen
while using the manual
I have just committed some enhancements to JSONRPC binding. It should
now be able to work with the Tuscany Databinding framework (I
particulary tested with SDO). I have also added initial code to
support References for the JSONRPC Binding, although this is not
completely finished yet.
Note that
How about changing this to be a completely separate new binding? That way
we'll be able to keep backward compatibility - new users can use the new
extension but people already using binding.jsonrpc from the 1.0 release can
continue to use the old json-rpc-java based extension till they're ready to
The upgrade process is very harmless, two line of code, one for the js
reference and another for the reference declaration. Also, seems like
there are some bugs on the scaDomain.js [1] that would not happen
while using the manual reference. I also think that, having the two
very similar bindings
On 10/10/07, Luciano Resende [EMAIL PROTECTED] wrote:
To the specific question, the store sample is shipping the JSONRPC
proxy probably because the SCADomain.js does not have support for
components with multiple services as reported in [1].
As for a more broad number of enhancements around
To the specific question, the store sample is shipping the JSONRPC
proxy probably because the SCADomain.js does not have support for
components with multiple services as reported in [1].
As for a more broad number of enhancements around JSONRPC, I have
started to add support for Databindings [2],
