[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5706) Move to Hibernate 3.3.x [was: Spaces in project path causes JTA exception]
Vitali Yemialyanchyk (JIRA)
jira-events at lists.jboss.org
Mon Feb 8 13:25:19 EST 2010
[ https://jira.jboss.org/jira/browse/JBIDE-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12511063#action_12511063 ]
Vitali Yemialyanchyk commented on JBIDE-5706:
---------------------------------------------
As I wrote in email: "I saw some problems with several OpenMappingDiagramTest (in difference from old version) - but this could be just my test env. problem; I saw these message in console log: (javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial ...) - is necessary to check why this happened;"
Problem with junits was a problem with file transfer operation stability - I improve it - now it is more safe and stable.
> 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: Max Rydahl Andersen
> 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
More information about the jbosstools-issues
mailing list