Gaderian
  1. Gaderian
  2. GAD-2

Incorrect behaviour when both <rules/> and <conversion/> are specified

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      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).

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Raffael Herzog
            Reporter:
            Raffael Herzog
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development