- Original Message - From: "Matthew Sykes" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, June 06, 2007 12:31 PM
Subject: Re: CompositeBuilderImpl.createSelfReferences creates a $self$
reference using the service binding
I'm actually bumping up against one of the problems tha
Sebastien,
I should say that I'm working on a default binding that replaces the
Tuscany implementation. The URI isn't changed but new references are
created with target URIs that are unknown to the binding implementation
on the service side.
CompositeBuilderImpl.createSelfReferences creates
gt;
To:
Sent: Wednesday, June 06, 2007 12:31 PM
Subject: Re: CompositeBuilderImpl.createSelfReferences creates a $self$
reference using the service binding
I'm actually bumping up against one of the problems that ant has
described - the creation of $self$ reference URIs.
I don't believe a binding
Matthew Sykes wrote:
I'm actually bumping up against one of the problems that ant has
described - the creation of $self$ reference URIs.
I don't believe a binding implementation should have to expect to deal
with odd URI's that were generated by the runtime and I'm curious how
bindings are su
I'm actually bumping up against one of the problems that ant has
described - the creation of $self$ reference URIs.
I don't believe a binding implementation should have to expect to deal
with odd URI's that were generated by the runtime and I'm curious how
bindings are supposed to know what to
vice. So
invoking the json-rpc reference handler is the correct behavior from the
client side.
Thanks,
Raymond
- Original Message -
From: "ant elder" <[EMAIL PROTECTED]>
To:
Sent: Friday, May 18, 2007 9:32 AM
Subject: CompositeBuilderImpl.createSelfReferences creates a $self
9:32 AM
Subject: CompositeBuilderImpl.createSelfReferences creates a $self$
reference using the service binding
Debugging TUSCANY-1292 it looks like one part of the problem is that
CompositeBuilderImpl.createSelfReferences creates a new self reference for
each service on a component and adds every binding from t
Debugging TUSCANY-1292 it looks like one part of the problem is that
CompositeBuilderImpl.createSelfReferences creates a new self reference for
each service on a component and adds every binding from that service into
the new reference. That results is a JSON-RPC reference provider get used
which
