Skip to main content

Runner Extension Mechanism

Introduction​

Runner mechanism is similar to Spring CommandLineRunner startup hooks. After logic server starts, framework invokes Runner implementations once, so developers can extend their systems by implementing Runner.

This mechanism triggers once before logic-server connection is established and once after:

  1. onStart: called before logic-server connection is established.
  2. onStartAfter: called after logic-server connection is established.

example​

  • code 4: add Runner implementation class MyOperationConfigRunner.
  • code 6~16: add Runner.
public class DemoLogicServer implements LogicServer {
    @Override
    public void settingBarSkeletonBuilder(BarSkeletonBuilder builder) {
        builder.addRunner(new MyOperationConfigRunner());

        builder.addRunner(new Runner() {
            @Override
            public void onStart(BarSkeleton skeleton) {
                // YourBizCode
            }

            @Override
            public void onStartAfter(BarSkeleton skeleton) {
                // YourBizCode
            }
        });
    }
}

public class MyOperationConfigRunner implements Runner {
    @Override
    public void onStart(BarSkeleton skeleton) {
        // YourBizCode
    }
}

Summary​

Runner mechanism can both extend existing module capabilities in Runner form, and provide configuration-related capabilities to avoid scattered configuration.