Warning: This is a facade provided for use by user code, not for implementation in user code. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
Initially when the expression context is first created the current scope is the global scope. The global scope is visible from all other scopes within the expression context and so global variables can be accessed from all scopes unless they have been hidden by a variable with the same name in a closer enclosing scope.
A stack frame is used to hold a set of variables that are independent of variables used within other stack frames. Each stack frame consists of a new scope in which variables can be declared. This scope is connected to the global scope associated with the environment expression but is not connected to scopes from the enclosing stack frame.
It is often necessary within an expression to resolve a prefix name to an expanded name. e.g. variable references typically use {@link com.volantis.xml.namespace.QName}s to refer to variables rather than expanded names. Therefore, when an expression context is created it is given with a namespace prefix resolver to use. It is the responsibility of some external mechanism to ensure that the mappings held by that resolver are update properly.
See {@link PropertyContainer} for more details.
@volantis-api-include-in PublicAPI @volantis-api-include-in ProfessionalServicesAPI @volantis-api-include-in InternalAPI @mock.generate | |
| |
| |
| |
| |