śr., 29 sty 2025 o 08:46 Murali Challa <challamura...@gmail.com> napisał(a):

> Yes, this is what we are using in our application code. Same code we have
> mentioned at beginning of this mailing.
>
> Just to keep it clear, our code looks as below.
>
> Action Class (extends ActionSupport):
>
> HttpSession session = ServletActionContext.getRequest().getSession(false);
>
> session.setAttribute("menuList", objList);
>
> Jsp:
>
> <s:iterator value="#session.menuList" var="menu" status="s">
> ${menu.funcName}
> </s:iterator>

And this doesn't work, yes?

I was playing with showcase-app (on 6.7.x branch) and modified it like this:

<s:iterator value="#session.items" var="item" status="s">
<tr>
<td><a href="<s:url action="edit-%{empId}" />"><s:property
value="empId"/></a></td>
<td>${s.index} ${item.empId}</td>
<td><s:property value="firstName"/></td>
<td><s:property value="lastName"/></td>
</tr>
</s:iterator>

And action code:
ServletActionContext.getRequest().getSession(true).setAttribute("items",
availableItems);

I had to use "true" as the session didn't exist. All works without an issue.

Maybe try to increase the log level and observe what the framework reports?


Cheers
Łukasz

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Reply via email to