You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@batchee.apache.org by Karl Kildén <ka...@gmail.com> on 2015/12/09 21:48:35 UTC
Question about entities in BatchEE
Hello,
JobExecutionEntity is afaik not a regal entity because it maps TemporalType
to a java.sql.* (Timestamp). I think java.sql.* was legal at one point in
JPA but not anymore.
The javadoc for Java EE 6 and Java EE 7 says this about TemporalType:
"Type used to indicate a specific mapping of java.util.Date or
java.util.Calendar."
I tried a fancy scanning option from openejb that would hand the found
entities to jpa and suddenly eclipselink blew up because of that entity.
Cheers / Karl
Re: Question about entities in BatchEE
Posted by Romain Manni-Bucau <rm...@gmail.com>.
You can quote what i mentionned in jira.
Anyway would be a too impacting regression to be acceptable at EE level.
Le 10 déc. 2015 21:55, "Karl Kildén" <ka...@gmail.com> a écrit :
> Hrmm Ok, I guess I did a to sloppy check myself. I just went to the
> javadoc. I checked the sourcecode in EclipseLink:
>
> https://gist.github.com/anonymous/e497e1d72ae6754b0e16
>
> My exception:
>
> https://gist.github.com/anonymous/8b7e4752500c44fab63e
>
>
> So Eclipselink bug then. I will open something in their tracker after I
> find the quote from the spec
>
> Thanks again
>
> On 10 December 2015 at 21:35, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> just checked and it is legal even in jpa 2.1. can be a bug in eclipse
>> link or a setup issue.
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> <http://www.tomitribe.com>
>>
>> 2015-12-10 21:32 GMT+01:00 Karl Kildén <ka...@gmail.com>:
>>
>>> Thanks guys,
>>>
>>> the ticket: https://issues.apache.org/jira/browse/BATCHEE-87
>>>
>>> Seems like a very odd spec change.
>>>
>>> On 10 December 2015 at 00:01, Romain Manni-Bucau <rm...@gmail.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Also tempted to check jpa dpec and open an issue since it is a big
>>>> regression forbidden by EE spec.
>>>> Le 9 déc. 2015 23:27, "Mark Struberg" <st...@yahoo.de> a écrit :
>>>>
>>>>> Indeed we should change this to java.util.Date.
>>>>>
>>>>> Imo the format in the DB should not change. Can you plz create a jira
>>>>> issue for it?
>>>>>
>>>>> txs and LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>> > Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
>>>>> >
>>>>> > Hello,
>>>>> >
>>>>> > JobExecutionEntity is afaik not a regal entity because it maps
>>>>> TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at
>>>>> one point in JPA but not anymore.
>>>>> >
>>>>> > The javadoc for Java EE 6 and Java EE 7 says this about
>>>>> TemporalType: "Type used to indicate a specific mapping of java.util.Date
>>>>> or java.util.Calendar."
>>>>> >
>>>>> > I tried a fancy scanning option from openejb that would hand the
>>>>> found entities to jpa and suddenly eclipselink blew up because of that
>>>>> entity.
>>>>> >
>>>>> > Cheers / Karl
>>>>>
>>>>>
>>>
>>
>
Re: Question about entities in BatchEE
Posted by Karl Kildén <ka...@gmail.com>.
Hrmm Ok, I guess I did a to sloppy check myself. I just went to the
javadoc. I checked the sourcecode in EclipseLink:
https://gist.github.com/anonymous/e497e1d72ae6754b0e16
My exception:
https://gist.github.com/anonymous/8b7e4752500c44fab63e
So Eclipselink bug then. I will open something in their tracker after I
find the quote from the spec
Thanks again
On 10 December 2015 at 21:35, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> just checked and it is legal even in jpa 2.1. can be a bug in eclipse link
> or a setup issue.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-12-10 21:32 GMT+01:00 Karl Kildén <ka...@gmail.com>:
>
>> Thanks guys,
>>
>> the ticket: https://issues.apache.org/jira/browse/BATCHEE-87
>>
>> Seems like a very odd spec change.
>>
>> On 10 December 2015 at 00:01, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> Also tempted to check jpa dpec and open an issue since it is a big
>>> regression forbidden by EE spec.
>>> Le 9 déc. 2015 23:27, "Mark Struberg" <st...@yahoo.de> a écrit :
>>>
>>>> Indeed we should change this to java.util.Date.
>>>>
>>>> Imo the format in the DB should not change. Can you plz create a jira
>>>> issue for it?
>>>>
>>>> txs and LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> > Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
>>>> >
>>>> > Hello,
>>>> >
>>>> > JobExecutionEntity is afaik not a regal entity because it maps
>>>> TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at
>>>> one point in JPA but not anymore.
>>>> >
>>>> > The javadoc for Java EE 6 and Java EE 7 says this about
>>>> TemporalType: "Type used to indicate a specific mapping of java.util.Date
>>>> or java.util.Calendar."
>>>> >
>>>> > I tried a fancy scanning option from openejb that would hand the
>>>> found entities to jpa and suddenly eclipselink blew up because of that
>>>> entity.
>>>> >
>>>> > Cheers / Karl
>>>>
>>>>
>>
>
Re: Question about entities in BatchEE
Posted by Romain Manni-Bucau <rm...@gmail.com>.
just checked and it is legal even in jpa 2.1. can be a bug in eclipse link
or a setup issue.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-12-10 21:32 GMT+01:00 Karl Kildén <ka...@gmail.com>:
> Thanks guys,
>
> the ticket: https://issues.apache.org/jira/browse/BATCHEE-87
>
> Seems like a very odd spec change.
>
> On 10 December 2015 at 00:01, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> +1
>>
>> Also tempted to check jpa dpec and open an issue since it is a big
>> regression forbidden by EE spec.
>> Le 9 déc. 2015 23:27, "Mark Struberg" <st...@yahoo.de> a écrit :
>>
>>> Indeed we should change this to java.util.Date.
>>>
>>> Imo the format in the DB should not change. Can you plz create a jira
>>> issue for it?
>>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>
>>> > Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
>>> >
>>> > Hello,
>>> >
>>> > JobExecutionEntity is afaik not a regal entity because it maps
>>> TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at
>>> one point in JPA but not anymore.
>>> >
>>> > The javadoc for Java EE 6 and Java EE 7 says this about TemporalType:
>>> "Type used to indicate a specific mapping of java.util.Date or
>>> java.util.Calendar."
>>> >
>>> > I tried a fancy scanning option from openejb that would hand the found
>>> entities to jpa and suddenly eclipselink blew up because of that entity.
>>> >
>>> > Cheers / Karl
>>>
>>>
>
Re: Question about entities in BatchEE
Posted by Karl Kildén <ka...@gmail.com>.
Thanks guys,
the ticket: https://issues.apache.org/jira/browse/BATCHEE-87
Seems like a very odd spec change.
On 10 December 2015 at 00:01, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> +1
>
> Also tempted to check jpa dpec and open an issue since it is a big
> regression forbidden by EE spec.
> Le 9 déc. 2015 23:27, "Mark Struberg" <st...@yahoo.de> a écrit :
>
>> Indeed we should change this to java.util.Date.
>>
>> Imo the format in the DB should not change. Can you plz create a jira
>> issue for it?
>>
>> txs and LieGrue,
>> strub
>>
>>
>>
>> > Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
>> >
>> > Hello,
>> >
>> > JobExecutionEntity is afaik not a regal entity because it maps
>> TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at
>> one point in JPA but not anymore.
>> >
>> > The javadoc for Java EE 6 and Java EE 7 says this about TemporalType:
>> "Type used to indicate a specific mapping of java.util.Date or
>> java.util.Calendar."
>> >
>> > I tried a fancy scanning option from openejb that would hand the found
>> entities to jpa and suddenly eclipselink blew up because of that entity.
>> >
>> > Cheers / Karl
>>
>>
Re: Question about entities in BatchEE
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1
Also tempted to check jpa dpec and open an issue since it is a big
regression forbidden by EE spec.
Le 9 déc. 2015 23:27, "Mark Struberg" <st...@yahoo.de> a écrit :
> Indeed we should change this to java.util.Date.
>
> Imo the format in the DB should not change. Can you plz create a jira
> issue for it?
>
> txs and LieGrue,
> strub
>
>
>
> > Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
> >
> > Hello,
> >
> > JobExecutionEntity is afaik not a regal entity because it maps
> TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at
> one point in JPA but not anymore.
> >
> > The javadoc for Java EE 6 and Java EE 7 says this about TemporalType:
> "Type used to indicate a specific mapping of java.util.Date or
> java.util.Calendar."
> >
> > I tried a fancy scanning option from openejb that would hand the found
> entities to jpa and suddenly eclipselink blew up because of that entity.
> >
> > Cheers / Karl
>
>
Re: Question about entities in BatchEE
Posted by Mark Struberg <st...@yahoo.de>.
Indeed we should change this to java.util.Date.
Imo the format in the DB should not change. Can you plz create a jira issue for it?
txs and LieGrue,
strub
> Am 09.12.2015 um 21:48 schrieb Karl Kildén <ka...@gmail.com>:
>
> Hello,
>
> JobExecutionEntity is afaik not a regal entity because it maps TemporalType to a java.sql.* (Timestamp). I think java.sql.* was legal at one point in JPA but not anymore.
>
> The javadoc for Java EE 6 and Java EE 7 says this about TemporalType: "Type used to indicate a specific mapping of java.util.Date or java.util.Calendar."
>
> I tried a fancy scanning option from openejb that would hand the found entities to jpa and suddenly eclipselink blew up because of that entity.
>
> Cheers / Karl