This example demonstrates adding dynamic editor components depending on the chosen input type. The simple editor can even change its type after it has been initialized. The inheritance editor demonstrates how you can leverage more complex component hierarchies for dynamic editors. To demonstrate validation settings, the editor fields include validations but the components (implemented by buttons methods and @Eager properties) all have @Forced annotations to disable validations on their requests. You can see the validations in action by using the "Summarize (with validations)" button (which simply lacks the @Forced annotation). In a real life scenario one could implement a complex search form like this.

Editor Fields