[
https://jira.jboss.org/jira/browse/CDITCK-134?page=com.atlassian.jira.plu...
]
Gurkan Erdogdu commented on CDITCK-134:
---------------------------------------
Yes, it is a passivation capable via Serializable, but we do not validate it because
1* RequestScoped is not passivation capable scope
2* Bean is not injected into any other bean in the TCK test
Therefore, it does not trigger validation at startup. Why would we validate bean at
startup cost if we know that it is not injected
in any bean that has passivation capable scope?
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