| hi Steve Ebersole, I changed my mind after I realized how bad the impact is on day to day usage. It wasn't very clear initially, but any dumb mistake results in either getting an unexpected NPE or a confusing message like "there is no PU with this name". By "dumb mistakes" I mean there's a whole lot of cases, for which we normally give an helpful error message but they are all swallowed and hidden by default:
- wrong credentials to the database
- any configuration property doing something invalid
- any mapping issue which would normally get an exception
- forgot to add the right JDBC driver on classpath
- ...
I think we need to distinguish between:
- an "ERROR" in configuration, e.g. an internal exception
- a case of "this configuration is not for us, let another JPA provider try"
Logging such exceptions as ERROR seems reasonable; it certainly would be very helpful. |
