[jbosstools-issues] [JBoss JIRA] (JBIDE-26698) Hibernate 3.5 - Can’t open connection

[Josef Kopriva (Jira)]

Josef Kopriva created JBIDE-26698:
-------------------------------------

             Summary: Hibernate 3.5 - Can’t open connection
                 Key: JBIDE-26698
                 URL: https://issues.jboss.org/browse/JBIDE-26698
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: hibernate
    Affects Versions: 4.12.0.Final
            Reporter: Josef Kopriva
            Assignee: Koen Aers


From: https://developer.jboss.org/message/989820?et=watches.email.thread#989820
{code:java}
Hi, I have a problem with Hibernate Tools 5.4.4.v20190328-1505

 

I am trying to make Hibernate Console work on my new eclipse installation (Version: 2019-03 (4.11.0)).

 

Exception is: org.hibernate.exception.JDBCConnectionException: Cannot open connection
…
Caused by: java.sql.SQLException: No suitable driver found for jdbc:jtds:sqlserver://hidden-hostname:1433/hidden-db-name

 

 

Now, the driver is in the connection classpath, and I know it is OK, because if I only change the hibernate version to 4.3 or later, it works. With 4.0 or less, same exception.

 

I can’t just use it with version 4.3, because in my real configuration (many more mappings) I have all mapping files with 3.5 DTD and other characteristics not supported after 3.5 (LONG definitions, etc).

 

I have used hibernate console since long ago. I have had little struggle to make configuration work on other plugin installations, but this time I am getting out of ideas..

 

Previous working combination was not much older: eclipse Mars. 2 Release (4.5.2), same hibernate (3.5) Hibernate tools 5.0.1.Final-v20160331-1852-B88

 

Can anybody help me to find out what could be generating the problem?

 

Any information about some important changes between 5.0.1 and 5.0.4?

 

Thank you in advance

---

Juan
{code}


{code:java}
Trying to debug the code, I found that no matter which hibernate target version is selected, code always calls a SessionFactoryImpl from hibernate 4.0-Final, which could be the reason why queries start working selecting hibernate version 4.3 or higher (4.3 is the lowest selectable version higher than 4.0).

 

Could anybody who knows this project check this?

 

Thank you
{code}





--
This message was sent by Atlassian Jira
(v7.12.1#712002)