You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Xavier Dury (JIRA)" <ji...@apache.org> on 2015/06/29 16:09:04 UTC
[jira] [Created] (DELTASPIKE-940) @Transactional and
@EntityManagerConfig each use a different method to resolve EntityManagers
Xavier Dury created DELTASPIKE-940:
--------------------------------------
Summary: @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
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.4#6332)