[
https://jira.jboss.org/jira/browse/JBIDE-4531?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4531:
--------------------------------------------
1) this file should just stay there in both M2 and M3 for now.
It is there so Hibernate Tools can load the class SeamUtil when asked for it, if you put
it into the seam plugins it wont work since hibernate does not have access to their
classes.
2) The right solution for this is in trunk is to when we execute seam-gen to add the
seamgen.jar to the classpath of the console configuration used to run with it. Then it
should pick it up correctly and we would not need to have this copy/pasted class anymore.
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, Seam
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
Assignee: Aliaksey Nis
Priority: Critical
Fix For: 3.1.0.M2, 3.1.0.M3
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