org.safs.model.annotations

Annotation Type AutoConfigureJSAFS

@Target(value=TYPE)
 @Retention(value=RUNTIME)
public @interface AutoConfigureJSAFS

Tags a Class as requiring its package and subpackages to be checked for JSAFS auto injection. Alternatively, you can 'include' and/or 'exclude' a semi-colon delimited list of package names that should be autoconfigured.

Author:

Carl Nagle OCT 15, 2013, Carl Nagle OCT 17, 2013 Documentation updates

See Also:

JSAFSBefore, JSAFSTest, JSAFSAfter, Utilities.autoConfigure(String, JSAFSConfiguredClassStore)

Field Summary

Fields

Modifier and Type	Fields and Description
static int	DEFAULT_ORDER

Optional Element Summary

Optional Elements

Modifier and Type	Optional Element and Description
java.lang.String	exclude Optionally, exclude a semi-colon delimited path of package names to process.
java.lang.String	include Optionally, include a semi-colon delimited list of full Class names existing in other packages to be processed.
int	Order Lower order will be executed before higher order tests.
int	value A default for Order not requiring Order= prefix.

Field Detail

DEFAULT_ORDER

public static final int DEFAULT_ORDER

Element Detail

include

public abstract java.lang.String include

Optionally, include a semi-colon delimited list of full Class names existing in other packages to be processed. Only one Class in a given root package needs to be listed and all Classes in that package and sub-packages will be processed.

Example: com.sas.commons.SomeClass;com.sas.roadmaps.AnotherClass;org.mine.AClass

Note we have to only provide one Class from each unrelated package hierarchy. A processor should automatically process and include sub-packages of included packages.
(The algorithm currently requires Class names here, but we should figure out how to support just providing package names instead.)

Default:

""

exclude

public abstract java.lang.String exclude

Optionally, exclude a semi-colon delimited path of package names to process. The exclusion applies to packages found during the processing of the inclusion list or the default root package and sub-package processing.
(Yes, here we are able to use just package names.)

Default:

""

Order

public abstract int Order

Lower order will be executed before higher order tests. Tests of the same order value are not guaranteed to execute in any specific order and may even be intentionally randomized. The default is 1000.

Returns:

'order' determines in what order tests shall be executed.

Default:

1000

value

public abstract int value

A default for Order not requiring Order= prefix. The default is 1000.

Returns:

'order' determines in what order tests shall be executed.

Default:

1000