Gary Shea wrote:
On Fri, 22 Nov 2002, at 23:57 [+0100], Stephen McConnell ([EMAIL PROTECTED]:Yep.
There is a distinct difference between Type and Service. Imagine for
example a jar file container the service org.omg.CosTime.TimeService.
The TimeService interface is described by a class and a Service is the
meta info about the service. This service can exist indepedently of an
componet implemetation class (i.e. the service interface and meta
defintion can exist in a seperate jar from a component the provides the
service). On the other hand, types can declare that they provide
services - which basically means that a type manager when registering
types in its repository needs to be able to access/register services
from a service manager.
Are you saying that merlin supports Service jar manifest entries? Like: Name: blah/blah/someinterface.class Avalon: Service
If your doing something like navigation of a container, components and services, a service definition established from an Avalon: Service manfest entry allows the introuction of supplimentary attributes - but its totally optional - a service production declaration on a component type is sufficient.
Cheers, Steve.
That's the only way this distinction makes sense to me, otherwise no
information about the service's work interface (even its class name!) is
needed for assembly, and all information about a Service is derived from
various Type sources.
Regards,
Gary
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
