[hibernate-issues] [Hibernate-JIRA] Commented: (ANN-526) Property xyz has an unbound type - is that so?

Emmanuel Bernard (JIRA) noreply at atlassian.com
Tue Jan 16 18:02:44 EST 2007


    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-526?page=comments#action_25805 ] 

Emmanuel Bernard commented on ANN-526:
--------------------------------------

my understanding is that 
T in AbstractGenerics  is not resolved in your system.
Because T is a subtype of AbstractGenerics<U>, U not being resolved.
Am I wrong?

> Property xyz has an unbound type - is that so?
> ----------------------------------------------
>
>          Key: ANN-526
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-526
>      Project: Hibernate Annotations
>         Type: Bug

>     Versions: 3.2.1
>     Reporter: Sebastian Kirsch
>     Priority: Minor
>  Attachments: Hibernate ANN-526.zip
>
>
> I get this "Property reference has an unbound type and no explictit target entity" exception and I think this is not exactly true. I'm not sure if this is a bug or a feature requests though.
> Have a look at the attached files and read on.
> I guess the model ist pretty easy to understand. The AbstractGeneric allows my to have concrete entities referring to specifc other subclasses - as seen in ConcreteOther and ConcreteSelf. The test case "workingClasses" shows us that Hibernate may work with this model - note that the class AbstractGeneric itslef was NOT added to the configuration.
> Now for the problem: The class OtherEntity is a completly different entity, but it refers to instances of AbstractGeneric - to any subclass of it actually, as AbstractGeneric is obviously abstract.
> If you run the test case "otherClass" the first part states that Hibernate doesn't know AbstractGeneric - which is fine, so I add that class to the configuration and try to build a session factory again. Now we receive the beforementioned exception.
> That's the situation. So is AbstractGeneric really an unbound type? I'd say it is not - T has an upper bound which should be good enough to work with - we know the table and the PK...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira




More information about the hibernate-issues mailing list