search

ParthPancholi / janrain4j

Automatically exported from code.google.com/p/janrain4j
Apache License 2.0
0 stars 0 forks source link

EngageServiceImpl (created without Config) should always use global Config #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently the EngageServiceFactory.getInstance() will retrieve the Config from 
the ConfigHolder and stores it in EngageServiceImpl.

If the 'global' Config is changed using ConfigHolder.setConfig(newConfig) the 
EngageServiceImpl is still using the old config.

Original issue reported on code.google.com by marceloverdijk on 15 Oct 2010 at 1:28

GoogleCodeExporter commented 9 years ago

Original comment by marceloverdijk on 15 Oct 2010 at 1:29

GoogleCodeExporter commented 9 years ago

Original comment by marceloverdijk on 15 Oct 2010 at 1:37