You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Heath Borders <he...@gmail.com> on 2004/12/08 21:10:51 UTC
Re: Exception mapping to error page in web.xml not working with tiles and myfaces ?
Ours works fine. Here are our error page definitions:
<error-page>
<error-code>500</error-code>
<location>/error.jsp</location>
</error-page>
<error-page>
<exception-type>org.apache.struts.tiles.TilesException</exception-type>
<location>/error.jsp</location>
</error-page>
<error-page>
<exception-type>javax.servlet.ServletException</exception-type>
<location>/error.jsp</location>
</error-page>
My guess is that your error is getting wrapped either by a
ServletException or a TilesException
On Wed, 8 Dec 2004 15:06:34 -0500, Cote.Mark@hydro.qc.ca
<Co...@hydro.qc.ca> wrote:
>
> We are not able to get the functionality of exception mapping to work.
> We are using myfaces 1.0.7 & tiles.
>
> I have an <error-page> entry in web.xml which I have mapped to an
> exception(derived from RunTime)
> which is thrown from a constructor in one of my BBeans. Whenever the
> exception is thrown, the mapping is never acknowledged and the BBean
> is processed in the regular way...but with errors since the data was never
> loaded.
>
> The <error-page> mapping functionality works well when I run a webapp
> not using jsf and tiles, but fails to work when used with them.
>
> Has anyone been able to get this functionality to work with jsf and tiles ?
>
>
> Thanks in advance !
>
> Mark
>
>
--
If you don't have a GMail account, I probably have 5 invites. Just ask!
-Heath Borders-Wing
hborders@mail.win.org