[ http://issues.apache.org/jira/browse/COCOON-1772?page=comments#action_12375687 ]
Carsten Ziegeler commented on COCOON-1772: ------------------------------------------ Yes, this makes sense, thanks! I guess you're right that the incorrect code should be somewhere else. I'm wondering if this is due to the call of the flow script. Usually, the auth-protect action should set the state. The state is stored in a request attribute, so unless you're doing a redirect or something like that it should be available. Would it be possible to provide a simple test case? > [PATCH] AuthenticationContext: NullPointerException > --------------------------------------------------- > > Key: COCOON-1772 > URL: http://issues.apache.org/jira/browse/COCOON-1772 > Project: Cocoon > Type: Bug > Components: Blocks: Authentication Framework > Versions: 2.1.8 > Reporter: Antonio Fiol > Assignee: Carsten Ziegeler > Attachments: AuthenticationContext.java.patch, > AuthenticationContext.java.patch > > We got a NullPointerException on AuthenticationContext. > Apparently, this.getState() is returning null. > We did not investigate it any further, and supposed that a null RequestState > means a null applicationName, which is reasonable as we have no "application" > configured. > Patched, and it works perfectly here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
