On Thursday 19 July 2001 10:58 pm, you wrote:
> > 2. How can these subapps be mapped to their pipelines?
> >
> > <my thought> Again this could be specified in the XML.
> > The Turbine Servlet could use something like a "PipeManager".
> > The PipeManager could load it's mappings in init() and be keyed by
> > URL "context" as mentioned above. Each Pipeline would map to a
> > subapp. Each Pipeline would contain it's own module loader and
> > an aggregation of valves. Again *all* of this being configurable in
> > XML.
>
> I think more like an AppManager not a PipeManager. The pipeline used by
> the application would be defined in an application descriptor. The
> application descriptor would house all the app specific config info
> and the pipeline definition would be contained within the app descriptor.
Then what to do with actions ( you kinda mention this in your notes )
...relating specifically to security? What if I want a single security
policy ( action ) to govern all the subapps? I need a way to specify this at
the top of my configuration. Otherwise I'd need to duplicate this in each
subapp configuration. Maybe a "root" app or pipeline that can perform filters
( valves) on the request with nested apps.
Something like this:
<app pipeline="root" map="/">
<valve name="accesscontrol"/>
<app pipeline="subapp1" map="/subapp1">
<valve>
....
</app>
<app pipeline="subapp2" map="/subapp2">
<valve>
....
</app>
....
<valve name="postprocess"/>
</app>
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
