[
https://issues.jboss.org/browse/FORGE-372?page=com.atlassian.jira.plugin....
]
Daniel Sachse edited comment on FORGE-372 at 12/10/11 11:45 AM:
----------------------------------------------------------------
Hi,
I think the second case with the second propositions sounds most reasonable to me. I would
go with this solution.
Is everybody in with me so I can go and realize it?
Cheers,
Daniel
was (Author: sachsedaniel):
Hi,
I think the second case with the second propositions sounds most reasonable to me. I would
go with this solution.
Is everybody in with me so I can go and realize it?
cheers,
Daniel
Qualifier on Forge EntityManager
--------------------------------
Key: FORGE-372
URL:
https://issues.jboss.org/browse/FORGE-372
Project: Forge
Issue Type: Enhancement
Components: Scaffold
Affects Versions: 1.0.0.Beta3
Reporter: Paul Dijou
Assignee: Daniel Sachse
The EntityManager (same for the EntityManagerFactory) generated by Forge in
org.metawidget.forge.persistence.DatasourceProducer has no Qualifier. It becomes a problem
when I need to create my own EntityManager because they both have the @Default qualifier
and CDI throws an exception. The only solution is to add a qualifier to my EntityManager
but it bother me since I want it to be the default EntityManager.
To reproduce the problem, just install the seam-persistence plugin, ask
"seam-persistence install-managed-persistence-context" and it will generate
another EntityManagerFactory with no qualifier and here is the CDI exception.
Would it be possible to add a qualifier like "@ForgeEntityManager" and
"@ForgeEntityManagerFactory" on the DatasourceProducer class ? (and, of course,
on the PersistenceUtil class too). This way, if a user add it's own EntityManager, it
well be the @Default.
Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira