Probably ask the user list for this.
But, #user.name as it won't be searching the stack for the property.
On 19/02/2025 09:00, Murali Challa wrote:
Hi,
Can someone suggest among below which is best/preferred way of using
tag with in .
//getting value using var.name
// getting valu
Hello,
When using the tag in a JSP with the Struts tags library,
the included page does not appear. The following error is displayed:
Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:610)
~[jasper.jar:9.0.71]
at
org.apache.jasper.servlet.Jsp
Could you share the full stacktrace, including the exception thrown
and caused by hierarchy?
On Wed, Feb 19, 2025 at 9:14 PM 戸田 栞太（HARP） wrote:
>
> Hello,
>
> When using the tag in a JSP with the Struts tags
> library,
> the included page does not appear. The following error is displayed:
>
> S
I used a simple hierarchical structure.
Below is the JSP code:
``` sample.jsp
<%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%><%--
--%><%@ taglib prefix="s" uri="/struts-tags" %><%--
--%>http://www.w3.org/TR/html4/loose.dtd";><%--
--%><%@ taglib uri="http://
Thanks for sharing the full stacktrace.
So the relevant error here is: java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
This is a bytecode error which occurs when a library targeting JRE8 is
compiled with a JDK greater than 8 but without the '--release 8'
option.
I've
Great, I'm going to prepare a new test build then.
czw., 20 lut 2025 o 08:00 Kusal Kithul-Godage
napisał(a):
>
> No worries! Now that we have the 'release' option defined in the POM
> you should be able to continue using JDK17 but of course you can play
> it safe by just using JDK8
>
> On Thu, Fe
Thanks a lot Kusal for finding the issue and the fix! I started using
JDK17 as a default JDK on my computer and missed that :( Re-installed
JDK8 and should be fine now :)
czw., 20 lut 2025 o 06:30 Kusal Kithul-Godage
napisał(a):
>
> Thanks for sharing the full stacktrace.
>
> So the relevant erro
No worries! Now that we have the 'release' option defined in the POM
you should be able to continue using JDK17 but of course you can play
it safe by just using JDK8
On Thu, Feb 20, 2025 at 5:56 PM Łukasz Lenart wrote:
>
> Thanks a lot Kusal for finding the issue and the fix! I started using
> JD
