Eclipse Community Forums: EMF » Effect of Ecore properties on generated hiberante mapping

Help

Home

Home » Modeling » EMF » Effect of Ecore properties on generated hiberante mapping

Show: Today's Messages :: Show Polls :: Message Navigator

Effect of Ecore properties on generated hiberante mapping [message #427678]

Wed, 25 February 2009 22:21

Rachna Bakhru

Messages: 45
Registered: July 2009

Member

This is a multi-part message in MIME format.

------=_NextPart_000_0101_01C99754.60022490
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I was trying to understand its effect on=20

1) unique identifier fields.

=20

When I create an id field using the ecore property iD=3Dtrue. (Case1)

<eClassifiers xsi:type=3D"ecore:EClass" name=3D"Book">
<eAnnotations source=3D"teneo.jpa">
<details key=3D"appinfo" =
value=3D" @Inheritance(strategy=3DJOINED)
@Table(name =3D"myb=
ooktable")"/>
</eAnnotations>
<eStructuralFeatures xsi:type=3D"ecore:EAttribute" name=3D"id" =
eType=3D"ecore:EDataType =
http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject"
iD=3D"true"/>
<eStructuralFeatures xsi:type=3D"ecore:EAttribute" name=3D"title" =
lowerBound=3D"1" eType=3D"ecore:EDataType =
http://www.eclipse.org/emf/2002/Ecore#//EString">
<eAnnotations source=3D"teneo.jpa">
<details key=3D"appinfo" =
value=3D"@Column(name=3D"book_title")"/>
</eAnnotations>
</eStructuralFeatures>

=20

It creates a mapping like this:

<class name=3D"com.library.impl.BookImpl" entity-name=3D"Book" =
abstract=3D"false" lazy=3D"false" table=3D"`mybooktable`">
<meta attribute=3D"eclassName">Book</meta>
<meta attribute=3D"epackage">library.ecore</meta>
<id name=3D"id" type=3D"java.lang.Integer">
<column not-null=3D"true" unique=3D"false" name=3D"`id`"/>
<generator class=3D"native"/>
</id>

=20

But when I create an id field with the tag @Id (Case2)

<eClassifiers xsi:type=3D"ecore:EClass" name=3D"Writer">
<eStructuralFeatures xsi:type=3D"ecore:EAttribute" name=3D"id" =
eType=3D"ecore:EDataType =
http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject">
<eAnnotations source=3D"teneo.jpa">
<details key=3D"appinfo" value=3D"@Id"/>
</eAnnotations>
</eStructuralFeatures>
<eStructuralFeatures xsi:type=3D"ecore:EAttribute" name=3D"name" =
lowerBound=3D"1" eType=3D"ecore:EDataType =
http://www.eclipse.org/emf/2002/Ecore#//EString"/>
=20

=20

It creates a mapping like this

<class name=3D"com.library.impl.WriterImpl" entity-name=3D"Writer" =
abstract=3D"false" lazy=3D"false" discriminator-value=3D"Writer" =
table=3D"`writer`">
<meta attribute=3D"eclassName">Writer</meta>
<meta attribute=3D"epackage">library.ecore</meta>
<id name=3D"id" type=3D"java.lang.Integer">
<column not-null=3D"true" unique=3D"false" name=3D"`id`"/>
</id>

=20

Why doesn't it add <generator class=3D"native"/> in Case 2.

=20

I know I can add that using =
@GeneratedVale(strategy=3DGenerationType.AUTO)

=20

2) Ordering

<eStructuralFeatures xsi:type=3D"ecore:EReference" name=3D"books" =
ordered=3D"false"
upperBound=3D"-1" eType=3D"#//Book" =
eOpposite=3D"#//Book/author">
<eAnnotations source=3D"teneo.jpa">
<details key=3D"appinfo" =
value=3D"@OneToMany(cascade=3D{MERGE,PERSIST} =
targetEntity=3D"Book" mappedBy=3D"author")"/>
</eAnnotations>
</eStructuralFeatures>

=20

When I use ordered=3D"false"

