Class InAim

  • All Implemented Interfaces:
    JtAim

    public class InAim
    extends Object
    implements JtAim
    The handler chain contains 4 rules in sequence, it's for complex routing design ------ 1. 「Optional」This rule will execute IN_RULE for validation, there should be some components that could be defined, now it support VALIDATOR / CONVERTER instead. These components will provide response message to client and it will process in priority such as 400 bad request / 400 parameter required exception here. ------ 2. 「Optional」The second step to execute IN_MAPPING, it's for field mapping and the first time convert the field data in request. The output will be input data that will be used in next step. ------ 3. 「Optional」It's defined by java code ( IN_PLUG ) and reflect to generate to plug-in ------ 4. 「Optional」The last step is executing JS Engine ( JavaScript, IN_SCRIPT ), the javascript could call following service component, also it's dynamic to define different code-logical and business requirement. Here it's easy to expand. It's more smart. ------ The final execution sequence is as following: IN_RULE -> IN_MAPPING -> IN_PLUG -> IN_SCRIPT
    • Constructor Detail

      • InAim

        public InAim()
    • Method Detail

      • attack

        public io.vertx.core.Handler<io.vertx.ext.web.RoutingContext> attack​(JtUri uri)
        Specified by:
        attack in interface JtAim