Return-Path: X-Original-To: apmail-struts-issues-archive@minotaur.apache.org Delivered-To: apmail-struts-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37E26F514 for ; Fri, 5 Jul 2013 14:28:28 +0000 (UTC) Received: (qmail 20628 invoked by uid 500); 5 Jul 2013 14:28:27 -0000 Delivered-To: apmail-struts-issues-archive@struts.apache.org Received: (qmail 20587 invoked by uid 500); 5 Jul 2013 14:28:27 -0000 Mailing-List: contact issues-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list issues@struts.apache.org Received: (qmail 20553 invoked by uid 99); 5 Jul 2013 14:28:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 14:28:27 +0000 Date: Fri, 5 Jul 2013 14:28:27 +0000 (UTC) From: "Nathan.Comstock@wellsfargo.com (JIRA)" To: issues@struts.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (WW-4131) RestActionProxyFactory is handling all requests with PrefixBasedActionMapper MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WW-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700795#comment-13700795 ] Nathan.Comstock@wellsfargo.com commented on WW-4131: ---------------------------------------------------- I will be out of the office until July 5th On Jul 5, 2013, at 7:24 AM, "Nathan.Comstock@wellsfargo.com (JIRA)" wrote: [ https://issues.apache.org/jira/browse/WW-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700738#comment-13700738 ] Nathan.Comstock@wellsfargo.com commented on WW-4131: ---------------------------------------------------- I will be out of the office until July 5th On Jul 5, 2013, at 7:16 AM, "Nathan.Comstock@wellsfargo.com (JIRA)" wrote: [ https://issues.apache.org/jira/browse/WW-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700694#comment-13700694 ] Nathan.Comstock@wellsfargo.com commented on WW-4131: ---------------------------------------------------- I will be out of the office until July 5th On Jun 28, 2013, at 2:47 AM, "Lukasz Lenart (JIRA)" wrote: [ https://issues.apache.org/jira/browse/WW-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart updated WW-4131: ------------------------------ Fix Version/s: 2.3.16 RestActionProxyFactory is handling all requests with PrefixBasedActionMapper ---------------------------------------------------------------------------- Key: WW-4131 URL: https://issues.apache.org/jira/browse/WW-4131 Project: Struts 2 Issue Type: Bug Components: Plugin - REST Affects Versions: 2.3.12, 2.3.14, 2.3.15 Reporter: Felipe Lorenz Priority: Minor Fix For: 2.3.16 Using the following configuration: {noformat} {noformat} Is expected that when I request the following url http://xxxxxxxx.com/ajax/anyThingHere, struts action proxy should handle this call. But instead, RestActionProxyFactory is handling this call. But the RestActionProxyFactory class has a if, and every time the namespace attribute is injected with "/ajax" value. So the condition always is redirected to the rest plugin handler and not to the struts default. Here is my ActionProxyFactory implementation: {noformat} public class CustomActionProxyFactory extends RestActionProxyFactory { @Override public ActionProxy createActionProxy(String namespace, String actionName, String methodName, Map extraContext, boolean executeResult, boolean cleanupContext) { RestActionProxyFactory p = new RestActionProxyFactory(); p.setContainer(container); if ("/ajax".equals(namespace)) { p.setNamespace("/idealogic"); } return p.createActionProxy(namespace, actionName, methodName, extraContext, executeResult, cleanupContext); } } {noformat} By some reason, it fixed the origin behaviour. The begin of this issue was that tag was rendering the action result, even with executeResult = false, which is the default value. Another observation was that, changing the flush attribute value, the result is rendered in different parts of the html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira RestActionProxyFactory is handling all requests with PrefixBasedActionMapper ---------------------------------------------------------------------------- Key: WW-4131 URL: https://issues.apache.org/jira/browse/WW-4131 Project: Struts 2 Issue Type: Bug Components: Plugin - REST Affects Versions: 2.3.12, 2.3.14, 2.3.15 Reporter: Felipe Lorenz Priority: Minor Fix For: 2.3.16 Using the following configuration: {noformat} {noformat} Is expected that when I request the following url http://xxxxxxxx.com/ajax/anyThingHere, struts action proxy should handle this call. But instead, RestActionProxyFactory is handling this call. But the RestActionProxyFactory class has a if, and every time the namespace attribute is injected with "/ajax" value. So the condition always is redirected to the rest plugin handler and not to the struts default. Here is my ActionProxyFactory implementation: {noformat} public class CustomActionProxyFactory extends RestActionProxyFactory { @Override public ActionProxy createActionProxy(String namespace, String actionName, String methodName, Map extraContext, boolean executeResult, boolean cleanupContext) { RestActionProxyFactory p = new RestActionProxyFactory(); p.setContainer(container); if ("/ajax".equals(namespace)) { p.setNamespace("/idealogic"); } return p.createActionProxy(namespace, actionName, methodName, extraContext, executeResult, cleanupContext); } } {noformat} By some reason, it fixed the origin behaviour. The begin of this issue was that tag was rendering the action result, even with executeResult = false, which is the default value. Another observation was that, changing the flush attribute value, the result is rendered in different parts of the html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira RestActionProxyFactory is handling all requests with PrefixBasedActionMapper ---------------------------------------------------------------------------- Key: WW-4131 URL: https://issues.apache.org/jira/browse/WW-4131 Project: Struts 2 Issue Type: Bug Components: Plugin - REST Affects Versions: 2.3.12, 2.3.14, 2.3.15 Reporter: Felipe Lorenz Priority: Minor Fix For: 2.3.16 Using the following configuration: {noformat} {noformat} Is expected that when I request the following url http://xxxxxxxx.com/ajax/anyThingHere, struts action proxy should handle this call. But instead, RestActionProxyFactory is handling this call. But the RestActionProxyFactory class has a if, and every time the namespace attribute is injected with "/ajax" value. So the condition always is redirected to the rest plugin handler and not to the struts default. Here is my ActionProxyFactory implementation: {noformat} public class CustomActionProxyFactory extends RestActionProxyFactory { @Override public ActionProxy createActionProxy(String namespace, String actionName, String methodName, Map extraContext, boolean executeResult, boolean cleanupContext) { RestActionProxyFactory p = new RestActionProxyFactory(); p.setContainer(container); if ("/ajax".equals(namespace)) { p.setNamespace("/idealogic"); } return p.createActionProxy(namespace, actionName, methodName, extraContext, executeResult, cleanupContext); } } {noformat} By some reason, it fixed the origin behaviour. The begin of this issue was that tag was rendering the action result, even with executeResult = false, which is the default value. Another observation was that, changing the flush attribute value, the result is rendered in different parts of the html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira > RestActionProxyFactory is handling all requests with PrefixBasedActionMapper > ---------------------------------------------------------------------------- > > Key: WW-4131 > URL: https://issues.apache.org/jira/browse/WW-4131 > Project: Struts 2 > Issue Type: Bug > Components: Plugin - REST > Affects Versions: 2.3.12, 2.3.14, 2.3.15 > Reporter: Felipe Lorenz > Priority: Minor > Fix For: 2.3.16 > > > Using the following configuration: > {noformat} > > > {noformat} > Is expected that when I request the following url http://xxxxxxxx.com/ajax/anyThingHere, struts action proxy should handle this call. But instead, RestActionProxyFactory is handling this call. > But the RestActionProxyFactory class has a if, and every time the namespace attribute is injected with "/ajax" value. So the condition always is redirected to the rest plugin handler and not to the struts default. > Here is my ActionProxyFactory implementation: > {noformat} > public class CustomActionProxyFactory extends RestActionProxyFactory { > @Override > public ActionProxy createActionProxy(String namespace, String actionName, String methodName, Map extraContext, boolean executeResult, boolean cleanupContext) { > RestActionProxyFactory p = new RestActionProxyFactory(); > p.setContainer(container); > if ("/ajax".equals(namespace)) { > p.setNamespace("/idealogic"); > } > return p.createActionProxy(namespace, actionName, methodName, extraContext, executeResult, cleanupContext); > } > } > {noformat} > By some reason, it fixed the origin behaviour. > The begin of this issue was that tag was rendering the action result, even with executeResult = false, which is the default value. > Another observation was that, changing the flush attribute value, the result is rendered in different parts of the html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira