[
https://issues.jboss.org/browse/SEAMSOCIAL-10?page=com.atlassian.jira.plu...
]
Marek Schmidt commented on SEAMSOCIAL-10:
-----------------------------------------
I am not exactly sure why do we need that... If you just don't inject any Faceboook
service in your application, no instance of it will be created, right?
And even if that is a problem for whatever reason, why do it at runtime? Isn't
deployment time enough? In which case you can just split the module into service-specific
submodules and just let developers package the application with the services they need...
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