Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it

Description

We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools.

I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/wrong.

Environment

None

Activity

Show:
Max Rydahl Andersen
July 25, 2006, 11:20 AM

something like:

throw InvalidMappingException with type and path. e.g. "resource", "org/some/package/Blah" where today its just a generic MappingException

throw MappingNotFoundException (will in some cases be the cause for the above) with similar type and path when it can be identified that it is simply not there.

Max Rydahl Andersen
July 25, 2006, 4:26 PM

committed to HEAD for now.

Max Rydahl Andersen
July 26, 2006, 1:42 PM

in both 3.2 and HEAD now

Assignee

Max Rydahl Andersen

Reporter

Max Rydahl Andersen

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure