[
https://jira.jboss.org/jira/browse/CDITCK-134?page=com.atlassian.jira.plu...
]
David Allen commented on CDITCK-134:
------------------------------------
Right, the RequestScope is not a passivating scope.
In Section 6.6.1, A managed bean is passivation capable if and only if the bean class is
serializable and all interceptors and decorators of
the bean are serializable. The "if and only if" is very explicit that
UnderWaterCity is passivation capable. It does not depend on any other factors.
Furthermore, if UnderWaterCity happened to be injected into another RequestScoped bean,
then according to section 6.6.2, it is a passivation capable dependency too: all beans
with normal scope are passivation capable dependencies,
Decorator not applied to a passivation capable bean
---------------------------------------------------
Key: CDITCK-134
URL:
https://jira.jboss.org/jira/browse/CDITCK-134
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tests
Reporter: Gurkan Erdogdu
Assignee: David Allen
Fix For: 1.0.2.CR1, 1.1.0.CR1
org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor
org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod
org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField
These packages tests decorator injection points to check if they are passivation capable
dependency or not, however the decorator is not applied to a passivation capable bean
--
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