On Fri, 13 Sep 2002 07:13, Berin Loritsch wrote:
> If we use the Manifest file, then I would like to have entries like
> this:
>
> Avalon-Type: Service|Component|Extension|ExtensionHandler
Why restrict it to these types? Does not ExtensionHandler imply Component?
Could you not determine Extension/ExtensionHandler via inspection of the info
files?
> If we use an XML file, can we limit ourselves to only one?
I have been flip-flopping between one xml file with just two elements
(component and service) and two xml files with extensible set of types. If
you have a policy of one classloader per jar, it makes it easier if you
separate the xml files. (Or you will need two passes - one to pick up
services and one to pick up components).
I ended up separating them similar to way Myrmidon does (which I think was
inherited from Cocoon). Something like
roles.xml:
<roles>
<role shortName="component">
<role shortName="service">
<role shortName="extension" impl="o.a.a.Extension">
</roles>
types.xml:
<types>
<component impl="o.a.MyComponent"/>
<component impl="o.a.MyComponent2"/>
<service impl="o.a.MyService"/>
<extension impl="o.a.MyExtension"/>
</types>
I have also experimented with just a types.xml that had <type/> elements that
allowed you to define "category". Not sure on the best approach.
--
Cheers,
Peter Donald
------------------------------------------------
"No. Try not. Do. Or do not. There is no try."
-- Yoda
------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
