[
https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600378#comment-12600378
]
Antoine Sabot-Durand commented on SEAMSOCIAL-10:
------------------------------------------------
You're right guys. I guess I mixed up things here. But I've got 2 design issues
related to OAuth applications settings, OAuth services beans and OAuth user
connection relationship and lifecycles.
I close the ticket and re-think about my problem.
> Create service Bean when needed (configuration is available)
> ------------------------------------------------------------
>
> Key: SEAMSOCIAL-10
> URL: https://issues.jboss.org/browse/SEAMSOCIAL-10
> Project: Seam Social
> Issue Type: Enhancement
> Components: OAuth Core
> Affects Versions: 3.0.0.Alpha1
> Reporter: Antoine Sabot-Durand
> Assignee: Antoine Sabot-Durand
> Priority: Minor
> Original Estimate: 1 week, 1 day
> Remaining Estimate: 1 week, 1 day
>
> Right now each, each Service bean is created at application start. If there
> is no configuration for the bean an dependency exception is thrown.
> * Services should be created at startup only if configuration is available
> at application level : source code or Config file
> * We should be able to create service dynamically at run time.
>
> So perhaps OAuthServices should be created by producers.
--
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
