Sure, I will reopen this issue and change the message. Should we remove type + id from the message? Its already in the EntityNotFoundException.
New message could be:
@Message( value = "Returning null (as required by JPA spec) rather than throwing EntityNotFoundException, as the entity does not exist", id = 15013 )
When the exception call stack is displayed, we also show:
javax.persistence.EntityNotFoundException: Unable to find %s with id %s
Should we change the EntityNotFoundException message to use the "(type=%s, id=%s)" style?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Sure, I will reopen this issue and change the message. Should we remove type + id from the message? Its already in the EntityNotFoundException.
New message could be:
When the exception call stack is displayed, we also show:
Should we change the EntityNotFoundException message to use the "(type=%s, id=%s)" style?