Jason van Zyl wrote:
>
> The TurbineServletService is a place where all the information
> about the servlet is available. You can probably use some of the
> methods in there for what you are doing. I borrowed this
> from Jetspeed, so it may be of use to you for this task?
>
For content URIs, yes. But there is a different use, that is URI
corresponding to actions and events of the different portlets.
Those URIs will need to be managed by Jetspeed on a per-request or per-session
basis, and are not suitable for a static webapp object.
> I was trying to make the TurbineServletService the single
> place to store info about the webapp. I haven't looked
> at DynamicURI and friends, but would it be possible to
> use the TurbineServletService in the DynamicURI class?
>
Currently all DynamicURI variants use RunData as source of webapp/request info.
I don't think the servlet service is replacing rundata.
I'll take a look at the TurbineServletService, in any case.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
