I'm having trouble parsing this. Are you talking about an SCA
registry, or a WSDL registry, or the mechanism for locating it (via
IoC as Ant described or something else)?
I was saying that in an IoC world there is /no/ provider part of the
API - a user never locates anything, they declare dependencies and
the container resolves them. The dependency would be on the actual
client interface (SymbolSpace.Registry I guess but I've already
admitted to not grokking the interfaces).
--
Jeremy
On Aug 30, 2006, at 11:28 AM, Yang ZHONG wrote:
Can someone propose a SCA specific API mentioned by Jeremy please?
Something like
interface ScaRegistry
{
Definition getDefinition (String nameSpace);
Message getMessage (QName);
}
I don't know the SCA requirement much enough to make such proposal.
At the same time, we can practise IoC in ScaRegistry service locating.
I hope I can learn from that practice and update the registry
generic API
accordingly.
Thanks for pointing out a nice mechanism.
On 8/30/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Aug 30, 2006, at 10:49 AM, Jeremy Boynes wrote:
> As part of Tuscany there should not be any mechanism in a API for
> "service location" - that is the responsibility of the IoC
container.
>
+1 (which nicely avoids external dependencies on some locator
implementation and evil Singletons)
> --
> Jeremy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Yang ZHONG
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
