[ https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plu... ] Antoine Sabot-Durand commented on SEAMSOCIAL-10: ------------------------------------------------ CDI beans cannot be registered at runtime (but a new instance can be created via the @New Qualifier) As we don't want each service bean being created by default (if I only need Twitter, I don't want Facebook service), we probably need an extension to register required beans when the container starts. But if we want to register services dynamically at runtime perhaps what we need is more a factory for services than a service bean... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plu... ] Antoine Sabot-Durand commented on SEAMSOCIAL-10: ------------------------------------------------ I was thinking of the "Hootsuite" or "Seesmic" use case where user would ask for the creation of a connection to a given social service within the application. I think I missed the "if it's not injected it's not created" as my example app use an @Any injection point on an Instance<>. But the way I designed it is wrong because, if the container doesn't create the bean, it checks dependency at start time and as I created a OAuthSettings bean with a qualifier for each service that is injected in the service bean, I need to configure those settings even for services I don't need. I thought about splitting services in different modules but I was not sure it would fit in global Seam best practices design. Anyway, thanks Marek for your comment : I feel less alone and it helps me a lot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plu... ] Antoine Sabot-Durand edited comment on SEAMSOCIAL-10 at 5/6/11 9:33 AM: ------------------------------------------------------------------------ My first remark wasn't very clear, I meant : manage multiple Twitter or Facebook account in the same application was (Author: antoinesabot-durand): My first remark wasn't very clear : I meant manage multiple Twitter or Facebook account in the same application -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plu... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira