Hi Piotr,

can you please open an issue, and attach a small sample app?

regards,

Martin

On 9/27/07, Piotr <[EMAIL PROTECTED]> wrote:
>
> Hi users,
>
> I have upgraded recently MF to 1.2 version and I'm facing strange situation
> where in case of error with 500 code instead of my custom error page Tomcat
> displays its own.
> I have been trying to use the "org.apache.myfaces.ERROR_HANDLING" (true &
> false) but it doesn't influence the behavior at all.
>
> When I switched to the JSF RI 1.2 it worked fine just like with previous
> version of MF.
>
> Here is my web.xml error pages part:
> ...
>     <context-param>
>         <param-name>org.apache.myfaces.ERROR_HANDLING</param-name>
>         <param-value>true</param-value>
>     </context-param>
> ...
>     <error-page>
>         <error-code>500</error-code>
>         <location>/500.html</location>
>     </error-page>
>     <error-page>
>         <error-code>400</error-code>
>         <location>/index.html</location>
>     </error-page>
>     <error-page>
>         <error-code>403</error-code>
>         <location>/403.html</location>
>     </error-page>
>     <error-page>
>         <error-code>404</error-code>
>         <location>/404.html</location>
>     </error-page>
>
> Strange thing is that e.g. 404 error page works fine, like it should.
> Am I missing sth?
>
> I'm using MF 1.2, Facelets 1.1.13 and Tomcat 6.0.14.
>
>
> Thx for all replies
> Piotr.
> --
> View this message in context: 
> http://www.nabble.com/error-page-not-working-in-MF-1.2--tf4525353.html#a12911387
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>


-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Reply via email to