Hello,
currently I am somewhat puzzled about what implementing as service (a.k.a. component)
and what not. In my application I have a tiny subset of a JNDI interface and wonder,
whether I should implement the "TinyContext" and "TinyDirContext" as service or not.
My current feeling (after the DaW "What is not a good component?") says no. The single
element in such a DirContext scenario that cound be a service, seems to be the initial
DirContext responsible using some kind of factory for the other elements.
Basically all services are installed during the initialization phase and I should
normally not create new ones on the fly - right?
Also I am confused how to setup services with the same implementation, but different
configuration in Fortress e.g. I have a content provider based on the file system at
location a, but I may also have another one reading the files from location b. I am
not that sure, how to define the roles and xconf properly. Can I use the same role
more than once, but use a different id and different attributes?
xconf:
<gfn-servlet-container>
<content-provider id="content-provider id" logger="content-provider">
<tiny-file
id="tiny-file1 id"
logger="content-provider"
content-dir-var="tiny1" />
<tiny-file
id="tiny-file2 id"
logger="content-provider"
content-dir-var="tiny2" />
</content-provider>
</gfn-servlet-container>
Regards,
J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
