Might be possible to store objects like that, but when restoring them from
the database one must know which instance (of correct subclass type) to
create. Normally hibernate creates object instances. How is it possible to
replace that?

/Patrik


amphoras wrote:
> 
> Hi Patrik,
> 
> I thought about this again.  It seems that it should be possible to
> generate the BasicType as one Hibernate Component even if the BasicTypes
> uses inheritance.  In the template, one should be able to take the
> BasicType and recurse up the inheritance tree to output all the attributes
> into one Component mapping.  Hibernate should be able to save data and
> retrieve data into the subclass BasicType without knowing that it's even
> using inheritance.  Then one does not need Hibernate to implement
> Component inheritance, right?
> 
> Thanks,
> Polly
> 
> 
> 
> Patrik Nordwall wrote:
>> 
>> Sorry, I answered too quick without thinking of everything. The
>> persistence is problematic.
>> 
>> I don't think Hibernate have support for this.
>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-1152
>> 
>> /Patrik
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-Sculptor--BasicType-and-inheritance-tp19227979s17564p19616049.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer

Reply via email to