[
https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483852
]
Michael Dick commented on OPENJPA-176:
--------------------------------------
It looks like we just use type + " error" if the type isn't recognized.
+1 as it is, but I'm not opposed to changing type + " error" to "unexpected
error" or something similar.
> Exception prefixes should be human-readable
> -------------------------------------------
>
> Key: OPENJPA-176
> URL: https://issues.apache.org/jira/browse/OPENJPA-176
> Project: OpenJPA
> Issue Type: Improvement
> Components: diagnostics
> Affects Versions: 0.9.0, 0.9.6
> Reporter: Marc Prud'hommeaux
> Assigned To: Marc Prud'hommeaux
> Priority: Trivial
> Attachments: OPENJPA-176.patch
>
>
> OpenJPA prefixes all exception messages with a string of the form "<exception
> type|is fatal|version>", restulting in strings like
> "<4|false|0.9.6-incubating>
> org.apache.openjpa.persistence.PersistenceException". This isn't very useful
> to the casual observer, since no translation of the meaning of the fields is
> done.
> it would be nice if we translated the fatal and type parameters, so that the
> string looked like "<user-error|recoverable|0.9.6-incubating>".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
