Grails

Unexpected behaviour with Declarative Error Handling.

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.3
  • Fix Version/s: None
  • Component/s: URL mappings
  • Labels:
  • Environment:
    OSX (untested on other platforms)
  • Testcase included:
    yes

Description

When I define a exception url mapping for an exception that extends RuntimeException and url mapping for RuntimeException and a controller that throws an exception that extends RuntimeException the exception url mapping for the extended exception is never used.

Example configuration:

"500"                                   (controller: 'error', action: 'extendedRuntimeException', exception: ExtendedRuntimeException)
"500"                                   (controller: 'error', action: 'runtimeException', exception: RuntimeException)

Example controller action:

def throwExtendedRuntimeException() {
    throw new ExtendedRuntimeException()
}

A grails example project is attached

the responses from the following requests should be different.

http://localhost:8080/grailsbug1/test/throwExtendedRuntimeException
http://localhost:8080/grailsbug1/test/throwRuntimeException

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Dominic Clifton
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: