<tiles:importAttribute />
<nd:tabmgr page='<%= pageContext.getAttribute("currentPage"%>'/>
<nd:tabmgr> is a taglib that I wrote. If you pass it text for the current page, it displays a tab menu with the currentPage selected. Works like a charm like this:
<nd:tabmgr page='main'/>
I used <tiles:importAttribute /> to make all the tiles template attributes accessable through the pageContext. This to works well.
When I went back and debugged it, I found that the string "<%= pageContext.getAttribute("currentPage"%>" was not rendered but sent directly to the taglib as a text string. Arg!
It appears that the tag lib is rendered first. And then the JSP tags are rendered last. What is going on here? Is this how it works? Is there a way to render the JSP tag first?
<nd:tabmgr page='<%= pageContext.getAttribute("currentPage"%>'/>
<nd:tabmgr> is a taglib that I wrote. If you pass it text for the current page, it displays a tab menu with the currentPage selected. Works like a charm like this:
<nd:tabmgr page='main'/>
I used <tiles:importAttribute /> to make all the tiles template attributes accessable through the pageContext. This to works well.
When I went back and debugged it, I found that the string "<%= pageContext.getAttribute("currentPage"%>" was not rendered but sent directly to the taglib as a text string. Arg!
It appears that the tag lib is rendered first. And then the JSP tags are rendered last. What is going on here? Is this how it works? Is there a way to render the JSP tag first?