| Re: Texo: how to declare one-to-many relations for different parent types? [message #872116] |
Tue, 15 May 2012 13:41 |
 Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Btw Olaf, Texo questions are officially answered on the EMFT newsgroup (not on the EMF newsgroup). I added the EMFT
newsgroup on the cc of this post. So let's continue this thread there.
gr. Martin
On 05/15/2012 03:35 PM, Martin Taal wrote:
> Hi Olaf,
> Sorry, I don't understand what you mean...
>
> the matchSet java member is generated inside Class1, Class2 and Class3, right? What goes wrong?
> Do they all use the same joincolumn name (which would be wrong)? (were the join column is created inside
> ABC/MatchSetType I guess)
> Or what is the problem?
>
> gr. Martin
>
> On 05/15/2012 03:26 PM, Olaf Burdziakowski wrote:
>> In my xsd there are few different classes that contain list with elements ABC:
>>
>> Class1 one many ABC
>> Class2 one many ABC
>> Class3 one many ABC
>>
>> Texo generate correct relations from classes one to list, example:
>>
>> @OneToMany(cascade = { CascadeType.ALL }, targetEntity = MatchSetType.class)
>> @OrderColumn(name = "ind")
>> @JoinColumns({ @JoinColumn() })
>> private List<MatchSetType> matchSet = new ArrayList<MatchSetType>();
>>
>> There is needed more information in @JoinColumn(...) to which classX the record belongs.
>>
>> How to annotate this?
>>
>>
>>
>
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.02383 seconds
] 
Search
Help
Register
Login
Home
