[
https://jira.jboss.org/browse/JBIDE-6103?page=com.atlassian.jira.plugin.s...
]
Vitali Yemialyanchyk commented on JBIDE-6103:
---------------------------------------------
I saw 2 way to fix this issue partially:
1) the first is parse hibernate.cfg.xml & hibernate.properties files to find
"hibernate.connection.driver_class" property value and then inspect Console
Configuration classpath - trying to load the specified class (of course this is just
partial fix);
2) other way -> try to build Console Configuration during validation process of Edit
Console Configuration -> catch all exceptions and show most relevant suggestions howto
fix it (could be rather slow process - at least during first execution);
both ways has the drawbacks - we should discuss what is better.
Max, Jiri, what is your opinion?
Hibernate console performs check for defined JDBC library
---------------------------------------------------------
Key: JBIDE-6103
URL:
https://jira.jboss.org/browse/JBIDE-6103
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.GA
Reporter: Jiri Peterka
Assignee: Vitali Yemialyanchyk
Fix For: 3.2.next
Hibernate console should perform check for available JDBC Library, not throw an exception
when user clicks on hibernate console configuration. For example when there is
org.hsqldb.jdbcDriver defined in hibernate.cfg.xml which is set in hibernate console, it
should report missing library in classpath tab which would be more comfortable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira