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 do with each of forms that are
invented.
In the case of the binding implementation I'm working with, the
reference binding uses the uri to determine the target service. When
the URI is changed it is no longer valid as no service exists with at
the modified URI.
Any ideas on how this could be implemented without forcing the bindings
to understand $self$ references?
Thanks.
ant elder wrote:
I think its actually a bug in the jsonrpc binding that its using the
component self reference, but that aside, this still seems odd to me. Just
because a particular binding is on a service how can it be sure that that
same binding will work as a reference? Some binding's don't support
references, some have different attributes for services or references, on
some binding's the URI may include the reference name so this would end up
including $self$ in the URI.
...ant
On 5/18/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
The self references are created to support the
ComponentContext.createSelfReference() in a consistent way as regular
references.
In your case, if the binding.jsonrpc is declared under the component,
then
the component can only be assessed over jsonrpc binding (not even SCA
binding). And the component will be exposed as a json-rpc service. So
invoking the json-rpc reference handler is the correct behavior from the
client side.
Thanks,
Raymond
--
Matthew Sykes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
