Hi Ant, It seems I've missed Simon's commit and didn't update jsonp binding sources at the time I was checking them out... That was the problem I wanted to bring up. I've checked up the new getJSONRequestStringArray() method and I've spotted that the typesIndex is never incrementing... Can't estimate what's the impact of not having quotes for all string objects in JSON and if this is handled the right way by the databinding layer, maybe Simon can give us more details?
Looking at the code, I find the abstraction very useful and I would like to use this databinding layer for the comet binding too so we can have conversions done in one place. All that's required for parameters is to pass the string array as a Object[] type and tuscany will take care of everything else? How is it working actually? Are the objects passed through another layer that takes care of conversions before making the service call? I can also see that the tuscany-databinding-json artifact is used in binding-jsonp-runtime only with test scope. Does this mean every project using jsonp binding needs to declare tuscany-databinding-json as a dependency as well or tuscany will fail json conversion? Wouldn't that try to convert all the objects passed in the service calls made in the composite? On Tue, Aug 31, 2010 at 2:10 AM, Luciano Resende <[email protected]>wrote: > On Mon, Aug 30, 2010 at 3:51 PM, ant elder <[email protected]> wrote: > > > > If you really want to have all this is in just a single binding then > > why not call it binding.http? Merging this function into binding.rest > > makes no sense at all. REST is not RPC. > > > > ...ant > > > > I would like to have one binding, independent if we call it REST or > HTTP... some approach to easily provide some transition to that path > is also described in [1]. > > [1] http://markmail.org/message/gooxl7dfaxahxr7h > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
