[jira] [Comment Edited] (DELTASPIKE-1115) Entity meta data discovery works not the same as in JPA

["Alexandr Smirnov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DELTASPIKE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297016#comment-15297016 ] 

Alexandr Smirnov edited comment on DELTASPIKE-1115 at 5/23/16 8:24 PM:
-----------------------------------------------------------------------

That is. There was an idea to switch from our legacy code to the new, jpa based, without changing the qualified entity names. 
In this way that would be possible to make a migration step by step. Jpa works without any problem, because class path loading is limited to one jar with xml descriptor.
But deltaspike jpa tried to load any Entity class.
There is a solution in our case, we have to rename every entity class,

But does it has any sense in general case? 
There should be persistence descriptor in any case. Why try to have wider search scope for deltaspike.


was (Author: temaleva):
That is. There was an idea to switch from our legacy code the new, jpa based, without changing the qualified entity names. 
In this way that would be possible to make a migration step by step. Jpa works without any problem, because class path loading is limited to one jar with xml descriptor.
But deltaspike jpa tried to load any Entity class.
There is a solution in our case, we have to rename every entity class,

But does it has any sense in general case? 
There should be persistence descriptor in any case. Why try to have wider search scope for deltaspike.

> Entity meta data discovery works not the same as in JPA
> -------------------------------------------------------
>
>                 Key: DELTASPIKE-1115
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1115
>             Project: DeltaSpike
>          Issue Type: Improvement
>          Components: Data-Module, JPA-Module
>    Affects Versions: 1.6.0
>            Reporter: Alexandr Smirnov
>            Priority: Minor
>
> In JPA, Entity metadata discovery mechanism search and loads Entity only from one jar, where persistence.xml is found.
> On the other side, deltaspike jpa/data module search the whole classpath.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)