Incorrect behaviour when both <rules/> and <conversion/> are specified
----------------------------------------------------------------------
Key: GAD-2
URL: http://issues.ops4j.org/browse/GAD-2
Project: Gaderian
Issue Type: Bug
Components: Core
Reporter: Raffael Herzog
Assignee: Raffael Herzog
Priority: Minor
When both {{<rules/>}} and {{<conversion/>}} are specified in a contribution
schema, Gaderian won't report any error message. It looks like it'll put the
class from <conversion/> on top of the stack and then execute the rules, which,
in the end, results in a {{NoSuchMethodException: addElement}} at
{{org.apache.hivemind.schema.rules.InvokeParentRule.findMethod(InvokeParentRule.java:127)}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general