Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
On 9/10/2022 9:27 AM, wwyyzz_001 wrote: "login" action is defined in default namespase."success" result is defined inglobal-results,result type is json. Where in which package you've defined the global-results? Could you share please its definition? Have you extended strus-default? Invokehttp://localhost:8080/wisdomcampus-gs/user/login is ok in Struts2.3.34. But it is not ok in Structs 2.5.30,Structs throw exception(Could not find action or result) in DefaultActionInvocation.executeResult(DefaultActionInvocation.java:377) Error log is : 2022-09-09 18:32:16 [http-nio-8080-exec-1] DEBUG SecurityMemberAccess:67 - Checking access for [target: wisdom.user.action.LoginAction@3fd415d2, member: public final java.lang.String wisdom.common.JsonActionBase.execute() throws java.lang.Exception, property: null] 2022-09-09 18:32:16 [http-nio-8080-exec-1] DEBUG InstantiatingNullHandler:98 - Entering nullPropertyValue [target=[wisdom.user.action.LoginAction@3fd415d2, com. opensymphony.xwork2.DefaultTextProvider@e405047], property=locale] 2022-09-09 18:32:16 [http-nio-8080-exec-1] DEBUG I18nInterceptor:124 - After action invocation Locale=null 2022-09-09 18:32:16 [http-nio-8080-exec-1] WARN Dispatcher:613 - Could not find action or result: /wisdomcampus-gs/login com.opensymphony.xwork2.config.ConfigurationException: No result defined for action wisdom.user.action.LoginAction and result success This log line shows that the action is successfully resolved, but for some reason Struts cannot find global result 'success' for it. Are you sure that you've defined 'success' as a global result? TBH it's a bit strange I think to define 'success' as global result. Could you please explicitly define a result 'success' for that action specifically? just to see if problem is with global-results. Regards - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
pon., 12 wrz 2022 o 07:30 wwyyzz_001 <517654...@qq.com.invalid> napisał(a): > > No,I used struts.convention.action.mapallmatches because some people say that > with this configuration can solve problem.But it doesn't work. Ok, so you don't use the Convention plugin - just enabling an option without proper JARs won't work. > My original struts.xml file (see attachment). Attachment are not accepted in this mailing list. Could you setup "" in the default namespace? ... Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
No,I used struts.convention.action.mapallmatches because some people say that with this configuration can solve problem.But it doesn't work. My original struts.xml file (see attachment). Regards Mark Wang ---- ??: "Struts Users Mailing List" https://struts.apache.org/plugins/convention/ Regards -- ?0?9ukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
niedz., 11 wrz 2022 o 12:51 wwyyzz_001 <517654...@qq.com.invalid> napisał(a): > > Also do you use the Convention plugin? > Yes,I have defined the following in xwork-conversion.properties: > wisdom.common.DataTablesInput=wisdom.common.DataTablesConvert I was asking about the Convention plugin not conversion, I noticed that you have such setting in struts.xml: struts.convention.action.mapallmatches that's why I asked about the Convention plugin, do you use it? https://struts.apache.org/plugins/convention/ Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
Have you tried to use earlier version of 2.5 and then switch version by version? No,I'll try it later. Also do you use the Convention plugin? Yes,I have defined the followinginxwork-conversion.properties: wisdom.common.DataTablesInput=wisdom.common.DataTablesConvert See attachment for source code. Regards Mark Wang ---- ??: "Struts Users Mailing List" http://www.lenart.org.pl/ - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
Could you answer my questions first? > Have you tried to use earlier version of 2.5 and then switch version by > version? > Also do you use the Convention plugin? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
> org.apache.struts2.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:121) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.struts2.interceptor.ServletConfigInterceptor.intercept(ServletConfigInterceptor.java:167) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.interceptor.AliasInterceptor.intercept(AliasInterceptor.java:228) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:196) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.struts2.factory.StrutsActionProxy.execute(StrutsActionProxy.java:48) > > ~[struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:574) > > [struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.struts2.dispatcher.ExecuteOperations.executeAction(ExecuteOperations.java:79) > > [struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.struts2.dispatcher.filter.StrutsPrepareAndExecuteFilter.doFilter(StrutsPrepareAndExecuteFilter.java:141) > > [struts2-core-2.5.30.jar:2.5.30] > > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.filters.ExpiresFilter.doFilter(ExpiresFilter.java:1230) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:544) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) > > [catalina.jar:8.5.61] > > at > > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) > > [catalina.jar:8.5.61] > > at > > org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:616) > > [tomcat-coyote.jar:8.5.61] > > at > > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) > > [tomcat-coyote.jar:8.5.61] > > at > > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831) > > [tomcat-coyote.jar:8.5.61] > > at > > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1634) > > [tomcat-coyote.jar:8.5.61] > > at > > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) > > [tomcat-coyote.jar:8.5.61] > > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > [?:1.8.0_181] > > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > [?:1.8.0_181] > > at > > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > > [tomcat-util
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249) > ~[struts2-core-2.5.30.jar:2.5.30] > at > org.apache.struts2.factory.StrutsActionProxy.execute(StrutsActionProxy.java:48) > ~[struts2-core-2.5.30.jar:2.5.30] > at > org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:574) > [struts2-core-2.5.30.jar:2.5.30] > at > org.apache.struts2.dispatcher.ExecuteOperations.executeAction(ExecuteOperations.java:79) > [struts2-core-2.5.30.jar:2.5.30] > at > org.apache.struts2.dispatcher.filter.StrutsPrepareAndExecuteFilter.doFilter(StrutsPrepareAndExecuteFilter.java:141) > [struts2-core-2.5.30.jar:2.5.30] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > [catalina.jar:8.5.61] > at > org.apache.catalina.filters.ExpiresFilter.doFilter(ExpiresFilter.java:1230) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) > [catalina.jar:8.5.61] > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:544) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) > [catalina.jar:8.5.61] > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) > [catalina.jar:8.5.61] > at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) > [catalina.jar:8.5.61] > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) > [catalina.jar:8.5.61] > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) > [catalina.jar:8.5.61] > at > org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:616) > [tomcat-coyote.jar:8.5.61] > at > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) > [tomcat-coyote.jar:8.5.61] > at > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831) > [tomcat-coyote.jar:8.5.61] > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1634) > [tomcat-coyote.jar:8.5.61] > at > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) > [tomcat-coyote.jar:8.5.61] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:1.8.0_181] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:1.8.0_181] > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > [tomcat-util.jar:8.5.61] > at java.lang.Thread.run(Thread.java:748) > [?:1.8.0_181] > > --原始邮件-- > 发件人: > "Struts Users Mailing List" > > 发送时间:2022年9月9日(星期五) 中午1:41 > 收件人:"Struts Users Mailing List" > 主题:Re: When Struct 2.3.34 update Struct 2.5.30,the original interface > cannot be accessed > > > > As far I see you have defined "/login" action under default namespace > "/" and you don't have namespace called "/user" - which means is > working according to the config. > > https://issues.apache.org/jira/secure/attachment/13049087/struts.xml > https://issues.apache.org/jira/browse/WW-5222 > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > pt., 9 wrz 2022 o 04:06 wwyyzz_001 <517654...@qq.com.invalid napisał(a): > > Dear all: > > Use Struct 2.3.34,one interface can invoke by two ways,example: > > http://localhost:8080/wisdomcampus-gs/loginnbsp; can invoke, the > interface can also be called under the subdirectory, > > http://localhost:8080/wisdomcampus-gs/user/loginnbsp;can > invoke,result is same. > > Use Struct 2.5.30,one interface only invoke by one way, example: > > http://localhost:8080/wisdomcampus-gs/loginnbsp; can invoke, the > interface can'tnbsp; be called under the subdirectory, > > http://localhost:8080/wisdomcampus-gs/user/loginnbsp;can't > nbsp;invoke, return error: No result defined for action > wisdom.user.action.LoginAction and result success. > > > > > Why? How to config in Struct 2.5.30, can realization same > resultnbsp; in Struct 2.3.34?nbsp; nbsp; > > Look forward to your reply,nbsp; nbsp;thank you! > > > > > Mark wang > > - > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: When Struct 2.3.34 update Struct 2.5.30,the original interface cannot be accessed
As far I see you have defined "/login" action under default namespace "/" and you don't have namespace called "/user" - which means is working according to the config. https://issues.apache.org/jira/secure/attachment/13049087/struts.xml https://issues.apache.org/jira/browse/WW-5222 Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ pt., 9 wrz 2022 o 04:06 wwyyzz_001 <517654...@qq.com.invalid> napisał(a): > > Dear all: > > Use Struct 2.3.34,one interface can invoke by two ways,example: > > http://localhost:8080/wisdomcampus-gs/login; can invoke, the interface > can also be called under the subdirectory, > > http://localhost:8080/wisdomcampus-gs/user/logincan invoke,result is > same. > > Use Struct 2.5.30,one interface only invoke by one way, example: > > http://localhost:8080/wisdomcampus-gs/login; can invoke, the interface > can't be called under the subdirectory, > > http://localhost:8080/wisdomcampus-gs/user/logincan't invoke, > return error: No result defined for action wisdom.user.action.LoginAction and > result success. > > > > > Why? How to config in Struct 2.5.30, can realization same result in > Struct 2.3.34? > > Look forward to your reply, thank you! > > > > > Mark wang - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
