I intend to write a SessionContextSelector and
tried to use a SessionManager just like the SessionTransformer does. But it
seems that there is no SessionManager provided to a Selector while a Transformer
gets one.
Am I right?
Why is that so?
And: Has anybody a suggestion for a
workaround?
)
at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentMa
nager.java:227)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManag
erProxy.lookup DefaultComponentFactory.java:314)
...
Cheers,
Jan
-Original Message-
From: Jan Bromberger [mailto:[EMAIL PROTECTED
Message-
From: Jan Bromberger [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 05, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: No SesionManager provided for Seleector?
I intend to write a SessionContextSelector and tried to use a
SessionManager
just like
map:serialize type=xml/
/map:match
So it is created by the session transformer before the select state.
I have now commented out the session create statement.. But nothing changes.
Cheers,
Jan
Und danke fuers helfen!
-Original Message-
From: Jan Bromberger [mailto:[EMAIL PROTECTED
No, sorry - it is not. Actions, Matchers and Selectors are executed during
processing of the sitemap immediately - generators, transformers and
serializers
are executed after the complete xml pipeline is established.
So, first your selector is tested and at that time no context exists and
