It works,
Thanks a lot.
I did not add the application parameter through. I might need it later,
but the session context is accessible without it.
I'm sorry for my stupidity in not seeing the parameter. I must have
overlooked it at least three times. I'm still puzzled about something
though. When I log into the sunSpot portal in the latest CVS build (which
is using "sunspotdemohandler" as the handler) and then access the session
context with a handler called "sunRise", I get the context too!! This is
why I assumed that the default handler to store the values was called
"sunRise". I didn't automatically link the handler to the name of the
context. Stranger still: when I try to access the context using
"sunspotdemohandler" (the name of the handler in the cocoon portal) as the
context name, I can't access it.
The sitemap:
<map:match pattern="sunspotdemo**">
<map:act type="sunRise-auth">
<map:parameter name="handler" value="sunspotdemohandler"/>
<map:parameter name="application" value="sunspotdemo"/>
This works:
<resource xmlns:sunshine="http://cocoon.apache.org/sunshine/1.0";>
<sunshine:getxml context="sunRise" path="/"/>
</resource>
This doesn't:
<resource xmlns:sunshine="http://cocoon.apache.org/sunshine/1.0";>
<sunshine:getxml context="sunspotdemohandler" path="/"/>
</resource>
Can you explain this behavior, please?
Bert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
