Hello Bram, The "callback not found on component instances ..." log is normally displayed when a callback is not found from some given callback instance(s).
However, I just saw that when a callback instance was used (it is the case when an adapter is used), then the log was wrong: it did not log the actual callback instance. I fixed this in the revision 1746480. Can you please svn update the dm from the trunk, and try to reproduce, and see if the log is more meaningful now ? Then , if you can't figure out what is going one, then can you tell me how I can reproduce the problem using amdatu-web ? let me know. cheers; /Pierre On Wed, Jun 1, 2016 at 4:33 PM, Bram Pouwelse <[email protected]> wrote: > Hi, > > I have some troubles with a dependency manager adapter service, for some > reason it fails to call the remove callback (looking at the message there > are no instances available to invoke the method on). Tried to reproduce the > issue in less complex project but I don't have the problem there... > > The component is added in the DependencyActivatorBase#init method full > source is in bitbucket [1] > > manager.add(createAdapterService(ApplicationService.class, null, "onAdd", > "onChange", "onRemove") > .setInterface(Servlet.class.getName(), null) > .setImplementation(WinkServlet.class) > .setCallbacks("dmInit", "dmStart", "dmStop", "dmDestroy") > ); > > Any hints on where to start looking would be welcome ;) > > Regards, > Bram > > 1: > > https://bitbucket.org/amdatu/amdatu-web/src/74aabd7944c1e2365d2f8313228d69f3278a1d7a/org.amdatu.web.rest/src/org/amdatu/web/rest/wink/Activator.java?at=feature%2FAMDATUWEB-59&fileviewer=file-view-default >
