[
https://issues.jboss.org/browse/CDI-286?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-286:
----------------------------------
Yes, we can. But that wouldn't follow the rest of the chapter. E.g.:
{quote}
If a managed bean or stateful session bean which declares a passivating scope:
* is not passivation capable,
* ...
{quote}
Maybe we should reword all similar pieces in the chapter.
Inconsistencies in chapter "Validation of passivation capable
beans and dependencies"
-------------------------------------------------------------------------------------
Key: CDI-286
URL:
https://issues.jboss.org/browse/CDI-286
Project: CDI Specification Issues
Issue Type: Bug
Affects Versions: 1.1.PRD
Reporter: Martin Kouba
Fix For: 1.1 (Proposed)
The spec states in 6.6.4. "Validation of passivation capable beans and
dependencies":
{quote}
If a bean which declares a passivating scope type, or any stateful session bean, has a
decorator or interceptor which is not a
passivation capable dependency, the container automatically detects the problem and
treats it as a deployment problem.
{quote}
WRT CDI-136 "If a bean which declares a passivating scope type, or any stateful
session bean," should be replaced with: "If a managed bean or stateful session
bean which declares a passivating scope".
I'm not sure about the wording _"has a decorator or interceptor which is not a
passivation capable dependency"_ because the wording in section 6.6.1.
"Passivation capable beans" is _"interceptors and decorators of the bean
are passivation capable"_ (passivation capable dependency vs passivation capable).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira