Hi,me too - it hurts ;-)
still thinking over my application design. To get it right I would like to know your opinion.
In my application I will have a internal very basic interface for a content provider and several implementations that fullfil it. Actually I have set up my xconf in Fortress like:
<gfn-servlet-container>
<content-provider id="content-provider id" logger="content-provider">
<tiny-file id="tiny-file id" logger="content-provider"
content-dir-var="tiny" />
<tiny-xml id="tiny-xml id" logger="content-provider"
content-dir-var="tiny" />
<tiny-xml-file id="tiny-xml-file id" logger="content-provider"
content-dir-var="tiny" />
</content-provider>
</gfn-servlet-container>
Two questions in addition to this:
1/ what if you want to split the providers over different libraries, but hook them
into the same content-provider ? E.g. library a.jar has the xconf file above and
gets instantiated, but during the instantiation process needs to look at a lib/ext/
dir where there is b.jar and c.jar that also have xconf files which look similar
and need to be hooked into the same content-provider (basically they're extension
libraries that offer additional capabilities).
2/ how would you best provide different "sets" of providers that can be turned
on and off ??
E.g.
<content-provider>
.....
<content-provider-sets>
<content-provider-set id="default">
<provider-ref refid="tiny-xml-file id" />
</content-provider-set>
<content-provider-set id="all">
<provider-ref...
....
</content-provider-set>
<content-provider-sets></content-provider>
where content-provider would have some functions such as
activateSet( String setId ) getActiveSet(): String[]
(or alternatively each provider has a getActive()/setActive(boolean) method that
allows it to be activated)
Anybody any ideas ???
Thanks a lot!
- Filip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
