404 when the id is not found is not working

[lucascs]

Since ParameterLoader is now an Observer, it can't stop the interceptor stack.

So, if the id is not found on database, even if result.notFound() is called, the controller method will also be called. =/

Maybe we should change ParameterLoader to be an Interceptor again, and use methodInfo to set the parameter directly.

[garcia-jj]

Hmm, @Turini what you think?

[Turini]

hum, I think return to an interceptor would be the simpler option here.

[garcia-jj]

I'm thinking about this issue... and I was always opposed to throws an not found when an entity is not found. I think that is a decision that application knows, and not the framework.

What you think to change this behavior to same as JPA says: if an entity is not found, only returns null. So the application can decide if will throws an Exception, or a not found page, or another approach.

[lucascs]

If the id is on the URL and the entity is not found, it's a 404. We shouldn't return null to the user.

[Turini]

I agree with Lucas' comment. It's a 404

[rafaelGuerreiro]

Guys, could you, please, re-validate the PR #31? Should I add docs about it?