[
https://jira.jboss.org/jira/browse/JBIDE-6140?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-6140:
---------------------------------------
Fix Version/s: 3.1.x
3.2.next
(was: 3.1.1)
Jiri, any steps to reproduce this ?
Hibernate.dialect must be set error reported although set in
hibernate.cfg.xml
------------------------------------------------------------------------------
Key: JBIDE-6140
URL:
https://jira.jboss.org/jira/browse/JBIDE-6140
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.GA
Environment: JBDS 3.0.0 GA #50, Linux 32, java.version=1.5.0_22
Reporter: Jiri Peterka
Assignee: Jiri Peterka
Fix For: 3.1.x, 3.2.next
Steps: Created Java project, hibernate console, hibernate configuration is set for hsqldb
and dialect set. There is this error log
org.hibernate.HibernateException: 'hibernate.dialect' must be set when no
Connection avalable
at org.hibernate.dialect.resolver.DialectFactory.buildDialect(DialectFactory.java:107)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:142)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2111)
at
org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:110)
at
org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at
org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107)
at
org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63)
at
org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
at
org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira