David Sean Taylor wrote:
>
> So what you are suggesting is that Jetspeed has only one entry point from
> the Turbine servlet.
> Now it is the Turbine Screen org.apache.jetspeed.turbine.screens.Home.
>
> With the subclassing of the Turbine servlet, it gave me some ideas about
> using 'interceptors' to provide services declaratively. For example, the
> profile service could intercept requests so that it doesnt have to be
> specifically called from every Jetspeed module. If we only have one
> module-entry point Turbine screen (or action), the same can be accomplished.
>
The Turbine subclass is not there to stay unless there are some very important
functionalities that Turbine does not provide a hook for. What you want to do
with "intercepting" requests can be done be using a custom SessionValidator.
I'm not sure PSML should be used to replace navigations, screens, etc...
It is designed for allowing the user to specify its content within a
well-defined screen space and let him customize it. Everything out of this
screen space is off limit as far as the user is concerned and should be
clearly separated in the site structure, hence the notion of layout and
navigation in Turbine.
In Jetspeed it will certainly be possible to reference Portlet contents
in navigations/layouts without PSML if you really want.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
