Am 17.03.2006 um 21:52 schrieb David Sean Taylor:
Resolvers are running inside of the Jetspeed context, not in a
portlet.
Thus we are not coding against the Portlet API.
context.getRequest() returns the Jetspeed servlet's request, not a
portlet request. This attribute is only available in this manner
using the Portlet API, on a PortletRequest.
I see. That were my impressions, too.
Let me see if I can come up with a solution here shortly by hitting
the UserInfoManager component directly...
No need to hurry. I did exactly that by writing my own
CriterionResolver. However, getting it into the system was not quite
straightforward. Adding it to assembly/profiler.xml is easy, but in
the profiler admin portlet the Resolvers are hardcoded into the UI.
As a quick workaround I replaced an unused one with my
implementation. :-)
regards,
konrad
--
Konrad Hosemann
Software Development
EsPresto AG
Breite Str. 30-31
10178 Berlin/Germany
Tel: +49.30.90 226.766
Fax: +49.30.90 226.760
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
