[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-799) Exception with Session Factory and Database nodes in hibernate console
Adrian Mitev (JIRA)
jira-events at lists.jboss.org
Mon Sep 24 07:19:51 EDT 2007
[ http://jira.jboss.com/jira/browse/JBIDE-799?page=comments#action_12378292 ]
Adrian Mitev commented on JBIDE-799:
------------------------------------
It happened to me two times in a row when creating new seam project
> Exception with Session Factory and Database nodes in hibernate console
> ----------------------------------------------------------------------
>
> Key: JBIDE-799
> URL: http://jira.jboss.com/jira/browse/JBIDE-799
> Project: JBoss Tools
> Issue Type: Bug
> Components: Hibernate
> Affects Versions: 2.0.0.Beta3
> Environment: RHDS beta 1, Windows XP, jdk 1.5_0.12
> Reporter: Adrian Mitev
> Priority: Critical
> Fix For: 2.0.0.Beta4
>
>
> Hi! I've created new seam project and rhds creates hibernate console configuration for me.
> Steps:
> New -> Project -> Seam Web Project -> In the Seam Facet i select mysql database and mysql connection profile (i leave schema name and catalog name empty) -> Finish.
> In the Hibernate console properties file i got:
> hibernate.connection.password=bts
> hibernate.connection.username=bts
> hibernate.connection.driver_class=com.mysql.jdbc.Driver
> hibernate.dialect=org.hibernate.dialect.MySQLDialect
> hibernate.connection.url=jdbc:mysql://localhost:3306/btsproject
> hibernate.connection.provider_class org.hibernate.connection.DriverManagerConnectionProvider
> hibernate.datasource=
> hibernate.transaction.manager_lookup_class=
> (I've changed the dialect to org.hibernate.dialect.MySQLDialect it was the dialect of hsql)
> In the hibernate console i've tried to refresh the session factory but i get the following exception:
> java.lang.UnsupportedOperationException
> at org.hibernate.console.FakeTransactionManagerLookup.getUserTransactionName(FakeTransactionManagerL
> ookup.java:37)
> at org.hibernate.transaction.JTATransactionFactory.configure(JTATransactionFactory.java:49)
> at org.hibernate.transaction.TransactionFactoryFactory.buildTransactionFactory(TransactionFactoryFac
> tory.java:51)
> at org.hibernate.cfg.SettingsFactory.createTransactionFactory(SettingsFactory.java:418)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:138)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
> at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:353)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:88)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:348)
> at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryA
> dapter.java:41)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.j
> ava:89)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenc
> hAdapter.java:95)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:196)
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list