Print
MVEL 2.0 Type Literals

Type literals are treated pretty much the same as in Java, with the following format: <PackageName>.<ClassName>.

So a class may be qualified as such:

Or if the class has been imported either inline by or by external configuration--it is simply referred to by it's unqualified name:

Nested Classes

Nested classes are not accessible through the standard dot-notation (as in Java) in MVEL 2.0. Rather, you must qualify these classes with the $ symbol.

Powered by Atlassian Confluence