I can live with eliminating the extra call.
On Mon, Feb 7, 2011 at 5:34 AM, Sergey Beryozkin <[email protected]> wrote: > Hi Benson > > I've done a quick test, I believe you're probably doing > > setServiceClass and setServiceBean() calls. I've added the javadocs > recently, the setServiceBean() was added for Spring handlers to inject an > instantiated bean and it was added after setServiceClass() and > setResourceProvider() methods had been introduced. If you prefer calling > setServiceBean() programmatically then please avoid calling > setServiceClass(). > I'll update the docs, and if you feel calling setServiceClass() should not > have sideeffect when setServiceBean() is called then please open a JIRA :-) > > cheers, Sergey > > On Sun, Feb 6, 2011 at 8:01 PM, Benson Margulies <[email protected]>wrote: > >> It seems as if my code that was successful at using a singleton object >> for a service bean via sf.setServiceBean(coordinatorService) has >> stopped working. New objects are being created for each request. >> >
