Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Issues with resolving taglibs in JSP based component

Avatar

Avatar
Validate 1
Level 1
aemninja
Level 1

Likes

2 likes

Total Posts

53 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
aemninja
Level 1

Likes

2 likes

Total Posts

53 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
aemninja
Level 1

03-06-2021

Hello Community - Since my previous request was marked as resolved so I am opening this to get an assistance here. Please note that I am using JSP based component not HTL. This is a very simple component which takes the taglib from the dialog and inject the respective tags for the provided taglib. If I simply hardcoded the taglib directly in the component it works fine and I could see the expected results but it doesn't work when I provide the taglib via dialog. Not sure what is causing the issue. Any help on this is highly appreciated.

SS1.PNG

component.jsp:

<%@include file="/libs/foundation/global.jsp" %>
<%@page import="com.day.cq.wcm.api.WCMMode"%>
<%@ taglib uri="http://company.com/clientLib-taglib" prefix="evaltag" %>

<% if((WCMMode.fromRequest(request) != WCMMode.DISABLED)) { %>
Taglib Component
<%} %>

${properties.openhtml}


This is what I author from the dialog:

<evaltag:includeClientLibs async="true" defer="false" js="clientlib" verName="${projectVersion}" />

 

@BrianKasingli @Vijayalakshmi_S

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

518 likes

Total Posts

654 posts

Correct Reply

215 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

518 likes

Total Posts

654 posts

Correct Reply

215 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

07-06-2021

Hi @aemninja,

Can you try like the below. If it is not working, share your complete JSP if possible. Also share the node structure of how this particular field is saved (property value from respective node)

<%
String openHtml = properties.get("openhtml", ""); // provided openhtml dialog field/content authored is saved as String
%>
<%= openHtml %>

Answers (0)