From 30d30e07dee736243b035eb47be4a1c8dae469a2 Mon Sep 17 00:00:00 2001 From: Lukasz Lenart Date: Sun, 11 Oct 2015 18:54:15 +0200 Subject: [PATCH] WW-4536 Checks for patterns in action names to build the same key for actions with patterns --- .../xwork2/validator/AnnotationActionValidatorManager.java | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/xwork-core/src/main/java/com/opensymphony/xwork2/validator/AnnotationActionValidatorManager.java b/xwork-core/src/main/java/com/opensymphony/xwork2/validator/AnnotationActionValidatorManager.java index 5192e2a25..3eceaed9f 100644 --- a/xwork-core/src/main/java/com/opensymphony/xwork2/validator/AnnotationActionValidatorManager.java +++ b/xwork-core/src/main/java/com/opensymphony/xwork2/validator/AnnotationActionValidatorManager.java @@ -28,7 +28,6 @@ import com.opensymphony.xwork2.util.ClassLoaderUtil; import com.opensymphony.xwork2.util.ValueStack; import com.opensymphony.xwork2.util.logging.Logger; import com.opensymphony.xwork2.util.logging.LoggerFactory; -import com.opensymphony.xwork2.validator.validators.VisitorFieldValidator; import org.apache.commons.lang3.StringUtils; import java.io.IOException; @@ -253,8 +252,12 @@ public class AnnotationActionValidatorManager implements ActionValidatorManager // wild card actions to keep the flexibility provided // by the original design (such as mapping different contexts // to the same action and method if desired) + + // UPDATE: + // WW-4536 Using NameVariablePatternMatcher allows defines actions + // with patterns enclosed with '{}', it's similar case to WW-3753 String configName = config.getName(); - if (configName.contains(ActionConfig.WILDCARD)) { + if (configName.contains(ActionConfig.WILDCARD) || (configName.contains("{") && configName.contains("}"))) { sb.append(configName); sb.append("|"); sb.append(proxy.getMethod());