You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2017/05/09 11:53:04 UTC

[jira] [Assigned] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

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

John D. Ament reassigned DELTASPIKE-940:
----------------------------------------

    Assignee: John D. Ament  (was: Thomas Hug)

> @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers
> ---------------------------------------------------------------------------------------------
>
>                 Key: DELTASPIKE-940
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
>             Project: DeltaSpike
>          Issue Type: Improvement
>          Components: Data-Module, JPA-Module
>            Reporter: Xavier Dury
>            Assignee: John D. Ament
>            Priority: Minor
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to specify which one(s) should be used. Currently, {{@Transactional}} and {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}} ({{@EntityManagerConfig(entityManagerResolver = MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks better and should be applied to {{@EntityManagerConfig}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)