Is it safe to use Apache Sling Taglib version 1.3? | Community
Skip to main content
Dinu_Arya
Level 6
October 16, 2015
Solved

Is it safe to use Apache Sling Taglib version 1.3?

Hi Team,

I need to get the resource of a content source and I have to pass this as parameter to a method using JSTL. I'm achieving through Apache sling taglib 1.3

<%@taglib prefix="sling" uri="http://sling.apache.org/taglibs/sling" %>

But in AEM OOTB global.jsp we have 1.0 version. Is it safe o use? Will it create any problem anywhere? I have followed http://sling.apache.org/documentation/bundles/sling-scripting-jsp-taglib.html . Your comments are welcome.

Thanks,

AryA.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
JustinEd3Accepted solution
Employee
October 16, 2015

Hi,

You will get errors if you try to define the "sling" prefix multiple times. But this is relatively easy to avoid and the behavior should be entirely deterministic.

Regards,

Justin

3 replies

JustinEd3Accepted solution
Employee
October 16, 2015

Hi,

You will get errors if you try to define the "sling" prefix multiple times. But this is relatively easy to avoid and the behavior should be entirely deterministic.

Regards,

Justin

Translate
Employee
October 16, 2015

To be clear, this is a general JSP restriction and not specific to this taglib.

Translate
Dinu_Arya
Dinu_AryaAuthor
Level 6
October 16, 2015

Yes Justin. You are right. I got the errors. So I changed "sling"prefix to "newSling" and used in my JSP. It's working as I expected. Will it create any problems in future?

Translate