[
https://issues.apache.org/activemq/browse/CAMEL-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard resolved CAMEL-2273.
--------------------------------------
Resolution: Fixed
modifications done on camel-bam, camel-jpa and camel-example-etl
> Use unqualified name as recommended by JPA specification 1.0
> ------------------------------------------------------------
>
> Key: CAMEL-2273
> URL: https://issues.apache.org/activemq/browse/CAMEL-2273
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-bam, camel-jpa, examples
> Affects Versions: 2.2.0
> Reporter: Charles Moulliard
> Assignee: Charles Moulliard
>
> The following components :
> - camel-bam,
> - camel-jpa,
> - camel-example-etl,
> - ...
> have been designed with JPA specification 1.0 but our implementation uses
> Hibernate JPA. Unfortunately, Hibernate has added some extensions.
> A good example is the fully qualified name which is used by camel jpa
> consumer/producer or in our select statement (ex : select c from
> Customer.getClass.getName).
> The JPA specification does not support this
> ******
> 4.3.1 Naming
>
> Entities are designated in query strings by their entity names. The entity
> name is defined by the name
> element of the Entity annotation (or the entity-name XML descriptor element),
> and defaults to
> the unqualified name of the entity class. Entity names are scoped within the
> persistence unit and must be
> unique within the persistence unit.
> *****
> and in consequence, switching from Hibernate to EclipseLink JPA, OpenJPA, ...
> is not possible today.
> Suggestion : uses the unqualified class name or name of the @entity provided
> in the select statement
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
