Module org.eclipse.persistence.jpa.jpql
Package org.eclipse.persistence.jpa.jpql.parser

Class AbstractExpressionVisitor

java.lang.Object
org.eclipse.persistence.jpa.jpql.parser.AbstractExpressionVisitor
All Implemented Interfaces:
ExpressionVisitor
Direct Known Subclasses:
AbstractContentAssistVisitor.AcceptableTypeVisitor, AbstractContentAssistVisitor.CollectionExpressionVisitor, AbstractContentAssistVisitor.EnumVisitor, AbstractContentAssistVisitor.IncompleteCollectionExpressionVisitor, AbstractContentAssistVisitor.InvalidExpressionVisitor, AbstractContentAssistVisitor.NotExpressionVisitor, AbstractContentAssistVisitor.RangeVariableDeclarationVisitor, AbstractContentAssistVisitor.ResultVariableVisitor, AbstractEclipseLinkExpressionVisitor, AbstractGrammarValidator.AbstractCollectionValidator, AbstractGrammarValidator.CollectionExpressionVisitor, AbstractGrammarValidator.ComparisonExpressionVisitor, AbstractGrammarValidator.DateTimeVisitor, AbstractGrammarValidator.NullExpressionVisitor, AbstractSemanticValidator.CollectionValuedPathExpressionVisitor, AbstractSemanticValidator.ComparingEntityTypeLiteralVisitor, AbstractSemanticValidator.StateFieldPathExpressionVisitor, AbstractValidator.NestedArrayVisitor, AbstractValidator.SubqueryVisitor, BasicStateObjectBuilder, BasicStateObjectBuilder.JoinBuilder, DeclarationResolver.DeclarationVisitor, DeclarationResolver.QualifyRangeDeclarationVisitor, DefaultSemanticValidator.NullValueVisitor, DefaultSemanticValidator.ResultVariableInOrderByVisitor, DefaultSemanticValidator.TypeValidator, DefaultSemanticValidator.UpdateClauseAbstractSchemaNameFinder, GenericSemanticValidatorHelper.IdentificationVariableVisitor, ResolverBuilder.CollectionExpressionVisitor
public abstract class AbstractExpressionVisitor extends Object implements ExpressionVisitor
The abstract definition of ExpressionVisitor, which implements all the methods but does nothing. It can be subclassed so that only the required methods are overridden.

Provisional API: This interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.