org.aopalliance.reflect

Interface Field

All Superinterfaces:
Member, ProgramUnit

public interface Field
extends Member

This represents a field of a class.

Fields inherited from interface org.aopalliance.reflect.Member

PROVIDER_SIDE, USER_SIDE

Method Summary

CodeLocator
getReadLocator()
Same as getReadLocator(USER_SIDE).
CodeLocator
getReadLocator(int side)
This methods returns the points where the current field is read.
CodeLocator
getWriteLocator()
Same as getWriteLocator(USER_SIDE).
CodeLocator
getWriteLocator(int side)
This methods returns the points where the current field is written.

Methods inherited from interface org.aopalliance.reflect.Member

getDeclaringClass, getModifiers, getName

Methods inherited from interface org.aopalliance.reflect.ProgramUnit

addMetadata, getLocator, getMetadata, getMetadatas, removeMetadata

Method Details

getReadLocator

public CodeLocator getReadLocator()
Same as getReadLocator(USER_SIDE).

getReadLocator

public CodeLocator getReadLocator(int side)
This methods returns the points where the current field is read.

There are two different behaviors for this method depending on the side of the locator. At the user side, the locator designates all the points in methods bodies where the field is read (similarly to Code.getReadLocator(Field)). At the provider side, it really may depend on the implementor choice (e.g. it can return a locator on the body of the field's getter).

In Java, the user side is most of the time used so that you can use the method getReadLocator().

Parameters:
side - USER_SIDE || PROVIDER_SIDE

getWriteLocator

public CodeLocator getWriteLocator()
Same as getWriteLocator(USER_SIDE).

getWriteLocator

public CodeLocator getWriteLocator(int side)
This methods returns the points where the current field is written.

There are two different behaviors for this method depending on the side of the locator. At the user side, the locator designates all the points in methods bodies where the field is written (similarly to Code.getWriteLocator(Field)). At the provider side, it really may depend on the implementor choice (e.g. it can return a locator on the body of the field's setter).

In Java, the user side is most of the time used so that you can use the method getWriteLocator().

Parameters:
side - USER_SIDE || PROVIDER_SIDE