[seam-issues] [JBoss JIRA] Updated: (SEAMSECURITY-76) seam security external ScopeProducers don't work anywhere except AS6

[Marek Schmidt (JIRA)]

     [ https://issues.jboss.org/browse/SEAMSECURITY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Schmidt updated SEAMSECURITY-76:
--------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.1.0.Beta1
       Resolution: Done


fixed

All the *ScopeProducers (such as OpenIdProviderInVirtualApplicationScopeProducer, OpenIdProviderInApplicationScopeProducer, ...) are @Vetoed, and to enable the specific producer, you now have to use, e.g.:

<idp:SamlIdpInApplicationScopeProducer>
<s:modifies/>
</idp:SamlIdpInApplicationScopeProducer>

in seam-beans.xml

> seam security external ScopeProducers don't work anywhere except AS6
> --------------------------------------------------------------------
>
>                 Key: SEAMSECURITY-76
>                 URL: https://issues.jboss.org/browse/SEAMSECURITY-76
>             Project: Seam Security
>          Issue Type: Bug
>    Affects Versions: 3.0.0.Final
>            Reporter: Marek Schmidt
>            Assignee: Marek Schmidt
>             Fix For: 3.1.0.Beta1
>
>
> The design of the Security External module depends on undefined behaviour of alternatives. It defines alternatives (*ApplicationScopeProducer and *VirtualApplicationScopeProducer) in the module and expects the application to set the alternatives in its beans.xml, which isn't supported by CDI spec (see CDI-18) and doesn't seem to work anywhere except JBoss AS 6.
> We should probably just remove the Producers and make the beans @ApplicationScoped directly. Users interested in changing the scope of those beans could still use Seam Config for that.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira