...
@Configured Element | Type | |
---|---|---|
property | String, required | The configuration property name. |
required | boolean, optional | Flag indicating whether the property is required or not. Default: false |
defaultValue | String, optional | The default value of the property. Default: "<null>" |
description | String, optional | A description of the property. Default: "<null>" |
@AppIntrospectionPoints
Any @Configured annotated field or method in the main application class will be discovered by the Talon XVM. If additional classes in your application contain configured fields or methods, they can be exposed to the server using the @AppIntrospectionPoints annotation or @AppConfiguredAccessor annotation. The AppIntrospectionPoints annotation exposes a collection of application objects to introspect for any type of annotation supported by Talon while the AppConfiguredAccessor exposes a set of objects that should only be introspected for @Configured annotations. One can use the more narrowly scoped AppConfiguredAccessor annotation for applications that have a large number of objects to reduce the number of objects that the XVM needs to scan.
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
@AppHAPolicy(HAPolicy.EventSourcing)
public static class MyApp {
MyOtherClass someOtherClass = new MyOtherClass();
@AppIntrospectionPoints
public void getApplicationObjects(Set<Object> object) {
containers.add(someOtherClass );
}
}
private static class MyOtherClass {
@Configured(property = "simulator.ems.orderPreallocateCount", defaultValue = "1048576")
private int orderPreallocateCount;
MyOtherClass() {
}
} |
@AppConfiguredAccessor
Any @Configured annotated field or method in the main application class will be discovered by the Talon server. If additional classes in your application contain configured fields or methods, they can be exposed to the server using the @AppConfiguredAccessor annotation.
...