public interface ProcessingEnvironmentAn annotation processing tool framework will provide an annotation processor with an object implementing this interface so the processor can use facilities provided by the framework to write new files, report error messages, and find other utilities.
Third parties may wish to provide value-add wrappers around the facility objects from this interface, for example a
Filerextension that allows multiple processors to coordinate writing out a single source file. To enable this, for processors running in a context where their side effects via the API could be visible to each other, the tool infrastructure must provide corresponding facility objects that are
Filers that are
.equals, and so on. In addition, the tool invocation must be able to be configured such that from the perspective of the running annotation processors, at least the chosen subset of helper classes are viewed as being loaded by the same class loader. (Since the facility objects manage shared state, the implementation of a wrapper class must know whether or not the same base facility object has been wrapped before.)
All Methods Instance Methods Abstract Methods Modifier and Type Method Description
getElementUtils()Returns an implementation of some utility methods for operating on elements
getFiler()Returns the filer used to create new source, class, or auxiliary files.
getLocale()Returns the current locale or
nullif no locale is in effect.
getMessager()Returns the messager used to report errors, warnings, and other notices.
getOptions()Returns the processor-specific options passed to the annotation processing tool.
getTypeUtils()Returns an implementation of some utility methods for operating on types.
getOptionsReturns the processor-specific options passed to the annotation processing tool. Options are returned in the form of a map from option name to option value. For an option with no value, the corresponding value in the map is
See documentation of the particular tool infrastructure being used for details on how to pass in processor-specific options. For example, a command-line implementation may distinguish processor-specific options by prefixing them with a known string like
"-A"; other tool implementations may follow different conventions or provide alternative mechanisms. A given implementation may also provide implementation-specific ways of finding options passed to the tool in addition to the processor-specific options.
- the processor-specific options passed to the tool
Messager getMessager()Returns the messager used to report errors, warnings, and other notices.
- the messager
Filer getFiler()Returns the filer used to create new source, class, or auxiliary files.
- the filer
Elements getElementUtils()Returns an implementation of some utility methods for operating on elements
- element utilities
Types getTypeUtils()Returns an implementation of some utility methods for operating on types.
- type utilities
- the source version to which generated source and class files should conform to
- See Also: