[
https://issues.jboss.org/browse/JBIDE-9400?page=com.atlassian.jira.plugin...
]
Alexey Kazakov resolved JBIDE-9400.
-----------------------------------
Assignee: Viacheslav Kabanovich (was: Alexey Kazakov)
Resolution: Done
I found three issues during validating the fix.
Two of them are not caused by the code added to fix the issue: JBIDE-9484 and JBIDE-9483
They are related to general mechanism of CDI extension loading .
And the 3rd one is a minor issue of loading Seam Persistence extensions. We create both
EntityManager and Session beans if
org.jboss.seam.persistence.ManagedPersistenceContextExtension service implementation is
declared in META-INF which is not 100% correct since this extension should create only a
bean for EntityManager and another extension
org.jboss.seam.persistence.hibernate.HibernateManagedSessionExtension should create a bean
for Session. But both of these extensions are declared in the same JAR, so we decided not
to separate these extensions due to performance issues.
So i'm resolving the issue.
Tooling shows warning for Seam 3 Persistence created EntityManager
injection
----------------------------------------------------------------------------
Key: JBIDE-9400
URL:
https://issues.jboss.org/browse/JBIDE-9400
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi extensions
Affects Versions: 3.3.0.M2
Reporter: Cody Lerum
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M3
Create SMPC in Seam 3 Persistence module as shown here
http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers...
@Inject
EntityManager em;
Shows "No bean is eligible for injection to the injection point [JSR-299
§5.2.1]" warning
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira