4:40 p.m.
Joseph Snyder created WELD-1133:
-----------------------------------
Summary: Session EJB deployment failure
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.8.Final, 1.1.7.Final, 1.1.6.Final, 1.1.5.Final
Environment: linux
Reporter: Joseph Snyder
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean Session
bean [class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with
qualifiers [@Any @Default]; local interfaces are [OfficeLocal] does not have bean type
interface org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal
of specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
4:42 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
To reproduce the failure run the cts...to speed it up configure the test harness to only
run the test
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
4:48 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Ales Justin commented on WELD-1133:
-----------------------------------
Is this similar to WELD-921?
(which needs API changes to be properly fixed)
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
4:56 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
It is similar but not the same case. In this case interface Bar does not extend interface
Foo (this is the same as the cts test classes and interfaces). In WELD-921 the interface
extends the super's interface.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
7:41 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Ales Justin reassigned WELD-1133:
---------------------------------
Assignee: Marko Lukša
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
4:19 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Jozef Hartinger commented on WELD-1133:
---------------------------------------
It looks like you are hitting the following bug in the testsuite:
https://issues.jboss.org/browse/CDITCK-249
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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:19 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
I am using jsr299-tck-1.0.4.SP3. Is this the correct version?
The only thing that changes when I run the tck is the version of weld. The tests pass
with Weld 1.1.4.Final but fail with 1.1.5.Final (up to 1.1.8.Final...I have not tried
1.1.9.Final).
The bug in CDITCK-249 says that it's resolved by making the interface OfficeLocal
extend BuildingLocal. But according to the EJB spec this will not get Office (implements
OfficeLocal) a local type of BuildingLocal. The session bean (Office) must explicitly
declare the interfaces that will be included in its local types.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
5:37 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Martin Kouba commented on WELD-1133:
------------------------------------
1.0.4.SP3 is the correct version as it is the last release of TCK. This test should be
definitely excluded. Most likely I forgot to update *tck-tests.xml* in 1.0 branch.
{quote}
The bug in CDITCK-249 says that it's resolved by making the interface OfficeLocal
extend BuildingLocal. But according to the EJB spec this will not get Office (implements
OfficeLocal) a local type of BuildingLocal. The session bean (Office) must explicitly
declare the interfaces that will be included in its local types.
{quote}
I'm not completely sure about this statement. The spec does allow Session Bean’s
Business Interface to have superinterfaces (see *4.9.7 Session Bean’s Business Interface*
and *4.9.11 Session Bean’s Local Interface*). And the section you're touching applies
to Session Bean Superclasses only.
Anyway I will update the exclude list in 1.0 branch.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
9:27 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
There are actually more failures: In 1.1.5.Final there are these 3:
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest.testSpecializingBeanHasNameOfSpecializedBean
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest.testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.testSpecializedBeanNotInstantiated
and in 1.1.8.Final there are these 13 failures:
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest.testSpecializingBeanHasNameOfSpecializedBean
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerFieldBeanCreate
org.jboss.jsr299.tck.tests.implementation.producer.method.definition.ProducerMethodDefinitionTest.testNonStaticProducerMethodInheritedBySpecializingSubclass
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerFieldForNullValueNotDependent
org.jboss.jsr299.tck.tests.inheritance.specialization.simple.SimpleBeanSpecializationTest.testProducerMethodOnSpecializedBeanCalledOnSpecializingBean
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsDependent
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testSpecializedBeanAlwaysUsed
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsNotDependent
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.testSpecializedBeanNotInstantiated
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerStaticFieldBean
org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest.testProducerFieldNotAnotherBean
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest.testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean
org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefinitionTest.testNonStaticProducerMethodInheritedBySpecializingSubclass
I looked at sections 4.9.7 and 4.9.11 and yes session beans can have interfaces that have
superinterfaces but according to section 4.9.2.1 a session bean needs to explicitly
include a super interface in its set of exposed views for that interface to apply as a
local business interface.
It's interesting in that if I change the GlassFish code to include super interfaces in
the session beans local interface view then all of these tests pass. So it appears that
weld is expecting super interfaces for session beans when it shouldn't (and it appears
this change happened in 1.1.5.Final as all of these tests pass in 1.1.4.Final.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
6:43 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
It appears to me that there is a conflict between the ejb and cdi specs. Section 4.9.2.1
of the ejb spec says, "...the client views exposed by a particular session bean are
not inherited by a subclass that also happens to define a session bean." And it
provides a code example illustrating inherited interfaces and explicitly states that the
inherited interface is not part of the subclass' client view.
Section 3.2.2 of the CDI spec states, "The unrestricted set of bean types for a
session bean contains all local interfaces of the bean and their superinterfaces."
Perhaps I'm interpreting the specs incorrectly or I don't fully understand what
the bean types of a session bean are (I'm certainly not an ejb expert!) Wdyt?
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
9:57 a.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Martin Kouba commented on WELD-1133:
------------------------------------
bq. Perhaps I'm interpreting the specs incorrectly or I don't fully understand
what the bean types of a session bean are (I'm certainly not an ejb expert!) Wdyt?
Nor am I. Though my interpretation is that EJB spec (4.9.2.1 Session Bean Superclasses)
does not say anything about session bean business interface inheritance. It only covers
superclasses and the example is showing component inheritance (superclass) does not work.
Yes, if you're right this would mean conflict between EJB and CDI spec. Anyway I sent
the question to some CDI/EJB experts. So I hope we'll have more relevant information
soon.
AFAIK JBoss AS (4.2.x ,5.x, 7.x) supports this kind of inheritance.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
8:17 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
Martin,
Have you received any answers yet?
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
12:16 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Martin Kouba commented on WELD-1133:
------------------------------------
Joseph, so far I only have the answer from Pete Muir - he thinks that session bean
business interface inheritance is ok. I'll try to drive this forward...
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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:55 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Joseph Snyder commented on WELD-1133:
-------------------------------------
Thanks Martin...not to belabor the point but please reference section 4.9.2.1, Session
Bean Superclasses, of the ejb spec as it provides a very specific example of what is and
what is not allowed as far as interface inheritence.
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
12:36 p.m.
[
https://issues.jboss.org/browse/WELD-1133?page=com.atlassian.jira.plugin....
]
Martin Kouba resolved WELD-1133.
--------------------------------
Resolution: Rejected
The reason of failures was outdated canonical exclude list (related TCK tests are not
valid any more).
See also Session Bean business interface inheritance thread on cdi-dev:
http://lists.jboss.org/pipermail/cdi-dev/2012-June/001885.html
Session EJB deployment failure
------------------------------
Key: WELD-1133
URL: https://issues.jboss.org/browse/WELD-1133
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Infrastructure
Affects Versions: 1.1.5.Final, 1.1.6.Final, 1.1.7.Final, 1.1.8.Final
Environment: linux
Reporter: Joseph Snyder
Assignee: Marko Lukša
Starting with Weld 1.1.5.Final there are several CTS failures when running CTS against
GlassFish. One specific test failure is
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest.
When the application associated with this test is deployed the deployment fails (see
"Deployment Failure" below). I investigated the specs and it appears that weld
is expecting the type of the session ejb (Office) to include the interface defined by the
session bean that it extends (Building).
The CDI spec states in section "4.3.1 Direct and indirect specialization"
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y,
the container automatically detects the problem and treats it as a definition error.
..
However this is in direct violation of the ejb 3.1 specification section 4.9.2.1 Session
Bean Superclasses:
...
As an example, the client views exposed by a particular session bean are not inherited by
a subclass that also happens to define a session bean.
@Stateless
public class A implements Foo { ... }
@Stateless
public class B extends A implements Bar { ... }
Assuming Foo and Bar are local business interfaces and there is no associated deployment
descriptor, session bean A exposes local business interface Foo and session bean B exposes
local business interface Bar, but not Foo.
...
Deployment Failure:
[#|2012-05-09T18:19:20.875-0400|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|WELD-001511
Specializing bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
org.glassfish.deployment.common.DeploymentException: WELD-001511 Specializing bean
Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Office with qualifiers
[@Any @Default]; local interfaces are [OfficeLocal] does not have bean type interface
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.BuildingLocal of
specialized bean Session bean [class
org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Building with qualifiers
[@Any @Default]; local interfaces are [BuildingLocal]
--
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
4339
days inactive
4368
days old
14 comments
4 participants
participants (4)
-
Ales Justin (JIRA) -
Joseph Snyder (JIRA)
-
Jozef Hartinger (JIRA)
-
Martin Kouba (JIRA)