It changes the books collection from list to bag, but doesn't get rid of =
the <list-index column=3D"`writer_books_idx`"/>
<bag name=3D"books" lazy=3D"true" =
cascade=3D"merge,persist,save-update,lock">
<key update=3D"true">
<column name=3D"`myauthor_id`" not-null=3D"false" unique=3D"false"/>
</key>
<list-index column=3D"`writer_books_idx`"/>
<one-to-many entity-name=3D"Book"/>
</bag>

=20

only when I add indexed=3Dfalse does it do that.

@OneToMany(cascade=3D{MERGE,PERSIST} targetEntity=3D"Book" =
mappedBy=3D"author", indexed=3D"false")

Is it a good idea to use ecore properties?

=20

------=_NextPart_000_0101_01C99754.60022490
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">I was =
trying to=20
understand its effect on <?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" /><o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">1) unique =
identifier=20
fields.<o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">When I =
create an id=20
field using the ecore property iD=3Dtrue. (Case1)<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'"><eClassifiers=20
xsi:type=3D"ecore:EClass" name=3D"Book">     =
<eAnnotations=20
source=3D"teneo.jpa">       <details=20
key=3D"appinfo"=20
value=3D" @Inheritance(strategy=3DJOINED)&#xD;&#xA;@Ta ble(name=3D&=
amp;quot;mybooktable&quot;)"/>    =20
</eAnnotations>     <eStructuralFeatures=20
xsi:type=3D"ecore:EAttribute" name=3D"id" eType=3D"ecore:EDataType =
<A=20
href=3D"http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'">http://www.eclipse.org/emf/2002/Ecore#//EIntegerObj=
ect</A><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'">"          <STR=
ONG><SPAN=20
style=3D"FONT-FAMILY: 'Arial','sans-serif'">=20
iD=3D"true"/>     =
<eStructuralFeatures=20
xsi:type=3D"ecore:EAttribute" name=3D"title" lowerBound=3D"1" =
eType=3D"ecore:EDataType=20
<A href=3D"http://www.eclipse.org/emf/2002/Ecore#//EString">http://www.eclipse.org/emf/2002/Ecore#//EString</SP=
AN></A><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'">">      =20
<eAnnotations=20
source=3D"teneo.jpa">          =
<details=20
key=3D"appinfo"=20
value=3D"@Column(name=3D&quot;book_title&quot;) "/>  &n=
bsp;   =20
</eAnnotations>    =20
</eStructuralFeatures><o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">It creates =
a mapping=20
like this:<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><class=20
name=3D"com.library.impl.BookImpl" entity-name=3D"Book" =
abstract=3D"false"=20
lazy=3D"false" table=3D"`mybooktable`">   <meta=20
attribute=3D"eclassName">Book</meta>   <meta=20
attribute=3D"epackage">library.ecore</meta>   <i=
d=20
name=3D"id" =
type=3D"java.lang.Integer">    <column=20
not-null=3D"true" unique=3D"false"=20
name=3D"`id`"/>     <SPAN=20
style=3D"FONT-FAMILY: 'Arial','sans-serif'"><generator=20
class=3D"native"/>   </id> </=
SPAN><o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">But when I =
create an=20
id field with the tag @Id (Case2)<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'"><eClassifiers=20
xsi:type=3D"ecore:EClass" name=3D"Writer">    =20
<eStructuralFeatures xsi:type=3D"ecore:EAttribute" name=3D"id"=20
eType=3D"ecore:EDataType <A=20
href=3D"http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject">http://ww=
w.eclipse.org/emf/2002/Ecore#//EIntegerObject</A>">   &nb=
sp;  =20
<eAnnotations=20
source=3D"teneo.jpa">          =
<details=20
key=3D"appinfo" value=3D"@Id"/>      =20
</eAnnotations>    =20
</eStructuralFeatures>     =
<eStructuralFeatures=20
xsi:type=3D"ecore:EAttribute" name=3D"name" lowerBound=3D"1" =
eType=3D"ecore:EDataType <A=20
href=3D"http://www.eclipse.org/emf/2002/Ecore#//EString">http://www.eclip=
se.org/emf/2002/Ecore#//EString"/</A>>    =20
<o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">It creates =
a mapping=20
like this<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><class=20
name=3D"com.library.impl.WriterImpl" entity-name=3D"Writer" =
abstract=3D"false"=20
lazy=3D"false" discriminator-value=3D"Writer"=20
table=3D"`writer`">   <meta=20
attribute=3D"eclassName">Writer</meta>   <meta=20
attribute=3D"epackage">library.ecore</meta>   <i=
d=20
name=3D"id" =
type=3D"java.lang.Integer">    <column=20
not-null=3D"true" unique=3D"false"=20
name=3D"`id`"/>   </id> <o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Why doesn't =
it=20
add  <SPAN=20
style=3D"FONT-FAMILY: 'Arial','sans-serif'"><generator =
class=3D"native"/>=20
in Case=20
2.<o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">I know I =
can add that=20
using =
@GeneratedVale(strategy=3DGenerationType.AUTO)<o:p> </o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">2)=20
Ordering<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'"><eStructuralFeatures=20
xsi:type=3D"ecore:EReference" name=3D"books" <SPAN=20
style=3D"FONT-FAMILY: =
'Arial','sans-serif'">ordered=3D"false"   &n=
bsp;    =20
upperBound=3D"-1" eType=3D"#//Book"=20
eOpposite=3D"#//Book/author">      =20
<eAnnotations=20
source=3D"teneo.jpa">          =
<details=20
key=3D"appinfo" value=3D"@OneToMany(cascade=3D{MERGE,PERSIST}=20
targetEntity=3D&quot;Book&quot;=20
mappedBy=3D&quot;author&quot;)"/>     &=
nbsp;=20
</eAnnotations>    =20
</eStructuralFeatures><o:p></o:p>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">When I use=20
ordered=3D"false"<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">It changes =
the books=20
collection from list to bag, but doesn=92t get rid of=20
the  <list-index =
column=3D"`writer_books_idx`"/> <bag=20
name=3D"books" lazy=3D"true"=20
cascade=3D"merge,persist,save-update,lock">    <k=
ey=20
update=3D"true">     <column =
name=3D"`myauthor_id`"=20
not-null=3D"false"=20
unique=3D"false"/>    </key>   &n=
bsp;<list-index=20
column=3D"`writer_books_idx`"/>    <one-to-many=20
entity-name=3D"Book"/>   </bag> <o:p></o:p></=
P>
<FONT=20
face=3DCalibri> <o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">only when I =
add=20
indexed=3Dfalse does it do that.<o:p></o:p>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Arial','sans-serif'">@OneToMany(cascade=3D{MERGE,PERSIST}=20
targetEntity=3D"Book" mappedBy=3D"author", <SPAN=20
style=3D"FONT-FAMILY: =
'Arial','sans-serif'">indexed=3D"false")<o:p></o:p=
>
<SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Is it a =
good idea to=20
use ecore properties?<o:p></o:p>
<o:p> </o:p></DIV></BODY ></HTML>

