See also this article by Nate: http://www.nateyolles.com/blog/2017/05/osgi-declarative-services-annotations-in-aem

But what is the issue you are having? That is not clear to me now.

This looks a non-related error

The way you get the resourceResolver is fine, however you must close it. The golden rule is "you create, you close".Normally you can do this in a finally{} clause, or if you use 6.2 or above you can benefit from the AutoCloseable implementation.Example here: https://github.com/heervisscher/htl-examp...

Also do realize that this code creates hanging sessions that you want to avoid

Do you see anything related in the error.log?

There is no need to include global.jsp in HTL files.This is required for JSP files

when using non-String types make sure to use the correct data-type.Example here for the service-ranking and using :Integerhttps://github.com/heervisscher/htl-examples/blob/master/core/src/main/java/com/adobe/examples/htl/core/bindings/CustomBindingProvider.java

I am not aware that the Felix annotations are deprecated in AEM6.3.To your question on @SlingFilter, this is same like @SlingServletThere 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/cor...

You can have multiple ways here, but you can of course store the clientlibs you want to use also at jcr:content level.Then using the inheritedPageProperties you can request the property.This way you can override the setting at each level.