Please see my comments inline.
Thanks,
Raymond
----- Original Message -----
From: "Simon Laws" <[EMAIL PROTECTED]>
To: "tuscany-dev" <[email protected]>
Sent: Tuesday, November 27, 2007 1:18 AM
Subject: Domain level autowiring etc.
Should autowiring work at the domain level? It doesn't at the moment. It's
only considered within a contributed composite. To autowire at the domain
level we have to adjust the way that service endpoints and references are
matched, i.e. extend the process to looking at interfaces and policies.
Domain-level autowiring should be supported. The matching algorithm should
check the interfaces and policies and the same rules apply to both autowire
and regular wires.
In line with moving the registration and lookup code out of the SCA
binding
[1] I'm thinking about tidying the code in this area to make future
reliability scenarios easier to cope with (by making sure all the
processing
is in one place with a clear services of associated events) so now would
be
a good time to cover other outstanding issues. I think the outstanding
things are
Domain level wire elements in stand alone composites.
Domain level autowiring
A related question: For the @target attribute of <reference> or <wire>
element, the URI is <componentName>/<serviceName>. Can the URI point to a
component service in the SCA domain or does it have to be in the same
composite?
Are there any more that people can think of?
Regards
Simon
[1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg25636.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
