[cdi-dev] [JBoss JIRA] (CDI-513) Clarify whether passivating pseudo-scopes are valid

[Sven Linstaedt (JIRA)]

    [ https://issues.jboss.org/browse/CDI-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045774#comment-13045774 ] 

Sven Linstaedt edited comment on CDI-513 at 3/4/15 3:33 AM:
------------------------------------------------------------

...and having a PassivationCapable implementing bean returned by the container, which might be used by custom pseudo scopes.


was (Author: tzwoenn):
...and having a PassivationCapable implementing returned by the container, which might be used by custom pseudo scopes.

> Clarify whether passivating pseudo-scopes are valid
> ---------------------------------------------------
>
>                 Key: CDI-513
>                 URL: https://issues.jboss.org/browse/CDI-513
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>    Affects Versions: 1.2.Final
>            Reporter: Mark Struberg
>
> On behalf of Jozef I copied this to a CDI ticket... See CDITCK-466
> I personally think it is clear as there is no single word which forbids this and there is a very vocal description about the single flags.
> -----
> AddingPassivatingScopeTest is illegal as addScope for passivating non-normalscopes is perfectly fine.
> There is nothing in the spec which says that a non-normalscope cannot be passivating.
> The practical use case for this is e.g. when bridging over to Spring. Those beans might need to get checked for Serializable BUT spring brings it's own proxies. So we do not need to wrap it into just another normalscoping proxy.
> Actually the test should come in 2 flavours:
> 1.) RomanEmpire being Serializable -> all fine must work
> 2.) RomainEmpire not Serializable -> DefinitionException



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)