If no implementation has been provided, you have a problem anyway.
Module.getService will throw an ApplicationRuntimeException when you try
to get that service.
If you catch that, you will know. If you are dynamically providing
implementations, you are already digging into this stuff, so you could
add your own hook...

Steve Gibson

-----Original Message-----
From: Nelson, Randy [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 18, 2004 4:28 PM
To: hivemind-dev@jakarta.apache.org
Subject: [SPAM] - RE: Grabbbing a reference to the registry - Email has
different SMTP TO: and MIME TO: fields in the email addresses


What if need to access to the valueForSymbol() method on the
RegistryImpl?
We use that to determine if a service body (implementation) has been
associated with a service head (interface).

However, Module doesn't have a cover method for that, and the
expandSymbols() doesn't return the information that we need.

-Randy

-----Original Message-----
From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 11:05 AM
To: hivemind-dev@jakarta.apache.org
Subject: RE: [SPAM] - Grabbbing a reference to the registry - Email has
different SMTP TO: and MIME TO: fields in the email addresses


There's a kind of triad between Registry, RegistryInternal and Module.
The
Registry is the "outside
looking in" view of the Registry.  RegistryInternal is the inner
workings
and Module is a gateway
into RegistryInternal for services and contributions within a specific
module.

The need for this doesn't exist yet, but in the future, the three
interfaces
will diverge more, as
we add some support for visibility (of services, configurations and
schemas).

Module duplicates a bunch of methods from RegistryInternal, and adds
automatic qualifiactons of
module-local IDS to fully qualified ids.

--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com


> -----Original Message-----
> From: Steve Gibson [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, June 17, 2004 11:02 AM
> To: hivemind-dev@jakarta.apache.org
> Subject: RE: [SPAM] - Grabbbing a reference to the registry - 
> Email has different SMTP TO: and MIME TO: fields in the email 
> addresses
> 
> 
> My question is - do you really need a registry instance? Can't you get
> what you need from Module?
> Module.getService can take a fully-qualified serviceId...
> 
> Steve Gibson
> 
> -----Original Message-----
> From: Nelson, Randy [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, June 17, 2004 10:55 AM
> To: hivemind-dev@jakarta.apache.org
> Subject: [SPAM] - Grabbbing a reference to the registry - Email has
> different SMTP TO: and MIME TO: fields in the email addresses
> 
> 
> We have a ServiceBroker which associates different service
> implementations
> with a head declaration and checks service versions.
> 
> In the ServiceBroker, under Hivemind 1.0 alpha, we would use the
> registry to
>  1. get a given module, then use the Module to get the 
> ServicePoint (was
> ServiceExtensionPoint) for a ServiceID. 
>  2. resolve "valueForSymbol()"  
> 
> We were able to make the registry available to this internal 
> service by
> using the "set-module" rule on a contribution object, then asking this
> module for the registry  (module.getRegistry()).
> 
> 
> However, under the 1.0beta-1, several items have changed, 
> including the
> fact
> that there is no longer a "getRegistry()" method on Module.  The
> ModuleImpl,
> does have a setRegistry().
> 
> Question: How can/should I get ahold of the registry now?  
> 
> Thanks,
> Randy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to