public class SetNextRule extends Rule
Rule implementation that calls a method on the (top-1) (parent) object, passing the top object (child) as an argument. It is commonly used to establish parent-child relationships.
This rule now supports more flexible method matching by default.
It is possible that this may break (some) code
written against release 1.1.1 or earlier.
See isExactMatch()
for more details.
Modifier and Type | Field and Description |
---|---|
protected String |
methodName
The method name to call on the parent object.
|
protected String |
paramType
The Java class name of the parameter type expected by the method.
|
protected boolean |
useExactMatch
Should we use exact matching.
|
digester, namespaceURI
Constructor and Description |
---|
SetNextRule(String methodName,
String paramType)
Construct a "set next" rule with the specified method name.
|
Modifier and Type | Method and Description |
---|---|
void |
end(String namespace,
String name)
Process the end of this element.
|
boolean |
isExactMatch()
Is exact matching being used.
|
void |
setExactMatch(boolean useExactMatch)
Set whether exact matching is enabled.
|
String |
toString()
Render a printable version of this Rule.
|
begin, body, finish, getDigester, getNamespaceURI, setDigester, setNamespaceURI
protected String methodName
protected String paramType
protected boolean useExactMatch
public SetNextRule(String methodName, String paramType)
methodName
- Method name of the parent method to callparamType
- Java class of the parent method's argument
(if you wish to use a primitive type, specify the corresponding
Java wrapper class instead, such as java.lang.Boolean
for a boolean
parameter)public boolean isExactMatch()
Is exact matching being used.
This rule uses org.apache.commons.beanutils.MethodUtils
to introspect the relevant objects so that the right method can be called.
Originally, MethodUtils.invokeExactMethod
was used.
This matches methods very strictly
and so may not find a matching method when one exists.
This is still the behaviour when exact matching is enabled.
When exact matching is disabled, MethodUtils.invokeMethod
is used.
This method finds more methods but is less precise when there are several methods
with correct signatures.
So, if you want to choose an exact signature you might need to enable this property.
The default setting is to disable exact matches.
public void setExactMatch(boolean useExactMatch)
Set whether exact matching is enabled.
See isExactMatch()
.
useExactMatch
- should this rule use exact method matchingpublic void end(String namespace, String name) throws Exception
end
in class Rule
namespace
- the namespace URI of the matching element, or an
empty string if the parser is not namespace aware or the element has
no namespacename
- the local name if the parser is namespace aware, or just
the element name otherwiseException
- if an error occurs while processing the eventCopyright © 2000-2016 Apache Software Foundation. All Rights Reserved.