cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Timberlake <>
Subject Re: 3 questions...
Date Wed, 20 Aug 2003 22:16:28 GMT

The following is an extract from a component I wrote in which I access
the UserContext. This code retrieves the UserHandler and then gets a
DocumentFragment of the contents of the data element which I then
process further using standard DOM methods.
I hope this helps a bit.

SessionManager sessionManager = (SessionManager)
     Session session = sessionManager.getSession(true);
     UserState userState = (UserState)
     if(userState != null)
         UserHandler userHandler = userState.getHandler(handler);
	DocumentFragment fragment =

Olivier Billard wrote:
> Hi Andrew,
> I have a little question about retrieving the "data" tag content.
> How could you get the content ? It seems that there is no corresponding 
> output module, and when I set a serializer instead of the classic 
> <map:redirect-to uri="login"/> to view the <data> content, I have the 
> following error :
> "You must set a generator first before you can use a serializer."
> So how can you access the data content ?
> Thanks,
> -- 
> Olivier
> On 20/08/2003 09:21, Andrew Timberlake wrote:
>> Sonny
>> Try walking the programming logic. Starting with 
>> org.apache.cocoon.webapps.authentication.acting.LoginAction
>> and follow how cocoon deals with each step of the process.
>> One thing to watch out for is when you get code such as 
>> manager.lookup(XXX.Role) this is referencing an Interface to which an 
>> implementation class has been assigned within cocoon.xconf. An easy 
>> way to identify the implementation class is to look for a class named 
>> in one of three common ways:
>> <NameOfInterface>
>> Simple<NameOfInterface>.java
>> or
>> Default<NameOfInterface>.java
>> and then continue walking the logic. This is a great way to figure out 
>> how cocoon works internally which will help your use of cocoon 
>> considerably.
>> Sonny Sukumar wrote:
>>> Andrew, thank you for your time and effort to find the info below for 
>>> *is* proving helpful.  See couple questions below...
>>>> I'm not sure that a login tag is created. The temprary context 
>>>> should contain an XML fragment which looks like the following:
>>>> <authentication>
>>>>     <failed/>
>>>>     <data>Any error message which was set by your authentication 
>>>> handler</data>
>>>> </authentication>
>>>> This I get from reading the few lines above the 
>>>> SessionConstants.TEMPORARY_CONTEXT code I mentioned above.
>>> Ahh, that's strange...the docs mention nothing about a <failed/> tag 
>>> from what I read.  Is this just a tagging element of some sort?  I 
>>> mean, is it just always an empty element that just signals the 
>>> authentication failed?
>> I think it is just a flag. Remember that this block is providing a 
>> generic process for handling authentication. Any block will try to 
>> provide a solution for the common problem but you don't need to use it 
>> to solve the problem in the way it was written specifically.
>> Example is that you need not check for the failed element to know that 
>> the auth failed as the action will pass the processing onto your 
>> failed pipeline fragment in which case, you simply need to retrieve 
>> the content of the data element and continue.
>> Andrew
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message