Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [Texo] [bug] Texo 0.1.0 does not respect @Temporal annotation model, sticks with DATE
[Texo] [bug] Texo 0.1.0 does not respect @Temporal annotation model, sticks with DATE [message #663749] Wed, 06 April 2011 11:46 Go to next message
Hendy Irawan is currently offline Hendy IrawanFriend
Messages: 58
Registered: July 2009
Location: Bandung, Indonesia
Member

Tested with Texo 0.1.0, both with Standard ORM and EclipseLink ORM
generation.

In the annotationsmodel, EClass is annotated with @MappedSuperclass and the
attribute has @Basic and @Temporal set to TIMESTAMP. However the generated
orm.xml :

<orm:mapped-superclass class="com.abispulsa.model._1.Timestampable">
<orm:attributes>
<orm:basic name="created" optional="true">
<orm:temporal>DATE</orm:temporal>
</orm:basic>
<orm:basic name="lastModified" optional="true">
<orm:temporal>DATE</orm:temporal>
</orm:basic>
</orm:attributes>
</orm:mapped-superclass>

They should be TIMESTAMP.

In addition, the annotationsmodel editor in the @Temporal property, doesn't
list the available choices (DATE, TIME, TIMESTAMP), unlike the other
properties like Access, which lists FIELD and PROPERTY choices.

--
Eclipse Driven Rich Application Development -
http://eclipsedriven.blogspot.com/
Re: [Texo] [bug] Texo 0.1.0 does not respect @Temporal annotation model, sticks with DATE [message #664098 is a reply to message #663749] Thu, 07 April 2011 13:29 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Hendy,
I published a new build which hopefully solves this.

gr. Martin

On 04/06/2011 01:46 PM, Hendy Irawan wrote:
> Tested with Texo 0.1.0, both with Standard ORM and EclipseLink ORM
> generation.
>
> In the annotationsmodel, EClass is annotated with @MappedSuperclass and the
> attribute has @Basic and @Temporal set to TIMESTAMP. However the generated
> orm.xml :
>
> <orm:mapped-superclass class="com.abispulsa.model._1.Timestampable">
> <orm:attributes>
> <orm:basic name="created" optional="true">
> <orm:temporal>DATE</orm:temporal>
> </orm:basic>
> <orm:basic name="lastModified" optional="true">
> <orm:temporal>DATE</orm:temporal>
> </orm:basic>
> </orm:attributes>
> </orm:mapped-superclass>
>
> They should be TIMESTAMP.
>
> In addition, the annotationsmodel editor in the @Temporal property, doesn't
> list the available choices (DATE, TIME, TIMESTAMP), unlike the other
> properties like Access, which lists FIELD and PROPERTY choices.
>


--

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
Re: [Texo] [bug] Texo 0.1.0 does not respect @Temporal annotation model, sticks with DATE [message #665034 is a reply to message #664098] Wed, 13 April 2011 01:07 Go to previous message
Hendy Irawan is currently offline Hendy IrawanFriend
Messages: 58
Registered: July 2009
Location: Bandung, Indonesia
Member

Thank you Martin!

Amazing.. @Temporal now works perfectly. Thanks!

Martin Taal wrote:

> Hi Hendy,
> I published a new build which hopefully solves this.
>
> gr. Martin
>
> On 04/06/2011 01:46 PM, Hendy Irawan wrote:
>> Tested with Texo 0.1.0, both with Standard ORM and EclipseLink ORM
>> generation.
>>
>> In the annotationsmodel, EClass is annotated with @MappedSuperclass and
>> the attribute has @Basic and @Temporal set to TIMESTAMP. However the
>> generated orm.xml :
>>
>> <orm:mapped-superclass class="com.abispulsa.model._1.Timestampable">
>> <orm:attributes>
>> <orm:basic name="created" optional="true">
>> <orm:temporal>DATE</orm:temporal>
>> </orm:basic>
>> <orm:basic name="lastModified" optional="true">
>> <orm:temporal>DATE</orm:temporal>
>> </orm:basic>
>> </orm:attributes>
>> </orm:mapped-superclass>
>>
>> They should be TIMESTAMP.
>>
>> In addition, the annotationsmodel editor in the @Temporal property,
>> doesn't list the available choices (DATE, TIME, TIMESTAMP), unlike the
>> other properties like Access, which lists FIELD and PROPERTY choices.
>>
>
>

--
Eclipse Driven Rich Application Development -
http://eclipsedriven.blogspot.com/
Previous Topic:[EMF compare]
Next Topic:[EMF Compare] don't ignore children of unmatched elements
Goto Forum:
  


Current Time: Thu Apr 25 03:36:23 GMT 2024

Powered by FUDForum. Page generated in 0.03608 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top