[jbosstools-issues] [JBoss JIRA] Assigned: (JBIDE-5706) Move to Hibernate 3.3.x [was: Spaces in project path causes JTA exception]

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen reassigned JBIDE-5706:
------------------------------------------

    Assignee: Dominik Pospisil  (was: Max Rydahl Andersen)


Want to resolve this issue since all code is now in place for it (waiting for build to confirm everything is fine), but assigning to Dominik for awareness to QA because this fix means Hibernate Tools is now using Hibernate 3.3.x instead of 3.2.x. This fixes this long standing issue and generally makes us much more compatible with later EAP releases etc.

All 300+ tests in hibernate tools passes so i'm pretty confident this is all fine.
Still if you see/notice weird behavior in working with hql editor, reverse engineering, seam generate entities, incompabilities when users are using different hibernate version etc. then let us know asap by creating new issues we can react to since it might be because we missed something.

You can resolve this one when you see it - or close if you verify it ;)


> Move to Hibernate 3.3.x [was: Spaces in project path causes JTA exception]
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-5706
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5706
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.1.0.CR1
>            Reporter: Ondrej Skutka
>            Assignee: Dominik Pospisil
>            Priority: Critical
>             Fix For: 3.1.0.CR2
>
>         Attachments: Hibernate Configuration error.png, JBIDE-5706_20100202.zip
>
>
> Steps to reproduce:
> 1) Create a new Seam project with database
> 2) Go to Hibernate Configurations view
> 3) Unfold the configuration
> following exception is thrown:
> org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
> Could not create JPA based Configuration
>   <No message>
>   java.lang.reflect.InvocationTargetException
>     java.lang.reflect.InvocationTargetException: <no message>
>     java.lang.reflect.InvocationTargetException
>     javax.persistence.PersistenceException: java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes
>     java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes
>     java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes
>     Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes
> Furturemore you cannot generate seam entities, because of "Couldn't connect to Database".

-- 
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