HI Robert As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per FELIX-3754. It has been a timing issue handling the activator and the bind methods.
Hope this helps. Regards Felix Am 28.05.2013 um 16:52 schrieb Robert Munteanu: > Hi, > > I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2 . > > In the Apache Sling project we have a component which binds service > references in its own activate method, and expects them to be bound to > itself later on ( see [0], near the end of the activate method ). > > With SCR 1.6.0, these components are bound. With 1.6.2 they are not bound. > > I found nothing relevant to this edge case in the OSGi Declarative > Services spec, so my question is : is this change intended or > accidental? > > Thanks, > > Robert > > > [0]: > http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
