On Dec 16, 2008, at 6:11 AM, Roberto Rossi wrote:
Hi to everyone!
I'm trying to perform some customization using Jetspeed 2 (my
version is
2.1.2) but I need some help from you.
1. I need to put some "initialization" code before the execution of
all
my portlets populating the request with a particular attribute and I
want also to execute some "finalization" code before jetspeed
aggregation and rendering (in particular for all templates of Velocity
Portlets I want to put some object in the Context, useful for portlet
templates).
I found a solution for the "initialization" code using a newly created
Valve inside the Jetspeed Pipeline before the profilerValve, but I
cannot do the same for the "finalization" code. I created, in the same
way, another Valve after aggregatorValve (in the pipeline) but I
cannot
access the GenericVelocityPortlet.PORTLET_BRIDGE_CONTEXT request
attribute. Is there a way of doing that? Are the valves the right
place
of performing such actions?
Yes, I think so. Have you seen the CleanupValve?
See the WEB-INF/assembly/pipelines.xml
2. I'd like to force a language fallback for registered users using
the
profiler. I found there is a "language" resolver. How can I use it to
accomplish this?
See the "j1" profiling rule as an example of using mediatype, language
and country code fallback
Of course you can remove any of these, for example its valid to use
language without country code or mediatype
See more docs on profiling here:
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html
3. We are deploying many websites using Jetspeed 2, everyone inside a
dedicated Tomcat instance. Can I deploy multiple jetspeed context
inside
a Tomcat instance using, for example, different host directives in
server.xml configuration file?
No, only one Jetspeed context per Tomcat instance is currently
supported. We do support subsites to achieve the same:
http://portals.apache.org/jetspeed-2/guides/guide-subsites.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
