[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374165#comment-16374165 ] ASF subversion and git services commented on ISIS-1755: --- Commit 7e409ca00e07c632f645035bc1e160d2fb79cd07 in isis's branch refs/heads/master from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=7e409ca ] ISIS-1871 ISIS-1755 let CDI ignore beans as specified > JEE Support - dummy bean as workaround for CDI > -- > > 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-M2 > > > 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] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364309#comment-16364309 ] ASF subversion and git services commented on ISIS-1755: --- Commit 14f99d6d5fe121ca4c343b9011dbe2ddde237513 in isis's branch refs/heads/ISIS-1779-jax-rs-2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=14f99d6 ] 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: Sub-task >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > 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] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317893#comment-16317893 ] ASF subversion and git services commented on ISIS-1755: --- Commit 14f99d6d5fe121ca4c343b9011dbe2ddde237513 in isis's branch refs/heads/dev/2.0.0-M2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=14f99d6 ] 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313542#comment-16313542 ] ASF subversion and git services commented on ISIS-1755: --- Commit 237ef69db8dad0f4dbb53afbb6aac94138ab396f in isis's branch refs/heads/dev/2.0.0-M2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=237ef69 ] 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313531#comment-16313531 ] ASF subversion and git services commented on ISIS-1755: --- Commit 237ef69db8dad0f4dbb53afbb6aac94138ab396f in isis's branch refs/heads/ISIS-1779-jax-rs-2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=237ef69 ] 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312954#comment-16312954 ] ASF subversion and git services commented on ISIS-1755: --- Commit 18e2b241db2c4255e6b82c7bc62b4ca97efb8776 in isis's branch refs/heads/dev/2.0.0-M2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=18e2b24 ] ISIS-1755 TomEE requires Service Providers to be public classes > 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312958#comment-16312958 ] ASF subversion and git services commented on ISIS-1755: --- Commit 6316c7cd99a768699bac6a91c80b68c7d37346ef in isis's branch refs/heads/dev/2.0.0-M2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=6316c7c ] 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312921#comment-16312921 ] ASF subversion and git services commented on ISIS-1755: --- Commit 6316c7cd99a768699bac6a91c80b68c7d37346ef in isis's branch refs/heads/ISIS-1779-jax-rs-2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=6316c7c ] 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312917#comment-16312917 ] ASF subversion and git services commented on ISIS-1755: --- Commit 18e2b241db2c4255e6b82c7bc62b4ca97efb8776 in isis's branch refs/heads/ISIS-1779-jax-rs-2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=18e2b24 ] ISIS-1755 TomEE requires Service Providers to be public classes > 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-M2 > > > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312138#comment-16312138 ] ASF subversion and git services commented on ISIS-1755: --- Commit f42ac8b9889ab72599ed8bfe81110d48e1f81c2b in isis's branch refs/heads/dev/2.0.0/ISIS-1779-jax-rs-2 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246155#comment-16246155 ] ASF subversion and git services commented on ISIS-1755: --- Commit 8b15e61a424930b40b96d393de4ae3d043d793c1 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=8b15e61 ] ISIS-1755 JEE 7+ allow coexistence of CDI and Isis' ServiceInjector > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246161#comment-16246161 ] ASF subversion and git services commented on ISIS-1755: --- Commit fee094352e2f6e35a7f3f6f6f5838a3b839222ff 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=fee0943 ] ISIS-1755 TomEE requires Service Providers to be public classes > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226428#comment-16226428 ] ASF subversion and git services commented on ISIS-1755: --- Commit 1ea665d47059c46fd4d1b8a34047240c12de4ba8 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=1ea665d ] ISIS-1755 TomEE requires Service Providers to be public classes > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223894#comment-16223894 ] Andi Huber commented on ISIS-1755: -- No dummy needed, we use CDI's extension mechanism to intercept bean scanning. see: https://docs.jboss.org/weld/reference/latest/en-US/html/extend.html > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223891#comment-16223891 ] ASF subversion and git services commented on ISIS-1755: --- Commit b0c0048e8b81a1650f964e7b20004019beefb95b 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=b0c0048 ] ISIS-1755 JEE 7+ allow coexistence of CDI and Isis' ServiceInjector > 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)
[jira] [Commented] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[
https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220178#comment-16220178
]
Andi Huber commented on ISIS-1755:
--
The dummy Enterprise Java Bean (EJB) requires annotations
* javax.ejb.Stateless
* javax.enterprise.inject.Produces
from
{code:xml}
javax
javaee-api
{code}
If we integrate this EJB into Isis we have an additional dependency. This seems
fine to me, but needs to be discussed.
> 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)
