[JBoss JIRA] Created: (CDITCK-208) TCK should test bean deployment archive behaviour more thoroughly
by Stuart Douglas (JIRA)
TCK should test bean deployment archive behaviour more thoroughly
------------------------------------------------------------------
Key: CDITCK-208
URL: https://issues.jboss.org/browse/CDITCK-208
Project: CDI TCK
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Tests
Reporter: Stuart Douglas
Fix For: 1.1.0.CR1
The TCK does not currently test that the behaviour of bean deployment archives confirms to the spec. In particular we need tests for:
- Different interceptor ordering between BDA's with the same scope
- Tests that all beans in a war are visible to each other (and WEB-INF/classes should be visible to WEB-INF/lib)
- Ear /lib is visible to everyone
- Portable Extensions are loaded correctly and any beans they define are defined at a global scope (as per the current spec, this may change in 1.1)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (CDITCK-73) Test abstract decorators functionally
by Marius Bogoevici (JIRA)
Test abstract decorators functionally
-------------------------------------
Key: CDITCK-73
URL: https://jira.jboss.org/jira/browse/CDITCK-73
Project: CDI TCK
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.GA
Reporter: Marius Bogoevici
Fix For: 1.0.1.CR1
The current assertions for abstract decorators are just testing that abstract classes annotated with decorators can be enabled and are resolved correctly. However, no functionality test involving abstract decorators is carried out.
The assertions should test that:
a) abstract decorators can be applied at all (i.e. instantiated)
b) methods which are not decorating methods of the decorated type cannot be abstract (DefinitionException)
c) when abstract decorating method are called as part of the decorator chain, they are actually deferring the call to the injected delegate
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (WELD-927) ViewScoped does not work because org.jboss.weld.bean.Managedbean is not serializable
by Thomas Andraschko (JIRA)
ViewScoped does not work because org.jboss.weld.bean.Managedbean is not serializable
------------------------------------------------------------------------------------
Key: WELD-927
URL: https://issues.jboss.org/browse/WELD-927
Project: Weld
Issue Type: Bug
Components: CDI API, Class Beans (Managed and Session), Scopes & Contexts, Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.1.1.Final
Environment: Tomcat/Jetty, Weld Servlet 1.1.2-SNAPSHOT or 1.1.1-Final, MyFaces 2.x or 2.1.x, Seam Faces 3.0.1-Final, Seam Persistence 3.0.0
Reporter: Thomas Andraschko
Priority: Blocker
If you use @ViewScoped, a will exception occur that org.jboss.weld.bean.Managedbean is not serializable.
This a blocker because we can't use @ViewScoped with Weld (and this envorionment) and Seam does not work with OWB.
This should be the same issue as: https://issues.apache.org/jira/browse/EXTCDI-118
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (CDITCK-61) Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar
by Santiago Pericas-Geertsen (JIRA)
Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar
----------------------------------------------------------------------------
Key: CDITCK-61
URL: https://jira.jboss.org/jira/browse/CDITCK-61
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tests
Affects Versions: 1.0.1.CR1
Environment: Solaris x86 / JDK 16u6 / GF v3
Reporter: Santiago Pericas-Geertsen
We have found that certain TCK test load classes from jsr299-tck-api.jar and jsr299-tck-impl.jar, but these jars are not normally included in the generated application bundles. An example of such a test is:
*.deployment.packaging.installedLibrary.WarInstalledLibraryTest.test
which looks for:
org/jboss/jsr299/tck/tests/deployment/packaging/installedLibrary/Bar
This test fails with GF as these classes are not available to applications. Should jsr299-tck-api.jar and jsr299-tck-impl.jar be bundled with apps? (We can provide a complete list of tests that depend on these TCK jars if needed).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months