[
https://issues.jboss.org/browse/SEAMSOCIAL-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603162#comment-12603162
]
Antoine Sabot-Durand commented on SEAMSOCIAL-12:
------------------------------------------------
I start the task by putting all the services bean to dependent scope and
created a qualifier (@RelatedTo) and an enum class Service listing all the
services to allow bean selection for a given service. Thus it's now possible to
get more than one bean for each services.
The OAuthSettings is now in @ApplicationScope since we support out of the box
only one OAuth application settings by service. The configuration file will add
qualifiers and value to create effective OAuthServiceSettings beans.
> Allow the support of multi-account on a given social service
> ------------------------------------------------------------
>
> Key: SEAMSOCIAL-12
> URL: https://issues.jboss.org/browse/SEAMSOCIAL-12
> Project: Seam Social
> Issue Type: Enhancement
> Components: OAuth Core
> Reporter: Antoine Sabot-Durand
> Assignee: Antoine Sabot-Durand
> Priority: Minor
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> It would be nice to support multi-account for a given social service (my
> personal Twitter account and my company's one).
> Since it can have an important impact on API design, the hook for this
> evolution should be created now to be sure we can go in this direction in the
> futur.
> The best would be to keep the standard behavior (single account for a
> service) as simple as today.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
