[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2283?page=c...
]
Max Rydahl Andersen commented on HHH-2283:
------------------------------------------
if the validator runs in to an error it does throw an exception. ...so ?
p.s. hbmlint is a better place to add more customization to the validation if that is what
you are after
SchemaValidator.validate() should throw or collect exception
------------------------------------------------------------
Key: HHH-2283
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2283
Project: Hibernate3
Type: Improvement
Components: core
Versions: 3.2.0.ga
Reporter: Mark Gorokhov
Original Estimate: 2 hours
Remaining: 2 hours
Method SchemaValidator.validate() logs SQLException without any option to retrieve this
exception in the client code.
EXAMPLE: Hibernate+HSQLDB is used in standalone application with "in-process"
connection. Only single DB connection could be created. Let's start first application
instance and then the second application instance. The second one will throw SQLException
which ends up in a log file and does not reach the client code.
Method SchemaValidator.validate() should throw an exception to be caught the client code
or at least to collect exceptions like SchemaUpdate.getExceptions().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira