See: Description
Interface | Description |
---|---|
DocumentClient<N> |
For tpath, each document object is a collection of "Nodes".
|
Class | Description |
---|---|
Boolean<N> | |
BuiltInFunctions<N> |
The built-in functions for xpath are defined by the
"core XPath function library" in [XPath 1.0:4]
The following list is in that sequential order!
[Xpath 1.0:4.1]
Function: number last()
Function: number position()
Function: number count(node-set)
Function: node-set id(object)
Function: string local-name(node-set?)
Function: string namespace-uri(node-set?)
Function: string name(node-set?)
[Xpath 1.0:4.2]
Function: string string(object?)
Function: string concat(string, string, string*)
Function: boolean starts-with(string, string)
Function: boolean contains(string, string)
Function: string substring-before(string, string)
Function: string substring-after(string, string)
Function: string substring(string, number, number?)
Function: number string-length(string?)
Function: string normalize-space(string?)
Function: string translate(string, string, string)
[Xpath 1.0:4.3]
Function: boolean boolean(object)
Function: boolean not(boolean)
Function: boolean true()
Function: boolean false()
Function: boolean lang(string)
[Xpath 1.0:4.4]
Function: number number(object?)
Function: number sum(node-set)
Function: number floor(number)
Function: number ceiling(number)
Function: number round(number)
Y
ASSUME xpath expressions are type-checked, so do NOT ALWAYS check parameter structure
when executing, but crash.
|
Context<N> | |
ContextSequence<N> | |
Frontend | |
Function<N> | |
FunctionLibrary<N> |
Infra-Structure for defining xpath functions, built-in as well as extensions.
|
Interpreter<N> | |
Lazy<N> | |
NodeSet<N> |
Needs a
DocumentClient , currently only for DocumentClient.stringValue(N) . |
Number<N> | |
Operators | |
SimpleInterpreter<N> | |
String<N> | |
Test | |
Value<N> |
Exception | Description |
---|---|
NodeSetException |
see also the complete user documentation .