You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/12/09 14:11:04 UTC

[jira] Resolved: (CAMEL-3419) timestamp property in JpaTraceEventMessage does not specify a temporal type

     [ https://issues.apache.org/jira/browse/CAMEL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3419.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6.0
         Assignee: Claus Ibsen

Thanks for reporting.

trunk: 1043957.

> timestamp property in JpaTraceEventMessage does not specify a temporal type
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-3419
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3419
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jpa
>    Affects Versions: 2.5.0
>         Environment: JPA 2.0 / EclipseLink 2.1.0
>            Reporter: Marco Zapletal
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>
> The timestamp property in the JpaTraceEventMessage does not specify a temporal type. This results in an exception using EclipseLink 2.1.0 (and maybe using other JPA frameworks, too). 
> Using the annotation  @Temporal(TemporalType.TIMESTAMP) on timestamp should solve this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.