AEM 6.3: Felix SCR Annotations Deprecated - Replacement for @SlingFilter? | Community
Skip to main content
timlwhite
Level 2
May 24, 2017
Solved

AEM 6.3: Felix SCR Annotations Deprecated - Replacement for @SlingFilter?

  • May 24, 2017
  • 16 replies
  • 24265 views

Hello, it appears that the Felix SCR annotations have been deprecated in AEM 6.3.  This is not reflected on the Sling website or documentation as far as I can tell, but is appearing that way when we compile against the 6.3 uberjar.

In fact, the latest AEM Maven Archetype does not include the Felix SCR dependency at all.

I see this blog post from last year that covers a lot of conversion questions.

And this very recent one from Feike.

The OSGi 6 method for registering configuration properties using a separate interface class is fairly convoluted, and thinly documented, but with enough time and money I am sure we can figure it out.

However, there does not seem to be mention in either article of what is replacing the @SlingFilter annotation, which is mentioned as the recommended approach even in fairly recent articles.

All our classes that use the @SlingFilter annotation no longer work (they are throwing ArrayIndexOutOfBounds exceptions), even keeping the Felix SCR dependency, and updating it to the latest version.

Is there documentation somewhere of what is replacing the @SlingFilter annotation?

Is there a plan for a more complete document describing the recommended migration path, and changes to the product that cause existing @SlingFilter usage not to work?

Thanks!

Tim

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Feike_Visser1

when using non-String types make sure to use the correct data-type.

Example here for the service-ranking and using :Integer

https://github.com/heervisscher/htl-examples/blob/master/core/src/main/java/com/adobe/examples/htl/core/bindings/CustomBindingProvider.java

16 replies

Feike_Visser1
Adobe Employee
Adobe Employee
May 25, 2017

I am not aware that the Felix annotations are deprecated in AEM6.3.

To your question on @SlingFilter, this is same like @SlingServlet

There isn't an equivalent you can use. You need to specify the properties like in this sample for a servlet.

https://github.com/heervisscher/htl-examples/blob/master/core/src/main/java/com/adobe/examples/htl/core/servlets/SimpleServlet.java

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe EmployeeAccepted solution
Adobe Employee
May 25, 2017

when using non-String types make sure to use the correct data-type.

Example here for the service-ranking and using :Integer

https://github.com/heervisscher/htl-examples/blob/master/core/src/main/java/com/adobe/examples/htl/core/bindings/CustomBindingProvider.java

timlwhite
timlwhiteAuthor
Level 2
May 25, 2017

Yes, most of the Felix annotations show deprecated when compiling against the 6.3 UberJar.  I'll try setting things up with @Component. Thanks!

Feike_Visser1
Adobe Employee
Adobe Employee
May 29, 2017
Level 4
February 10, 2018

I use OSGI R6 annotation based approach:

@Component(service = Filter.class, property = {

EngineConstants.SLING_FILTER_SCOPE + "=" + EngineConstants.FILTER_SCOPE_REQUEST,

Constants.SERVICE_RANKING + ":Integer=" + -10002

})

public class MyCustomFilter implements Filter {

Feike_Visser1
Adobe Employee
Adobe Employee
February 10, 2018
Level 2
April 17, 2018

import com.icfolson.aem.library.core.services.OsgiConfiguration

import com.ingredion.aem.core.services.EloquaService

import com.ingredion.aem.core.services.EloquaServiceUS

import com.ingredion.aem.core.services.SalesforceService

import org.apache.felix.scr.annotations.Activate
import org.apache.felix.scr.annotations.Component
import org.apache.felix.scr.annotations.Modified
import org.apache.felix.scr.annotations.Property
import org.apache.felix.scr.annotations.Service


@Component(label = "Ingredion Eloqua Connector Service For US", metatype = true)

@Service(EloquaServiceUS)

class DefaultEloquaServiceUS implements EloquaServiceUS

{

   private static final String DEFAULT_URL = "https://s2141011786.t.eloqua.com/e/f2"
   private static final String DEFAULT_ELQ_SITE_ID = "2141011786"

   @Property(label = "Eloqua URL", description = "Eloqua Url",

  value = DefaultEloquaServiceUS.DEFAULT_URL)

   private static final String URL = "url"

   @Property(label = "Eloqua Site ID", description = "This ID will tell Eloqua that the request is coming from Ingredion",

  value = DefaultEloquaServiceUS.DEFAULT_ELQ_SITE_ID)

   private static final String ELQ_SITE_ID = "elqSiteId"

   String url

   String elqSiteId

   @Activate
  @Modified
   void activate(Map<String, Object> properties) {

   def configuration = new OsgiConfiguration(properties)

   url = configuration.getAsString(URL, DEFAULT_URL)

   elqSiteId = configuration.getAsString(ELQ_SITE_ID, DEFAULT_ELQ_SITE_ID)

  }

}

This is my code and this was written in groovy.

Now we are upgrading to aem 6.3 from 6.1.

@Activate, @Modified, @Component, @Service is dericated.

So i replaced with osgi annotations.

But not sure how to replace below lines.

@Property(label = "Eloqua URL", description = "Eloqua Url",

  value = DefaultEloquaServiceUS.DEFAULT_URL)

   private static final String URL = "url"

  

Can anyone suggest me how to replace @Property?

Feike_Visser1
Adobe Employee
Adobe Employee
April 17, 2018
Level 2
July 30, 2018

Hi,

Did you get the replacement for @Property? Also what is the replacement for @Service in osgi? Can you share the exact import here. I'm struck with the two issues. Thanks in advance.

Regards,

Vijay

priydarshnas479
Level 2
August 6, 2018

did you find replacement for @Property ?