Schaible, J�rg wrote:
Hi Leo,
may be I am getting something wrong here. FortressConfig is not a Configuration
at all, but mainly a wrapper for a Context object. For my components I am
currently not certain which informartion from the ServletConfig will be used when.
It is very likely I have to use Servlet parameters during the service call of a
container component. Therefore I would like to put the ServletConfig into the
context of my root container ... which seems not to be possible :(
Sure it is... I never got around to implementing this, but what you can
do is write a Context object that wraps a ServletContext. That new
Context object will take care of standard mappings (i.e. for the context
directory and the work directory). Any initial configuration items and
parameters would be accessible via the get() method.
Does that sound feasible?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
