Difference between revisions of "Java Bindings"

From BaseX Documentation
Jump to navigation Jump to search
Line 1: Line 1:
 
This article is part of the [[Querying|Query Portal]].
 
This article is part of the [[Querying|Query Portal]].
It demonstrates how Java code can be invoked from XQuery.
+
It demonstrates two ways to invoke Java code from XQuery,
 +
and (since {{Version|7.2.1}}) an extension to make Java code aware of the current context.
  
 
The Java Binding [[Querying|query]] feature is an extensibility mechanism which enables developers
 
The Java Binding [[Querying|query]] feature is an extensibility mechanism which enables developers
 
to directly access Java variables and execute code from XQuery. Java classes are identified by
 
to directly access Java variables and execute code from XQuery. Java classes are identified by
 
namespaces; the namespace URI must be of the form {{Mono|java:fully.qualified.ClassName}}.
 
namespaces; the namespace URI must be of the form {{Mono|java:fully.qualified.ClassName}}.
 +
 +
=Namespace Declarations=
  
 
The following example uses Java’s {{Mono|Math}} class and returns the cosine of an angle.
 
The following example uses Java’s {{Mono|Math}} class and returns the cosine of an angle.
Line 31: Line 34:
 
as Java code cannot be pre-compiled, and will often be evaluated slower than optimized
 
as Java code cannot be pre-compiled, and will often be evaluated slower than optimized
 
XQuery code. Next, Java code can only be executed with [[User_Management|admin permissions]].
 
XQuery code. Next, Java code can only be executed with [[User_Management|admin permissions]].
 +
 +
=Module Imports=
 +
 +
{{Mark|Introduced with Version 7.2.1:}}
 +
 +
Java code can also be integrated by ''importing'' classes as modules. In this case,
 +
a new instance of the addressed class is created, which can then be accessed in the query body.
 +
 +
An example (the boolean values returned by {{Mono|set:add()}} are ignored):
 +
 +
<pre class="brush:xquery">
 +
import module namespace set = "java:java.util.HashSet";
 +
let $loop :=
 +
  for $i in 1 to 10000
 +
  return set:add($i)
 +
return set:size()
 +
</pre>
 +
 +
Advantages of this approach are:
 +
* imported code can be executed faster than instances created at runtime via {{Mono|new()}}.
 +
* the work on class instances ensures that queries run in parallel will not cause any concurrency issues (provided that the class contains no static variables or functions).
 +
 +
A drawback is that no arguments can be passed on to the class constructor.
 +
This also implies that the class must provide a constructor without no arguments.
 +
 +
=Context-Awareness=
 +
 +
 +
=Changelog=
 +
 +
===Version 7.2.1===
 +
 +
* Added: import of Java modules
  
 
[[Category:XQuery]]
 
[[Category:XQuery]]
 
[[Category:API]]
 
[[Category:API]]

Revision as of 17:33, 28 March 2012

This article is part of the Query Portal. It demonstrates two ways to invoke Java code from XQuery, and (since Version 7.2.1) an extension to make Java code aware of the current context.

The Java Binding query feature is an extensibility mechanism which enables developers to directly access Java variables and execute code from XQuery. Java classes are identified by namespaces; the namespace URI must be of the form java:fully.qualified.ClassName.

Namespace Declarations

The following example uses Java’s Math class and returns the cosine of an angle. The cos() method can be directly called, as it is a static method:

declare namespace math = "java:java.lang.Math";
math:cos(xs:double(0))

The next example writes 256 bytes to the file output.txt. First, a new FileWriter instance is created: by calling the new() function, the class constructor is invoked. Instance methods are called by passing on the resulting Java object as first argument:

declare namespace fw = "java:java.io.FileWriter";
 let $file := fw:new('output.txt')
return (
  for $i in 0 to 255
  return fw:write($file, xs:int($i)),
  fw:close($file)
)

In general, it is recommended to use XQuery expressions and functions whenever possible, as Java code cannot be pre-compiled, and will often be evaluated slower than optimized XQuery code. Next, Java code can only be executed with admin permissions.

Module Imports

Template:Mark

Java code can also be integrated by importing classes as modules. In this case, a new instance of the addressed class is created, which can then be accessed in the query body.

An example (the boolean values returned by set:add() are ignored):

import module namespace set = "java:java.util.HashSet";
let $loop :=
  for $i in 1 to 10000
  return set:add($i)
return set:size()

Advantages of this approach are:

  • imported code can be executed faster than instances created at runtime via new().
  • the work on class instances ensures that queries run in parallel will not cause any concurrency issues (provided that the class contains no static variables or functions).

A drawback is that no arguments can be passed on to the class constructor. This also implies that the class must provide a constructor without no arguments.

Context-Awareness

Changelog

Version 7.2.1

  • Added: import of Java modules