------=_NextPart_000_0101_01C99754.60022490--

Report message to a moderator

Re: Effect of Ecore properties on generated hiberante mapping [message #427679 is a reply to message #427678]

Wed, 25 February 2009 22:36

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Hi RJ,
These are valid remarks!

1) you are correct that this difference should not be there, can you enter a bugzilla for this? If id=true then it
should not automatically add generator class="native", that can be controlled by a generator.

2) again a correct statement, the order="false" should make it a bag (that's correct) but the list-index should not be
there, can you enter a bugzilla for this to?

Overall I would use annotations more than use ecore properties to control persistence. With annotations you have much
more control and it is much more precise.

gr. Martin

RJDAG wrote:
>
>
> I was trying to understand its effect on
>
> 1) unique identifier fields.
>
>
>
> When I create an id field using the ecore property iD=true. (Case1)
>
> <eClassifiers xsi:type="ecore:EClass" name="Book">
> <eAnnotations source="teneo.jpa">
> <details key="appinfo"
> value=" @Inheritance(strategy=JOINED)
@Table(name=& amp;quot;mybooktable") "/>
> </eAnnotations>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
> eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject"
> * iD="true"/*>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="title"
> lowerBound="1" eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EString">
> <eAnnotations source="teneo.jpa">
> <details key="appinfo"
> value="@Column(name="book_title")"/>
> </eAnnotations>
> </eStructuralFeatures>
>
>
>
> It creates a mapping like this:
>
> <class name="com.library.impl.BookImpl" entity-name="Book"
> abstract="false" lazy="false" table="`mybooktable`">
> <meta attribute="eclassName">Book</meta>
> <meta attribute="epackage">library.ecore</meta>
> <id name="id" type="java.lang.Integer">
> <column not-null="true" unique="false" name="`id`"/>
> *<generator class="native"/>**
> * </id>
>
>
>
> But when I create an id field with the tag @Id (Case2)
>
> <eClassifiers xsi:type="ecore:EClass" name="Writer">
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
> eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject">
> <eAnnotations source="teneo.jpa">
> <details key="appinfo" value="@Id"/>
> </eAnnotations>
> </eStructuralFeatures>
> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
> lowerBound="1" eType="ecore:EDataType
> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>
>
>
>
> It creates a mapping like this
>
> <class name="com.library.impl.WriterImpl" entity-name="Writer"
> abstract="false" lazy="false" discriminator-value="Writer" table="`writer`">
> <meta attribute="eclassName">Writer</meta>
> <meta attribute="epackage">library.ecore</meta>
> <id name="id" type="java.lang.Integer">
> <column not-null="true" unique="false" name="`id`"/>
> </id>
>
>
>
> Why doesn't it add *<generator class="native"/> *in* Case 2.*
>
>
>
> I know I can add that using @GeneratedVale(strategy=GenerationType.AUTO)
>
>
>
> 2) Ordering
>
> <eStructuralFeatures xsi:type="ecore:EReference" name="books"
> *ordered="false"*
> upperBound="-1" eType="#//Book" eOpposite="#//Book/author">
> <eAnnotations source="teneo.jpa">
> <details key="appinfo" value="@OneToMany(cascade={MERGE,PERSIST}
> targetEntity="Book" mappedBy="author")"/>
> </eAnnotations>
> </eStructuralFeatures>
>
>
>
> When I use ordered="false"
>
> It changes the books collection from list to bag, but doesn’t get rid of
> the <list-index column="`writer_books_idx`"/>
> <bag name="books" lazy="true" cascade="merge,persist,save-update,lock">
> <key update="true">
> <column name="`myauthor_id`" not-null="false" unique="false"/>
> </key>
> <list-index column="`writer_books_idx`"/>
> <one-to-many entity-name="Book"/>
> </bag>
>
>
>
> only when I add indexed=false does it do that.
>
> @OneToMany(cascade={MERGE,PERSIST} targetEntity="Book"
> mappedBy="author", *indexed="false")*
>
> Is it a good idea to use ecore properties?
>
>
>

--

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@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org

Report message to a moderator

Re: Effect of Ecore properties on generated hiberante mapping [message #427680 is a reply to message #427679]

Thu, 26 February 2009 00:58

Rachna Bakhru

Messages: 45
Registered: July 2009

Member

Thank you for the clarifications.
I will enter the bugs as soon as I setup a bugzilla account.

"Martin Taal" <mtaal@elver.org> wrote in message
news:go4h4r$sdm$1@build.eclipse.org...
> Hi RJ,
> These are valid remarks!
>
> 1) you are correct that this difference should not be there, can you enter
> a bugzilla for this? If id=true then it should not automatically add
> generator class="native", that can be controlled by a generator.
>
> 2) again a correct statement, the order="false" should make it a bag
> (that's correct) but the list-index should not be there, can you enter a
> bugzilla for this to?
>
> Overall I would use annotations more than use ecore properties to control
> persistence. With annotations you have much more control and it is much
> more precise.
>
> gr. Martin
>
> RJDAG wrote:
>>
>>
>> I was trying to understand its effect on
>>
>> 1) unique identifier fields.
>>
>> When I create an id field using the ecore property iD=true. (Case1)
>>
>> <eClassifiers xsi:type="ecore:EClass" name="Book">
>> <eAnnotations source="teneo.jpa">
>> <details key="appinfo"
>> value=" @Inheritance(strategy=JOINED)
@Table(name=& amp;quot;mybooktable") "/>
>> </eAnnotations>
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
>> eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject"
>> * iD="true"/*>
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="title"
>> lowerBound="1" eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString">
>> <eAnnotations source="teneo.jpa">
>> <details key="appinfo"
>> value="@Column(name="book_title")"/>
>> </eAnnotations>
>> </eStructuralFeatures>
>>
>> It creates a mapping like this:
>>
>> <class name="com.library.impl.BookImpl" entity-name="Book"
>> abstract="false" lazy="false" table="`mybooktable`">
>> <meta attribute="eclassName">Book</meta>
>> <meta attribute="epackage">library.ecore</meta>
>> <id name="id" type="java.lang.Integer">
>> <column not-null="true" unique="false" name="`id`"/>
>> *<generator class="native"/>**
>> * </id>
>>
>> But when I create an id field with the tag @Id (Case2)
>>
>> <eClassifiers xsi:type="ecore:EClass" name="Writer">
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
>> eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject">
>> <eAnnotations source="teneo.jpa">
>> <details key="appinfo" value="@Id"/>
>> </eAnnotations>
>> </eStructuralFeatures>
>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
>> lowerBound="1" eType="ecore:EDataType
>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>> It creates a mapping like this
>>
>> <class name="com.library.impl.WriterImpl" entity-name="Writer"
>> abstract="false" lazy="false" discriminator-value="Writer"
>> table="`writer`">
>> <meta attribute="eclassName">Writer</meta>
>> <meta attribute="epackage">library.ecore</meta>
>> <id name="id" type="java.lang.Integer">
>> <column not-null="true" unique="false" name="`id`"/>
>> </id>
>>
>> Why doesn't it add *<generator class="native"/> *in* Case 2.*
>>
>> I know I can add that using @GeneratedVale(strategy=GenerationType.AUTO)
>>
>> 2) Ordering
>>
>> <eStructuralFeatures xsi:type="ecore:EReference" name="books"
>> *ordered="false"*
>> upperBound="-1" eType="#//Book" eOpposite="#//Book/author">
>> <eAnnotations source="teneo.jpa">
>> <details key="appinfo" value="@OneToMany(cascade={MERGE,PERSIST}
>> targetEntity="Book" mappedBy="author")"/>
>> </eAnnotations>
>> </eStructuralFeatures>
>>
>> When I use ordered="false"
>>
>> It changes the books collection from list to bag, but doesn

Report message to a moderator

Re: Effect of Ecore properties on generated hiberante mapping [message #427743 is a reply to message #427680]

Fri, 27 February 2009 23:00

Rachna Bakhru

Messages: 45
Registered: July 2009

Member

Bugs created:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=266572
https://bugs.eclipse.org/bugs/show_bug.cgi?id=266573

"RJDAG" <rjotwani@dag.com> wrote in message
news:go4pi3$9bh$1@build.eclipse.org...
> Thank you for the clarifications.
> I will enter the bugs as soon as I setup a bugzilla account.
>
> "Martin Taal" <mtaal@elver.org> wrote in message
> news:go4h4r$sdm$1@build.eclipse.org...
>> Hi RJ,
>> These are valid remarks!
>>
>> 1) you are correct that this difference should not be there, can you
>> enter a bugzilla for this? If id=true then it should not automatically
>> add generator class="native", that can be controlled by a generator.
>>
>> 2) again a correct statement, the order="false" should make it a bag
>> (that's correct) but the list-index should not be there, can you enter a
>> bugzilla for this to?
>>
>> Overall I would use annotations more than use ecore properties to control
>> persistence. With annotations you have much more control and it is much
>> more precise.
>>
>> gr. Martin
>>
>> RJDAG wrote:
>>>
>>>
>>> I was trying to understand its effect on
>>>
>>> 1) unique identifier fields.
>>>
>>> When I create an id field using the ecore property iD=true. (Case1)
>>>
>>> <eClassifiers xsi:type="ecore:EClass" name="Book">
>>> <eAnnotations source="teneo.jpa">
>>> <details key="appinfo"
>>> value=" @Inheritance(strategy=JOINED)
@Table(name=& amp;quot;mybooktable") "/>
>>> </eAnnotations>
>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
>>> eType="ecore:EDataType
>>> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject"
>>> * iD="true"/*>
>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="title"
>>> lowerBound="1" eType="ecore:EDataType
>>> http://www.eclipse.org/emf/2002/Ecore#//EString">
>>> <eAnnotations source="teneo.jpa">
>>> <details key="appinfo"
>>> value="@Column(name="book_title")"/>
>>> </eAnnotations>
>>> </eStructuralFeatures>
>>>
>>> It creates a mapping like this:
>>>
>>> <class name="com.library.impl.BookImpl" entity-name="Book"
>>> abstract="false" lazy="false" table="`mybooktable`">
>>> <meta attribute="eclassName">Book</meta>
>>> <meta attribute="epackage">library.ecore</meta>
>>> <id name="id" type="java.lang.Integer">
>>> <column not-null="true" unique="false" name="`id`"/>
>>> *<generator class="native"/>**
>>> * </id>
>>>
>>> But when I create an id field with the tag @Id (Case2)
>>>
>>> <eClassifiers xsi:type="ecore:EClass" name="Writer">
>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="id"
>>> eType="ecore:EDataType
>>> http://www.eclipse.org/emf/2002/Ecore#//EIntegerObject">
>>> <eAnnotations source="teneo.jpa">
>>> <details key="appinfo" value="@Id"/>
>>> </eAnnotations>
>>> </eStructuralFeatures>
>>> <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
>>> lowerBound="1" eType="ecore:EDataType
>>> http://www.eclipse.org/emf/2002/Ecore#//EString"/>
>>> It creates a mapping like this
>>>
>>> <class name="com.library.impl.WriterImpl" entity-name="Writer"
>>> abstract="false" lazy="false" discriminator-value="Writer"
>>> table="`writer`">
>>> <meta attribute="eclassName">Writer</meta>
>>> <meta attribute="epackage">library.ecore</meta>
>>> <id name="id" type="java.lang.Integer">
>>> <column not-null="true" unique="false" name="`id`"/>
>>> </id>
>>>
>>> Why doesn't it add *<generator class="native"/> *in* Case 2.*
>>>
>>> I know I can add that using
>>> @GeneratedVale(strategy=GenerationType.AUTO)
>>>
>>> 2) Ordering
>>>
>>> <eStructuralFeatures xsi:type="ecore:EReference" name="books"
>>> *ordered="false"*
>>> upperBound="-1" eType="#//Book" eOpposite="#//Book/author">
>>> <eAnnotations source="teneo.jpa">
>>> <details key="appinfo" value="@OneToMany(cascade={MERGE,PERSIST}
>>> targetEntity="Book" mappedBy="author")"/>
>>> </eAnnotations>
>>> </eStructuralFeatures>
>>>
>>> When I use ordered="false"
>>>
>>> It changes the books collection from list to bag, but doesn't get rid of
>>> the <list-index column="`writer_books_idx`"/>
>>> <bag name="books" lazy="true" cascade="merge,persist,save-update,lock">
>>> <key update="true">
>>> <column name="`myauthor_id`" not-null="false" unique="false"/>
>>> </key>
>>> <list-index column="`writer_books_idx`"/>
>>> <one-to-many entity-name="Book"/>
>>> </bag>
>>>
>>> only when I add indexed=false does it do that.
>>>
>>> @OneToMany(cascade={MERGE,PERSIST} targetEntity="Book"
>>> mappedBy="author", *indexed="false")*
>>>
>>> Is it a good idea to use ecore properties?
>>>
>>>
>>
>>
>> --
>>
>> 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@springsite.com - mtaal@elver.org
>> Web: www.springsite.com - www.elver.org
>
>

Report message to a moderator

Previous Topic:	Ordering collections in a one-to-many association
Next Topic:	Re: Best practice: Modifying model in ok/cancel dialog.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 04:32:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter