Sure
org.apache.cocoon.ProcessingException: Application is required
at
org.apache.cocoon.webapps.authentication.context.AuthenticationContext.s
etXML(AuthenticationContext.java:255)
at
org.apache.cocoon.webapps.authentication.context.AuthenticationContext.l
oadApplicationXML(AuthenticationContext.java:892)
at
org.apache.cocoon.webapps.authentication.components.DefaultAuthenticatio
nManager.login(DefaultAuthenticationManager.java:303)
at
org.apache.cocoon.webapps.authentication.acting.LoginAction.act(LoginAct
ion.java:117)
Laurent
> -----Message d'origine-----
> De�: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Envoy�: jeudi 30 octobre 2003 10:10
> ��: [EMAIL PROTECTED]
> Objet�: RE: RE : RE : [auth-fw] NPE in Application Manager
>
> Hmm, are you sure? I'm not aware of any changes in the authentication
> framework after I committed the patch. Hmm, can you please show
> the stack trace again?
>
> Thanks
> Carsten
>
> > -----Original Message-----
> > From: Laurent Trillaud [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, October 30, 2003 9:40 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE : RE : [auth-fw] NPE in Application Manager
> >
> >
> > Hmmm, the fix worked, but I just going to build a brand new cocoon
from
> > the Cocoon-2.1 CVS and the bug is still here.
> > It seems that the fix has been overwritten!
> > Laurent Trillaud
> >
> > > -----Message d'origine-----
> > > De�: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> > > Envoy�: vendredi 24 octobre 2003 15:03
> > > ��: [EMAIL PROTECTED]
> > > Objet�: RE : [auth-fw] NPE in Application Manager
> > >
> > > Laurent Trillaud wrote:
> > > > Great, it's working. :-)
> > >
> > > > But I have detected something weird, or may be something that I
> > don't
> > > > understand.
> > > > If you declare an application without the loadondemand, this
> > application
> > > > is loaded at login time, but this loading fails in
> > > > [EMAIL PROTECTED] because the application name is
not
> > > > set.
> > > > If I put the name in the sitemap like that the loading succeeds.
> > > > ...
> > > > <map:act type="auth-login">
> > > > <map:parameter name="handler" value="portalhandler"/>
> > > > <map:parameter name="application" value="MyApp"/>
> > > > <map:parameter name="parameter_name"
value="{request-param:name}"/>
> > > > <map:parameter name="parameter_password"
> > > > value="{request-param:password}"/>
> > > > <map:redirect-to uri="portal"/>
> > > > </map:act>
> > > > ...
> > > > I think that this design is weird. In
> > > > [EMAIL PROTECTED], we have a loop on each
> > > > application in the handler but only one will be loaded.
> > > > Is it the right design or is it a bug?
> > >
> > > It's another bug :) I just committed a fix, so it should now
> > > work for you (hopefully). You shouldn't need to specify
> > > the application in the login action.
> > >
> > > Thanks for spotting this!
> > >
> > > Carsten
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
