[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4531) ClassNotFoundException "org.hibernate.eclipse.launch.SeamUtil" when generating entities

Julien Kronegg (JIRA) jira-events at lists.jboss.org
Fri Jun 26 03:20:56 EDT 2009


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

Julien Kronegg updated JBIDE-4531:
----------------------------------

    Attachment: ClassNotFoundExceptionSeamUtil.png


> ClassNotFoundException "org.hibernate.eclipse.launch.SeamUtil" when generating entities
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4531
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4531
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.1.0.M2
>         Environment: JBossTools-ALL-win32-3.1.0.M2-N200906241801-H293.zip; Eclipse 3.5; Seam 2.1.2.GA
>            Reporter: Julien Kronegg
>            Priority: Critical
>         Attachments: ClassNotFoundExceptionSeamUtil.png
>
>
> When using Jboss Tools's "Generate Entities", a ClassCastException occurs and the entities cannot be generated when clicking on the "Finish" button (see screenshot).
> The exception message is:  "org.hibernate.tool.hbm2x.ExporterException: Exception when instantiating tool hibernatetool.util.toolclass with org.hibernate.eclipse.launch.SeamUtil".
> The root cause seems that the org.hibernate.eclipse.launch.SeamUtil class could not be found (ClassNotFoundException).
> In JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18.zip, there was a SeamUtil class in "eclipse\plugins\org.hibernate.eclipse_3.2.4.GA-R200905070146-H18\org.hibernate.eclipse.jar\org\hibernate\eclipse\launch\"
> In JBossTools-ALL-win32-3.1.0.M2-N200906241801-H293.zip, this is not the case anymore: the "launch" package is no more in "eclipse\plugins\org.hibernate.eclipse_3.3.0.M2-N200906241801-H293\org.hibernate.eclipse.jar\org\hibernate\eclipse\"
> Since there is a workaround, I set the severity to "Critical" rather than "Blocker".

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