Problem with custom 404 page mapping

[gutomarzagao]

In order to create a custom 404 page I made the following mapping inside web.xml:

<error-page>
    <error-code>404</error-code>
    <location>/404</location>
</error-page>

My goal was to have the /404 route treated by some controller. Unfortunately, this mapping causes a NullPointerException.

After some research I figure out that the problem is that the /404 request fired by the ERROR dispatcher is beeing missed along VRaptor code.

You can check the problem inspecting RequestInfo instance located at VRaptor class and RequestInfo instance located at DefaultResourceTranslator class. Usually they are the same instance with the same id. But when handling 404 error mapping URL, these 2 instances are different from each other.

[garcia-jj]

I that we can mapping dispatcher to ERROR too. There are no problems to use this dispatchers.

@lucascs What you think?

May be affects vraptor4.

[lucascs]

There is some issue when you add the ERROR dispatcher on VRaptor, I don't remember which issue. But it doesn't work directly.