Re: [Xdoclet-user] [Hibernate] Need help mapping polymorphic component

[Frank A. <fr...@bu...>]

Hi,

I have just been through the same process, and the only way around it I =20=

managed to get working is to treat the component as a separate table, =20=

rather than part of the main table.  That way, normal polymorphic =20
configuration is applicable.

All other mechanisms I tried ended up with the base class being the =20
returned type, regardless of the type actually placed in the database.

Regards
Frank

On 31/05/2005, at 4:16 AM, Mark Lundquist wrote:

> Hi,
>
> I need to map a class with a <component> (i.e., a value type) that is =20=

> polymorphic.  It seems like a basic thing, but I don't even know how =20=

> to represent this in Hibernate.  I've got a request in on the =20
> Hibernate Forum =20
> (http://forum.hibernate.org/viewtopic.php?=20
> t=3D943021&highlight=3Dpolymorphic), no answers yet...
>
> But I realized that even if I did, I wouldn't necessarily know how to =20=

> write the Xdoclet tags to generate the mapping.
>
> So then I thought, maybe somebody here can help me figure this out all =
=20
> in one go! :-)
>
> I'm using Hibernate 3, Xdoclet 1.2.3, more than willing to give =20
> Xdoclet 2 a whirl if necessary...
>
> Thanks,
> =97ml=97
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit =20
> http://developer.yahoo.net/?=20
> fr_______________________________________________
> xdoclet-user mailing list
> xdo...@li...
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>
Regards
Frank Adcock
fr...@bu...

This email and any files transmitted with it are confidential and =20
intended solely for the use of the individual or entity to whom they =20
are addressed.  If you have received this email in error please notify =20=

the system manager.  Please note that any views or opinions presented =20=

in this email are solely those of the author and do not necessarily =20
represent those of Bush Life Pty Limited.  Finally, the recipient =20
should check this email and any attachments for the presence of =20
viruses.  Bush Life  accepts no liability for any damage caused by any =20=

virus transmitted by this email.