Return-Path: 
 <issues-return-21153-apmail-struts-issues-archive=struts.apache.org@struts.apache.org>
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 140F6CA23
	for <apmail-struts-issues-archive@minotaur.apache.org>;
 Mon,  1 Jul 2013 01:43:21 +0000 (UTC)
Received: (qmail 13992 invoked by uid 500); 1 Jul 2013 01:43:20 -0000
Delivered-To: apmail-struts-issues-archive@struts.apache.org
Received: (qmail 13914 invoked by uid 500); 1 Jul 2013 01:43:20 -0000
Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@struts.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@struts.apache.org>
List-Post: <mailto:issues@struts.apache.org>
List-Id: <issues.struts.apache.org>
Reply-To: dev@struts.apache.org
Delivered-To: mailing list issues@struts.apache.org
Received: (qmail 13907 invoked by uid 99); 1 Jul 2013 01:43:20 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 01:43:20 +0000
Date: Mon, 1 Jul 2013 01:43:20 +0000 (UTC)
From: "Felipe Lorenz (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12655213.1372364434719.189942.1372643000087@arcas>
In-Reply-To: <JIRA.12655213.1372364434719@arcas>
References: <JIRA.12655213.1372364434719@arcas>
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=13696440#comment-13696440 ] 

Felipe Lorenz commented on WW-4131:
-----------------------------------

I use to work with 2.3.8, but the pattern of using s:action tag to populate select or list(i.e) is the first time. So I can't say which version this behavior starts.
                
> 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}
> <constant name="struts.mapper.class" value="org.apache.struts2.dispatcher.mapper.PrefixBasedActionMapper"/>
> <constant name="struts.mapper.prefixMapping" value=":rest,/ajax:struts,/login:struts"/>
> {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<String, Object> 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 <s:action> 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