Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Is it safe to use Apache Sling Taglib version 1.3?

Avatar

Level 7

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.

1 Accepted Solution

Avatar

Correct answer by
Employee

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

View solution in original post

3 Replies

Avatar

Correct answer by
Employee

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

Avatar

Employee

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

Avatar

Level 7

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?