openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Rüegg (JIRA) <>
Subject [jira] [Updated] (OPENJPA-2341) OpenJPA ignores custom field strategies globally defined in persistence.xml
Date Wed, 27 Feb 2013 16:27:12 GMT


Michael Rüegg updated OPENJPA-2341:

    Priority: Blocker  (was: Major)
> OpenJPA ignores custom field strategies globally defined in persistence.xml
> ---------------------------------------------------------------------------
>                 Key: OPENJPA-2341
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Michael Rüegg
>            Priority: Blocker
> I use a custom field strategy value handler (a class that extends org.apache.openjpa.jdbc.meta.strats.AbstractValueHandler)
for my entities that make use of joda time fields:
> @Entity
> public class MyEntity {
>   org.joda.time.LocalDateTime creationDate;
> }
> When I use the inline strategy annotation (@Strategy("")),
everything works as expected and my LocalDateTime field 'creationDate' gets mapped to an SQL
timestamp. However, if I reference my value handler globally in the persistence.xml file,
then OpenJPA is not able to find the value handler (i.e., it is never called), which results
in a blob column type for 'creationDate'. Here's the corresponding snippet from my persistence.xml:
> <property name="openjpa.jdbc.MappingDefaults" value="FieldStrategies='"/>
> Note that if I use a mapping from a standard JDK class like java.lang.String to my value
handler, then my handler is called as expected. Is this issue somehow related to #OPENJPA-758?
Note that I use Derby as my database.
> Any help would be much appreciated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message