[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-7985) NoSuchMethodError Trying to explore a DB from Hibernate Configurations

Dmitry Geraskov (JIRA) jira-events at lists.jboss.org
Thu Dec 23 05:27:17 EST 2010


    [ https://issues.jboss.org/browse/JBIDE-7985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572161#comment-12572161 ] 

Dmitry Geraskov edited comment on JBIDE-7985 at 12/23/10 5:27 AM:
------------------------------------------------------------------

Angus, do you have the same error when you use a hibernate configuration in your project?
Could you please provide us the library names and versions in your project build path?
And how do you configure the logger? With log4j.properties? Could you please provide the logger configuration file too?
We have some libraries inside our plugins which we are using to build the hibernate configutaion but also we load the libraries from your project class path. That is why we need to know them to reproduce the issue.

      was (Author: dgeraskov):
    Angus, do you have the same error when you use a hibernate configuration in your project?
Could you please provide use the library names and versions in your project build path?
And how do you configure the logger? With log4j.properties? Could you please provide the logger configuration file too?
  
> NoSuchMethodError Trying to explore a DB from Hibernate Configurations
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-7985
>                 URL: https://issues.jboss.org/browse/JBIDE-7985
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Angus Mezick
>            Assignee: Dmitry Geraskov
>            Priority: Critical
>         Attachments: screenshot-1.jpg
>
>
> What steps will reproduce the problem?
> 1. Create a new hibernate configuration
> 2. Use the "Hibernate Configurations" view to explore the database
> 3. Notice the error popup.
> -- Error Details --
> Date: Wed Dec 22 12:47:27 EST 2010
> Message: An internal error occurred during: "Fetching children of Database".
> Severity: Error
> Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.jee.product)
> Plugin: org.eclipse.core.jobs
> Session Data:
> eclipse.buildId=M20100909-0800
> java.version=1.6.0_22
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments:  -product org.eclipse.epp.package.jee.product
> Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
> Exception Stack Trace:
> java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> 	at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133)
> 	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26)
> 	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
> 	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
> 	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116)
> 	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:235)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list