4:13 p.m.
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Ales Justin commented on WELD-832:
----------------------------------
Aslak, is this still an issue?
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:46 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on WELD-832:
------------------------------------
still seems to be a issue with 7.1.0.Final:
{code}
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateful.RemoteViewStatefulEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.singleton.RemoteViewSingletonEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateless.RemoteViewStatelessEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
{code}
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:46 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on WELD-832:
------------------------------------
oops.. that should only have been added once :)
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:46 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on WELD-832:
------------------------------------
still seems to be a issue with 7.1.0.Final:
{code}
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateful.RemoteViewStatefulEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.singleton.RemoteViewSingletonEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateless.RemoteViewStatelessEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
{code}
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:59 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Ales Justin updated WELD-832:
-----------------------------
Comment: was deleted
(was: still seems to be a issue with 7.1.0.Final:
{code}
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateful.RemoteViewStatefulEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.singleton.RemoteViewSingletonEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest):
No beans should be found: [Session bean [class
org.opentck.javaee.cdi_ejb.deployments.beans.stateless.RemoteViewStatelessEJB with
qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but
was:<1>
{code})
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:59 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Ales Justin updated WELD-832:
-----------------------------
Comment: was deleted
(was: oops.. that should only have been added once :))
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
3:59 p.m.
New subject: [JBoss JIRA] (WELD-832) Remote EJBs can be resolved by name
[
https://issues.jboss.org/browse/WELD-832?page=com.atlassian.jira.plugin.s...
]
Ales Justin reassigned WELD-832:
--------------------------------
Assignee: Stuart Douglas
Stuart, can you please have a look?
Remote EJBs can be resolved by name
-----------------------------------
Key: WELD-832
URL: https://issues.jboss.org/browse/WELD-832
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.0.Final
Reporter: Aslak Knutsen
Assignee: Stuart Douglas
You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be
registered as Beans.
Failed tests:
runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)
tests: https://github.com/opentck/javaee_cdi_ejb
--
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
4440
days inactive
4845
days old
7 comments
2 participants
participants (2)
-
Ales Justin (JIRA) -
Aslak Knutsen (JIRA)