Re: Minimal set of component attributes?

Berin Loritsch wrote:

> I have some rudimentary support for using attributes to represent
> components and their roles.  The core mechanisms in Fortress have
> not changed, but I am adding a new RoleManager that can read a
> resolve components from several different jars automatically.
>
> It will be used in my GUIApp system--but I want to put it in Fortress
> before we release as well.  I want to mark the services and components
> with a minimal set of attributes--which will get our users used to
> added functionality in Merlin and Phoenix.
>
> I can think of the following *core* attributes:
>
> @avalon.service   -- Required for marking role interfaces. 


Are you using this as a marker attribute in an interface soruce or a 
attribute of a component class?

i.e. @avalon.service <---- this is a work interface
or  @avalon.service xxx.yyy.MyInterface <--- this class exposes this 
service as a work interface

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:[email protected]
http://www.osm.net