IT. Expert System.

Java Standard Edition (SE)


Package javax.lang.model.element

Interfaces used to model elements of the Java programming language.

See: Description

  • Interface Summary 
    Interface Description
    Represents an annotation.
    Represents a value of an annotation type element.
    A visitor of the values of annotation type elements, using a variant of the visitor design pattern.
    Represents a program element such as a package, class, or method.
    A visitor of program elements, in the style of the visitor design pattern.
    Represents a method, constructor, or initializer (static or instance) of a class or interface, including annotation type elements.
    An immutable sequence of characters.
    Represents a package program element.
    A mixin interface for an element that has type parameters.
    A mixin interface for an element that has a qualified name.
    Represents a class or interface program element.
    Represents a formal type parameter of a generic class, interface, method, or constructor element.
    Represents a field, enum constant, method or constructor parameter, local variable, resource variable, or exception parameter.
  • Enum Summary 
    Enum Description
    The kind of an element.
    Represents a modifier on a program element such as a class, method, or field.
    The nesting kind of a type element.
  • Exception Summary 
    Exception Description
    Indicates that an unknown kind of annotation value was encountered.
    Indicates that an unknown kind of element was encountered.

Package javax.lang.model.element Description

Interfaces used to model elements of the Java programming language. The term "element" in this package is used to refer to program elements, the declared entities that make up a program. Elements include classes, interfaces, methods, constructors, and fields. The interfaces in this package do not model the structure of a program inside a method body; for example there is no representation of a for loop or try-finally block. However, the interfaces can model some structures only appearing inside method bodies, such as local variables and anonymous classes.

When used in the context of annotation processing, an accurate model of the element being represented must be returned. As this is a language model, the source code provides the fiducial (reference) representation of the construct in question rather than a representation in an executable output like a class file. Executable output may serve as the basis for creating a modeling element. However, the process of translating source code to executable output may not permit recovering some aspects of the source code representation. For example, annotations with source retention cannot be recovered from class files and class files might not be able to provide source position information. Names of parameters may not be recoverable from class files. The modifiers on an element may differ in some cases including:

  • strictfp on a class or interface
  • final on a parameter
  • protected, private, and static on classes and interfaces
Additionally, synthetic constructs in a class file, such as accessor methods used in implementing nested classes and bridge methods used in implementing covariant returns, are translation artifacts outside of this model.

During annotation processing, operating on incomplete or erroneous programs is necessary; however, there are fewer guarantees about the nature of the resulting model. If the source code is not syntactically well-formed or has some other irrecoverable error that could not be removed by the generation of new types, a model may or may not be provided as a quality of implementation issue. If a program is syntactically valid but erroneous in some other fashion, any returned model must have no less information than if all the method bodies in the program were replaced by "throw new RuntimeException();". If a program refers to a missing type XYZ, the returned model must contain no less information than if the declaration of type XYZ were assumed to be "class XYZ {}", "interface XYZ {}", "enum XYZ {}", or "@interface XYZ {}". If a program refers to a missing type XYZ<K1, ... ,Kn>, the returned model must contain no less information than if the declaration of XYZ were assumed to be "class XYZ<T1, ... ,Tn> {}" or "interface XYZ<T1, ... ,Tn> {}"

Unless otherwise specified in a particular implementation, the collections returned by methods in this package should be expected to be unmodifiable by the caller and unsafe for concurrent access.

Unless otherwise specified, methods in this package will throw a NullPointerException if given a null argument.



Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)





Java Script








Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 732 / 159178551. Delta: 0.02550 с