Tags not being executed on first request...

[Nathan Wilhelmi <wi...@ucar.edu>]

Hello - We are using Tomcat 6.0.14, we have some pages that use some 
nested tags, such as Page A -> Tag A -> Tab B, it's not reclusive 
problem. We are using the JSP.tag files for this. The problem is on the 
first request, Page A -> Tag A works fine, however Tag B never appears 
to be rendered. Now on the second request Page A -> Tag A -> Tab B is 
all properly executed. Is this a know issue, are there any workarounds, 
are we doing something that isn't supported/allowed?

Thanks!

-Nate


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tags not being executed on first request...

[Nathan Wilhelmi <wi...@ucar.edu>]

A few more details based on your suggestion.

TagB looks like this (tagb.tag)

<%@ include file="/WEB-INF/views/jsp/common/include.jsp" %>

<%@ attribute name="ID" required="true" type="java.lang.String"  %>
   
    <c:url value="/somelink.htm">
        <c:param name="XYZ" >${ID}</c:param>
    </c:url>

TagA looks like this (taga.tag)

{html/jsp code}
    <c:when test="count > 0}">
         <a href="<tags:taga ID="${identifier}" /> "> Some Link text </a>
    </c:when>

{html/jsp code}
   
The when condition gets evaluated 3 times on the page, first 2 are 
false, last is true. I put some logging statements in TagB, around the 
url tag. In the third case the tag is called with the proper value, 
however the param tag is ignored, just the link is generated with the 
parameter. Now if I refresh the page in the browser it all works 
correctly. So I am not sure if this is a tomcat issue or a JSTL lib 
issue? Any thoughts?

-Nate

david delbecq wrote:

> It's probably that tag A you use has conditional logic that is false 
> upon first request. Making it skip it's content. Difficult to tell 
> more without knowing the taglibs involved and the associated conditions
> Nathan Wilhelmi a écrit :
>
>> Hello - We are using Tomcat 6.0.14, we have some pages that use some 
>> nested tags, such as Page A -> Tag A -> Tab B, it's not reclusive 
>> problem. We are using the JSP.tag files for this. The problem is on 
>> the first request, Page A -> Tag A works fine, however Tag B never 
>> appears to be rendered. Now on the second request Page A -> Tag A -> 
>> Tab B is all properly executed. Is this a know issue, are there any 
>> workarounds, are we doing something that isn't supported/allowed?
>>
>> Thanks!
>>
>> -Nate
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tags not being executed on first request...

[david delbecq <de...@oma.be>]

It's probably that tag A you use has conditional logic that is false 
upon first request. Making it skip it's content. Difficult to tell more 
without knowing the taglibs involved and the associated conditions
Nathan Wilhelmi a écrit :
> Hello - We are using Tomcat 6.0.14, we have some pages that use some 
> nested tags, such as Page A -> Tag A -> Tab B, it's not reclusive 
> problem. We are using the JSP.tag files for this. The problem is on 
> the first request, Page A -> Tag A works fine, however Tag B never 
> appears to be rendered. Now on the second request Page A -> Tag A -> 
> Tab B is all properly executed. Is this a know issue, are there any 
> workarounds, are we doing something that isn't supported/allowed?
>
> Thanks!
>
> -Nate
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org