Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: OpenSAGA 2.0.0 M1
-
Fix Version/s: OpenSAGA 2.0.0
-
Component/s: Generator
-
Labels:None
Description
When naming a domaintype "type" there is a conflict with the defintion of the Type annotation of hibernate. Since the generation is hidden from the developer most times, you must know that the name of the DomainType becomes the name of the Java class. Maybe we should add a test and a qualified error message to the self-validiation of the model. Priority is set to "trivial", because this may be a very rare case.
2011-09-23 10:40:51,260 (main) ERROR org.opensaga.runtime.model.domain.startup.EclipseCompilerBasedJavaDomainClassGenerator: org/opensaga/runtime/model/domain/types/Type.java (L:20, C:489)-(L:20, C:518): The import org.hibernate.annotations.Type conflicts with a type defined in the same file
2011-09-23 10:40:51,260 (main) ERROR org.opensaga.runtime.model.domain.startup.EclipseCompilerBasedJavaDomainClassGenerator: org/opensaga/runtime/model/domain/types/Type.java (L:109, C:2905)-(L:109, C:2908): Type mismatch: cannot convert from Type to Annotation
2011-09-23 10:40:51,260 (main) ERROR org.opensaga.runtime.model.domain.startup.EclipseCompilerBasedJavaDomainClassGenerator: org/opensaga/runtime/model/domain/types/Type.java (L:178, C:5515)-(L:178, C:5518): Type mismatch: cannot convert from Type to Annotation
I used qualified names, this should now work. Please verify!