Filerpublic interface Filer | This interface supports the creation of new files by an annotation
processor. Files created in this way will be known to the
annotation processing tool implementing this interface, better
enabling the tool to manage them. Source and class files so
created will be considered for processing by the tool after the
{@code close} method has been called on the {@code Writer} or
{@code OutputStream} used to write the contents of the file.
Three kinds of files are distinguished: source files, class files,
and auxiliary resource files.
There are two distinguished supported locations (subtrees
within the logical file system) where newly created files are
placed: one for {@linkplain
javax.tools.StandardLocation#SOURCE_OUTPUT new source files}, and
one for {@linkplain javax.tools.StandardLocation#CLASS_OUTPUT new
class files}. (These might be specified on a tool's command line,
for example, using flags such as {@code -s} and {@code -d}.) The
actual locations for new source files and new class files may or
may not be distinct on a particular run of the tool. Resource
files may be created in either location. The methods for reading
and writing resources take a relative name argument. A relative
name is a non-null, non-empty sequence of path segments separated
by {@code '/'}; {@code '.'} and {@code '..'} are invalid path
segments. A valid relative name must match the
"path-rootless" rule of RFC 3986, section
3.3.
The file creation methods take a variable number of arguments to
allow the originating elements to be provided as hints to
the tool infrastructure to better manage dependencies. The
originating elements are the types or packages (representing {@code
package-info} files) which caused an annotation processor to
attempt to create a new file. For example, if an annotation
processor tries to create a source file, {@code
GeneratedFromUserSource}, in response to processing
@Generate
public class UserSource {}
the type element for {@code UserSource} should be passed as part of
the creation method call as in:
filer.createSourceFile("GeneratedFromUserSource",
eltUtils.getTypeElement("UserSource"));
If there are no originating elements, none need to be passed. This
information may be used in an incremental environment to determine
the need to rerun processors or remove generated files.
Non-incremental environments may ignore the originating element
information.
During each run of an annotation processing tool, a file with a
given pathname may be created only once. If that file already
exists before the first attempt to create it, the old contents will
be deleted. Any subsequent attempt to create the same file during
a run will throw a {@link FilerException}, as will attempting to
create both a class file and source file for the same type name or
same package name. The {@linkplain Processor initial inputs} to
the tool are considered to be created by the zeroth round;
therefore, attempting to create a source or class file
corresponding to one of those inputs will result in a {@link
FilerException}.
In general, processors must not knowingly attempt to overwrite
existing files that were not generated by some processor. A {@code
Filer} may reject attempts to open a file corresponding to an
existing type, like {@code java.lang.Object}. Likewise, the
invoker of the annotation processing tool must not knowingly
configure the tool such that the discovered processors will attempt
to overwrite existing files that were not generated.
Processors can indicate a source or class file is generated by
including an {@link javax.annotation.Generated @Generated}
annotation.
Note that some of the effect of overwriting a file can be
achieved by using a decorator-style pattern. Instead of
modifying a class directly, the class is designed so that either
its superclass is generated by annotation processing or subclasses
of the class are generated by annotation processing. If the
subclasses are generated, the parent class may be designed to use
factories instead of public constructors so that only subclass
instances would be presented to clients of the parent class. |
| Methods Summary |
|---|
| public javax.tools.JavaFileObject | createClassFile(java.lang.CharSequence name, javax.lang.model.element.Element originatingElements)Creates a new class file, and returns an object to allow
writing to it. The file's name and path (relative to the
{@linkplain StandardLocation#CLASS_OUTPUT root output location
for class files}) are based on the name of the type being
written. A class file can also be created to hold information
about a package, including package annotations. To create a
class file for a named package, have {@code name} be the
package's name followed by {@code ".package-info"}; creating a
class file for an unnamed package is not supported.
To avoid subsequent errors, the contents of the class file
should be compatible with the {@linkplain
ProcessingEnvironment#getSourceVersion source version} being used
for this run.
| | public javax.tools.FileObject | createResource(javax.tools.JavaFileManager$Location location, java.lang.CharSequence pkg, java.lang.CharSequence relativeName, javax.lang.model.element.Element originatingElements)Creates a new auxiliary resource file for writing and returns a
file object for it. The file may be located along with the
newly created source files, newly created binary files, or
other supported location. The locations {@link
StandardLocation#CLASS_OUTPUT CLASS_OUTPUT} and {@link
StandardLocation#SOURCE_OUTPUT SOURCE_OUTPUT} must be
supported. The resource may be named relative to some package
(as are source and class files), and from there by a relative
pathname. In a loose sense, the full pathname of the new file
will be the concatenation of {@code location}, {@code pkg}, and
{@code relativeName}.
Files created via this method are not registered for
annotation processing, even if the full pathname of the file
would correspond to the full pathname of a new source file
or new class file.
| | public javax.tools.JavaFileObject | createSourceFile(java.lang.CharSequence name, javax.lang.model.element.Element originatingElements)Creates a new source file and returns an object to allow
writing to it. The file's name and path (relative to the
{@linkplain StandardLocation#SOURCE_OUTPUT root output location
for source files}) are based on the type to be declared in that
file. If more than one type is being declared, the name of the
principal top-level type (the public one, for example) should
be used. A source file can also be created to hold information
about a package, including package annotations. To create a
source file for a named package, have {@code name} be the
package's name followed by {@code ".package-info"}; to create a
source file for an unnamed package, use {@code "package-info"}.
Note that to use a particular {@linkplain
java.nio.charset.Charset charset} to encode the contents of the
file, an {@code OutputStreamWriter} with the chosen charset can
be created from the {@code OutputStream} from the returned
object. If the {@code Writer} from the returned object is
directly used for writing, its charset is determined by the
implementation. An annotation processing tool may have an
{@code -encoding} flag or analogous option for specifying this;
otherwise, it will typically be the platform's default
encoding.
To avoid subsequent errors, the contents of the source file
should be compatible with the {@linkplain
ProcessingEnvironment#getSourceVersion source version} being used
for this run.
| | public javax.tools.FileObject | getResource(javax.tools.JavaFileManager$Location location, java.lang.CharSequence pkg, java.lang.CharSequence relativeName)Returns an object for reading an existing resource. The
locations {@link StandardLocation#CLASS_OUTPUT CLASS_OUTPUT}
and {@link StandardLocation#SOURCE_OUTPUT SOURCE_OUTPUT} must
be supported.
|
|
