[jira] [Updated] (ISIS-1755) JEE Support - let CDI ignore certain beans
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1755: - Issue Type: Improvement (was: Sub-task) Parent: (was: ISIS-1767) > JEE Support - let CDI ignore certain beans > -- > > Key: ISIS-1755 > URL: https://issues.apache.org/jira/browse/ISIS-1755 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M1 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > During JEE-Application bootstrapping the JEE container identifies a > list of Isis classes it feels responsible for, but does not know how to > instantiate; so errors are thrown. For me it was sufficient to provide a > single stateless JEE bean that states, that it produces all these > classes. As long as you deploy your Isis application including this > dummy-bean, CDI does not complain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1755) JEE Support - let CDI ignore certain beans
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1755: - Summary: JEE Support - let CDI ignore certain beans (was: JEE Support - dummy bean as workaround for CDI) > JEE Support - let CDI ignore certain beans > -- > > Key: ISIS-1755 > URL: https://issues.apache.org/jira/browse/ISIS-1755 > Project: Isis > Issue Type: Sub-task >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M1 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > During JEE-Application bootstrapping the JEE container identifies a > list of Isis classes it feels responsible for, but does not know how to > instantiate; so errors are thrown. For me it was sufficient to provide a > single stateless JEE bean that states, that it produces all these > classes. As long as you deploy your Isis application including this > dummy-bean, CDI does not complain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)