I don't understand. Are we having different java classes for the subclasses, or do you mean that we flatten the java classes also?
If we have java subclasses I don't think the component mapping you suggest will be able to restore the correct type. If we have one java class, UserInformation, containing all properties from all subclasses, it will of course work. /Patrik amphoras wrote: > > It should be ok. The Hibernate mapping for the component has the class > name. Like this: > > <component class="com.foo.UserInformation" lazy="false" > name="userInformation"> > ... > </component> > > Please let me know if I'm missing something. > > Thanks, > Polly > > > > Patrik Nordwall wrote: >> >> 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 >> >> >> > > -- View this message in context: http://www.nabble.com/-Sculptor--BasicType-and-inheritance-tp19227979s17564p19635147.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
