These 2 questions are based on this doc: http://cocoon.apache.org/2.1/developing/webapps/authentication.html
1.) The doc states "If the authentication is successful, a session object is created on the server (if not already done). If the authentication fails, the error information delivered by the authentication resource is stored into the temporary context (which is named simply 'temp')."
Question: Where is this 'temp' context stored, if not in the session?
2.) For the auth-login action, request parameters are passed to it like:
<map:parameter name="parameter_userid" value="{request:name}"/>
<map:parameter name="parameter_password" value="{request:password}"/>Question: Is this "request:" syntax generally available to pass request params to all actions?
3.) A handler is also configured like this:
<handler name="unique">
<!-- The login resource -->
<redirect-to uri="cocoon:raw://loginpage"/>
<authentication uri="cocoon:raw://authenticationresource"/>
</handler>Question: Is it necessary to use the "raw:" subprotocol here for not forwarding request params?
It says "...this resource is requested by the framework with the given parameters from the auth-login action" referring to the authentication resource, so perhaps the "raw:" subprotocol is there to prevent duplicate request params? I'm just guessing here...
Thanks,
Sonny
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
