[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262496#comment-16262496 ]
ASF subversion and git services commented on ISIS-1755: ------------------------------------------------------- Commit f42ac8b9889ab72599ed8bfe81110d48e1f81c2b in isis's branch refs/heads/dev/2.0.0/ISIS-1767-jee-7 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=f42ac8b ] ISIS-1755 veto ExceptionRecognizer on CDI scan > JEE Support - dummy bean as workaround for CDI > ---------------------------------------------- > > 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 > Fix For: 2.0.0 > > > 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 (v6.4.14#64029)