It keeps mine, but it still refused to go to my error page, any hints
how to find where it fail?

Torsten

Am Mittwoch, den 18.10.2006, 09:57 +0200 schrieb Torsten Krah:
> Hm realized that i've got a warning:
> 
>  WARN main org.apache.myfaces.config.FacesConfigurator - More than one
> managed bean w/ the name of 'org$apache$shale$view$EXCEPTION_HANDLER' -
> only keeping the last
> 
> Hm which one it keeps - i hope mine?
> 
> Torsten
> 
> Am Mittwoch, den 18.10.2006, 09:14 +0200 schrieb Torsten Krah:
> > Looking at:
> > 
> > http://wiki.apache.org/shale/ExceptionHandling
> > 
> > i created a error handler which implements
> > org.apache.shale.view.ExceptionHandler.
> > 
> > I've than stored it in application scope - faces-config.xml:
> > 
> > <managed-bean>
> >             <managed-bean-name>
> >                     org$apache$shale$view$EXCEPTION_HANDLER
> >             </managed-bean-name>
> >             <managed-bean-class>
> >                     my.util.ErrorHandler
> >             </managed-bean-class>
> >             <managed-bean-scope>application</managed-bean-scope>
> >     </managed-bean>
> > 
> > Is this correct or wrong?
> > 
> > I've than debugged the application - my error handler does not get
> > called ... if the above one is right, it should be called, should it?
> > 
> > Torsten
> > 
> > Am Dienstag, den 17.10.2006, 22:02 -0700 schrieb Craig McClanahan:
> > > On 10/17/06, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > > >
> > > > https://issues.apache.org/struts/browse/SHALE-277
> > > >
> > > > Does anyone got it working - i mean the custom error page which is
> > > > configured through the param mentioned there.
> > > > If yes - any hints how to get it work or debug would be nice - because
> > > > the resolution is "not a problem", but for me it is one ...
> > > 
> > > 
> > > I closed the issue with that status because I could not reproduce the
> > > situation you have found yourself in (which is a prerequisite for fixiing
> > > such a problem :-).   Plus,  If you can tell me how to reproduce the
> > > problems you see, please feel free to reopen the SHALE-277 issue and 
> > > provide
> > > the instructions for how to demonstrate that the current code is broken.
> > > There is a use case in the shale-usecases app that works for me ... does 
> > > it
> > > work for you?
> > > 
> > > Craig
> > > 
> > > 
> > > kind regards
> > > >
> > > >
> > 
> 

Reply via email to