<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Accesscontroltool on TechBlog - Tarasenko Oleksandr</title><link>https://taradevko.com/tags/accesscontroltool/</link><description>Recent content in Accesscontroltool on TechBlog - Tarasenko Oleksandr</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 16 Jan 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://taradevko.com/tags/accesscontroltool/index.xml" rel="self" type="application/rss+xml"/><item><title>OSGi: migration to OSGi annotations caveats</title><link>https://taradevko.com/2019/01-16-migration-osgi-annotations-caveats-sling-aem/</link><pubDate>Wed, 16 Jan 2019 00:00:00 +0000</pubDate><guid>https://taradevko.com/2019/01-16-migration-osgi-annotations-caveats-sling-aem/</guid><description>&lt;p&gt;I think that every developer from AEM/Sling world has already read many articles regarding switching to the &lt;a href="http://www.nateyolles.com/blog/2017/05/osgi-declarative-services-annotations-in-aem"&gt;R6&lt;/a&gt; and &lt;a href="http://blogs.adobe.com/experiencedelivers/experience-management/osgi/using-osgi-r7-annotations-aem/"&gt;R7&lt;/a&gt; OSGi annotations. But new annotations do not only allow us to write less boilerplate code, but also bring new caveats and we better be aware of them.&lt;/p&gt;
&lt;p&gt;Several days ago there was suggested a &lt;a href="https://github.com/Netcentric/accesscontroltool/pull/346"&gt;PR&lt;/a&gt; for &lt;a href="https://github.com/Netcentric/accesscontroltool"&gt;AC Tool&lt;/a&gt; which fixes missing referenced service in AEM 6.4, even though this service was shown as satisfied in Web Console. The fix contained next change:&lt;/p&gt;</description></item></channel></rss>