[
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...
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