Re: specific : WARNING

2019-11-15 Thread Lukasz Lenart
pt., 15 lis 2019 o 21:31 zahis Rahman napisał(a): > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.opensymphony.xwork2.util.AbstractLocalizedTextProvider > (file:/C:/Users/zahid/.m2/repository/org/apache/struts/struts2- > core/2.5.20/st

REFLECTION WARNING :SOLVED

2019-11-15 Thread zahis Rahman
Hi, I changed the jvm from jdk 13 to jdk 8. The run time error has disappeared. [INFO] --- jetty-maven-plugin:9.4.22.v20191022:run (default-cli) @ allapps --- [INFO] Logging initialized @7595ms to org.eclipse.jetty.util.log.Slf4jLog [INFO] webAppSourceDirectory not set. Trying src\main\webapp [I

specific : WARNING

2019-11-15 Thread zahis Rahman
Hi, I googled for this warning. There are similar results, but not for this particular warning. I would like to get rid of it as this is the only warning left. [INFO] --- jetty-maven-plugin:9.4.22.v20191022:run (default-cli) @ allapps --- [INFO] Logging initialized @1895ms to org.eclipse.jetty.u

RE: WEIRD Constraint

2019-11-15 Thread zahis Rahman
I wanted to write the code as follows , but that was giving me an error. I think you are suggesting it is by design. HelloWorld /example Sent from Mail for Windows 10 From: Dave Newton Sent: 15 November 2019 19:16 To: Struts Users Mailing List Subject: Re: WEIR

Re: WEIRD Constraint

2019-11-15 Thread Dave Newton
I’m not sure what you mean. The dtd defines the ordering of xml elements in the config file. On Fri, Nov 15, 2019 at 14:12 zahis Rahman wrote: > Hi, > > The constraint I have labelled as “WEIRD CONSTRAINT” in the file > struts.xml below , > is that by design ? > > > "-//Apache Software

WEIRD Constraint

2019-11-15 Thread zahis Rahman
Hi, The constraint I have labelled as “WEIRD CONSTRAINT” in the file struts.xml below , is that by design ? http://struts.apache.org/dtds/struts-2.5.dtd";> /WEB-INF/jsp/error.jsp

Re: s:property #attr working in header.jsp but not HTTP 404.jsp

2019-11-15 Thread Lukasz Lenart
pt., 15 lis 2019 o 16:06 albert kao napisał(a): > > How to fix it? > I like to use a variable instead of hard coding like this: > "> It isn't about JavaScript, but how do you redirect/forward to such JSP page? You should define a global action `404.action` and use it instead of the JSP Regards

Re: s:property #attr working in header.jsp but not HTTP 404.jsp

2019-11-15 Thread albert kao
How to fix it? I like to use a variable instead of hard coding like this: "> On Fri, Nov 15, 2019 at 8:24 AM Lukasz Lenart wrote: > pt., 15 lis 2019 o 14:13 albert kao napisał(a): > > but displays an empty string > > in http404.jsp ("Page Not Found"): > >"> > > How do you access the http404

Re: s:property #attr working in header.jsp but not HTTP 404.jsp

2019-11-15 Thread Lukasz Lenart
pt., 15 lis 2019 o 14:13 albert kao napisał(a): > but displays an empty string > in http404.jsp ("Page Not Found"): >"> How do you access the http404.jsp? Directly, out of action? If so, there is no context that's why #attr doesn't work Regards -- Łukasz + 48 606 323 122 http://www.lenart.

s:property #attr working in header.jsp but not HTTP 404.jsp

2019-11-15 Thread albert kao
This line displays the proper value "> in header.jsp: "> but displays an empty string in http404.jsp ("Page Not Found"): "> Please help. Thanks.