XQuery API for Java - Revision history

JeanmarcL: Fix link to Duration man page

2024-10-29T06:24:40Z

Fix link to Duration man page

← Previous revision		Revision as of 06:24, 29 October 2024
Line 165:		Line 165:
	\| {{code\|xs:integer}}		\| {{code\|xs:integer}}
	\|-		\|-
	\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|~~Duratio~~\|module=java.~~xmln~~}}		\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|Duration\|module=java.xml}}
	\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}		\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}
	\|-		\|-

Rofraja: Fix bare URLs references, add title

2023-09-07T16:43:11Z

Fix bare URLs references, add title

← Previous revision		Revision as of 16:43, 7 September 2023
Line 259:		Line 259:
	specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.		specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.

	This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf ~~{{Bare~~ ~~URL PDF~~\|date=~~March 2022~~}}</ref><ref>{{cite web \|url=http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|title=Groklaw - Oracle v. Google - Understanding the Copyright Issue with API Specifications \|website=www.groklaw.net \|url-status=dead \|archive-url=https://web.archive.org/web/20120505083130/http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|archive-date=2012-05-05}} </ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.		This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>{{cite web\|url=http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf \|title=Open Standards\|access-date=2023-09-07}}</ref><ref>{{cite web \|url=http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|title=Groklaw - Oracle v. Google - Understanding the Copyright Issue with API Specifications \|website=www.groklaw.net \|url-status=dead \|archive-url=https://web.archive.org/web/20120505083130/http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|archive-date=2012-05-05}} </ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.

	The license for the reference implementation is a fairly conventional BSD-style open source license.		The license for the reference implementation is a fairly conventional BSD-style open source license.

Cedar101: /* Examples */ fix syntaxhighlight errors

2023-07-06T07:26:13Z

Examples: fix syntaxhighlight errors

← Previous revision		Revision as of 07:26, 6 July 2023
Line 53:		Line 53:
	The following example illustrates creating a connection to an [[XML database\|XML Database]], submitting an [[XQuery]] expression, then processing the results in [[Java (programming language)\|Java]]. Once all of the results have been processed, the connection is closed to free up all resources associated with it.		The following example illustrates creating a connection to an [[XML database\|XML Database]], submitting an [[XQuery]] expression, then processing the results in [[Java (programming language)\|Java]]. Once all of the results have been processed, the connection is closed to free up all resources associated with it.

	<syntaxhighlight lang="~~java5~~">		<syntaxhighlight lang="java">
	// Create a new connection to an XML database		// Create a new connection to an XML database
	XQConnection conn = vendorDataSource.getConnection("myUser", "myPassword");		XQConnection conn = vendorDataSource.getConnection("myUser", "myPassword");
Line 78:		Line 78:
	Assume that the connection {{code\|conn}} already exists:		Assume that the connection {{code\|conn}} already exists:

	<syntaxhighlight lang="~~java5~~">		<syntaxhighlight lang="java">
	XQExpression expr = conn.createExpression();		XQExpression expr = conn.createExpression();

HotMess: Fixing usages of Javadoc:SE

2022-11-13T02:35:22Z

Fixing usages of Javadoc:SE

← Previous revision		Revision as of 02:35, 13 November 2022
Line 45:		Line 45:
	[[XQuery]] expressions return a result sequence of XDM<ref name="XQueryDataModel"/> items which in XQJ are represented through the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> interface. The programmer can use an <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> to walk over individual XDM<ref name="XQueryDataModel"/> items in the result sequence. Each item in the sequence has XDM<ref name="XQueryDataModel"/> type information associated with it, such as its node type e.g. {{code\|element()}}, {{code\|document-node()}} or an XDM atomic type such as {{code\|xs:string}}, {{code\|xs:integer}} or {{code\|xs:dateTime}}. XDM type information in XQJ can be retrieved via the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemType.html XQItemType]</code> interface.		[[XQuery]] expressions return a result sequence of XDM<ref name="XQueryDataModel"/> items which in XQJ are represented through the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> interface. The programmer can use an <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> to walk over individual XDM<ref name="XQueryDataModel"/> items in the result sequence. Each item in the sequence has XDM<ref name="XQueryDataModel"/> type information associated with it, such as its node type e.g. {{code\|element()}}, {{code\|document-node()}} or an XDM atomic type such as {{code\|xs:string}}, {{code\|xs:integer}} or {{code\|xs:dateTime}}. XDM type information in XQJ can be retrieved via the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemType.html XQItemType]</code> interface.

	Atomic [[XQuery]] items can be easily cast to [[Java (programming language)\|Java]] primitives via <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html XQItemAccessor]</code> methods such as <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getByte() getByte()]</code> and <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getFloat() getFloat()]</code>. Also [[XQuery]] items and sequences can be serialized to [[Document Object Model\|DOM]] {{Javadoc:SE\|org/w3c/dom\|Node}}, [[Simple API for XML\|SAX]] {{Javadoc:SE\|org/xml/sax\|ContentHandler}}, [[StAX]] {{Javadoc:SE\|javax/xml/stream\|XMLStreamReader}} and the generic IO {{Javadoc:SE\|java/io\|Reader}} and {{Javadoc:SE\|java/io\|InputStream}} classes.		Atomic [[XQuery]] items can be easily cast to [[Java (programming language)\|Java]] primitives via <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html XQItemAccessor]</code> methods such as <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getByte() getByte()]</code> and <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getFloat() getFloat()]</code>. Also [[XQuery]] items and sequences can be serialized to [[Document Object Model\|DOM]] {{Javadoc:SE\|org/w3c/dom\|Node\|module=java.xml}}, [[Simple API for XML\|SAX]] {{Javadoc:SE\|org/xml/sax\|ContentHandler\|module=java.xml}}, [[StAX]] {{Javadoc:SE\|javax/xml/stream\|XMLStreamReader\|module=java.xml}} and the generic IO {{Javadoc:SE\|java/io\|Reader}} and {{Javadoc:SE\|java/io\|InputStream}} classes.

	==Examples==		==Examples==
Line 165:		Line 165:
	\| {{code\|xs:integer}}		\| {{code\|xs:integer}}
	\|-		\|-
	\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|~~Duration~~}}		\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|Duratio\|module=java.xmln}}
	\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}		\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}
	\|-		\|-
Line 172:		Line 172:
	\| {{code\|xs:duration}} if the {{code\|Duration}} Object's state is {{code\|xs:duration}}		\| {{code\|xs:duration}} if the {{code\|Duration}} Object's state is {{code\|xs:duration}}
	\|-		\|-
	\|rowspan="8"\| {{Javadoc:SE\|javax/xml/datatype\|XMLGregorianCalendar}}		\|rowspan="8"\| {{Javadoc:SE\|javax/xml/datatype\|XMLGregorianCalendar\|module=java.xml}}
	\| {{code\|xs:date}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:date}}		\| {{code\|xs:date}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:date}}
	\|-		\|-
Line 189:		Line 189:
	\| {{code\|xs:time}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:time}}		\| {{code\|xs:time}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:time}}
	\|-		\|-
	\| {{Javadoc:SE\|javax/xml/namespace\|QName}}		\| {{Javadoc:SE\|javax/xml/namespace\|QName\|module=java.xml}}
	\| {{code\|xs:QName}}		\| {{code\|xs:QName}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Document}}		\| {{Javadoc:SE\|org/w3c/dom\|Document\|module=java.xml}}
	\| {{code\|document-node(element(*, xs:untyped))}}		\| {{code\|document-node(element(*, xs:untyped))}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|DocumentFragment}}		\| {{Javadoc:SE\|org/w3c/dom\|DocumentFragment\|module=java.xml}}
	\| {{code\|document-node(element(*, xs:untyped))}}		\| {{code\|document-node(element(*, xs:untyped))}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Element}}		\| {{Javadoc:SE\|org/w3c/dom\|Element\|module=java.xml}}
	\| {{code\|element(*, xs:untyped)}}		\| {{code\|element(*, xs:untyped)}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Attr}}		\| {{Javadoc:SE\|org/w3c/dom\|Attr\|module=java.xml}}
	\| {{code\|attribute(*, xs:untypedAtomic)}}		\| {{code\|attribute(*, xs:untypedAtomic)}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Comment}}		\| {{Javadoc:SE\|org/w3c/dom\|Comment\|module=java.xml}}
	\| {{code\|comment()}}		\| {{code\|comment()}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|ProcessingInstruction}}		\| {{Javadoc:SE\|org/w3c/dom\|ProcessingInstruction\|module=java.xml}}
	\| {{code\|processing-instruction()}}		\| {{code\|processing-instruction()}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Text}}		\| {{Javadoc:SE\|org/w3c/dom\|Text\|module=java.xml}}
	\| {{code\|text()}}		\| {{code\|text()}}
	\|-		\|-

Vt320: use correct case for Db2

2022-05-29T21:27:31Z

use correct case for Db2

← Previous revision		Revision as of 21:27, 29 May 2022
Line 234:		Line 234:

	* [[Oracle Database\|Oracle DB]] <small>(Not XDB)</small>		* [[Oracle Database\|Oracle DB]] <small>(Not XDB)</small>
	* [[IBM ~~DB2~~]]		* [[IBM Db2]]
	* [[Microsoft SQL Server]]		* [[Microsoft SQL Server]]
	* [[Adaptive Server Enterprise\|Sybase ASE]]		* [[Adaptive Server Enterprise\|Sybase ASE]]

VulcanSphere: Adding short description: "Application programming interface" (Shortdesc helper)

2022-04-29T12:05:23Z

Adding short description: "Application programming interface" (Shortdesc helper)

← Previous revision		Revision as of 12:05, 29 April 2022
Line 1:		Line 1:
			{{Short description\|Application programming interface}}
	{{Use dmy dates\|date=August 2015}}		{{Use dmy dates\|date=August 2015}}
	{{Infobox software		{{Infobox software

Rlink2: /* License */Archiving dead bare references

2022-03-26T19:11:52Z

License: Archiving dead bare references

← Previous revision		Revision as of 19:11, 26 March 2022
Line 258:		Line 258:
	specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.		specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.

	This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf {{Bare URL PDF\|date=March 2022}}</ref><ref>http://www.groklaw.net/articlebasic.php?story=20120221094600287 ~~{{Dead~~ ~~link~~\|~~date~~=~~February~~ ~~2022~~}}</ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.		This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf {{Bare URL PDF\|date=March 2022}}</ref><ref>{{cite web \|url=http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|title=Groklaw - Oracle v. Google - Understanding the Copyright Issue with API Specifications \|website=www.groklaw.net \|url-status=dead \|archive-url=https://web.archive.org/web/20120505083130/http://www.groklaw.net/articlebasic.php?story=20120221094600287 \|archive-date=2012-05-05}} </ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.

	The license for the reference implementation is a fairly conventional BSD-style open source license.		The license for the reference implementation is a fairly conventional BSD-style open source license.

BrownHairedGirl: tag with {{Bare URL PDF}}

2022-03-14T00:29:13Z

tag with {{Bare URL PDF}}

← Previous revision		Revision as of 00:29, 14 March 2022
Line 258:		Line 258:
	specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.		specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.

	This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf</ref><ref>http://www.groklaw.net/articlebasic.php?story=20120221094600287 {{Dead link\|date=February 2022}}</ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.		This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf {{Bare URL PDF\|date=March 2022}}</ref><ref>http://www.groklaw.net/articlebasic.php?story=20120221094600287 {{Dead link\|date=February 2022}}</ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.

	The license for the reference implementation is a fairly conventional BSD-style open source license.		The license for the reference implementation is a fairly conventional BSD-style open source license.

BrownHairedGirl: {{Dead link}} tag on bare URL refs which return HTTP 404 or 410

2022-02-28T22:58:33Z

{{Dead link}} tag on bare URL refs which return HTTP 404 or 410

← Previous revision		Revision as of 22:58, 28 February 2022
Line 258:		Line 258:
	specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.		specification provided that it fully implements the entire specification, that it does not modify or extend any interfaces, and that it passes the compatibility tests.

	This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf</ref><ref>http://www.groklaw.net/articlebasic.php?story=20120221094600287</ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.		This provision has caused some controversy. Firstly, it is not universally accepted that implementing a published specification is something that requires a license (that is, that copyright law would disallow this in the absence of a license).<ref>http://rosenlaw.com/wp-content/uploads/Open-Standards.pdf</ref><ref>http://www.groklaw.net/articlebasic.php?story=20120221094600287 {{Dead link\|date=February 2022}}</ref> Secondly, the license does not meet the criteria to qualify as an open source license (see [[Open Source Definition]]), because of the ban on making extensions and modifications. This has led some open source enthusiasts to challenge whether XQJ implementations can ever be considered truly open source.

	The license for the reference implementation is a fairly conventional BSD-style open source license.		The license for the reference implementation is a fairly conventional BSD-style open source license.

Minorax: Reverted edits by 117.234.142.96 (talk) to last revision by Sir Dirt: nonconstructive edits

2020-10-13T04:47:53Z

Reverted edits by 117.234.142.96 (talk) to last revision by Sir Dirt: nonconstructive edits

← Previous revision		Revision as of 04:47, 13 October 2020
Line 15:		Line 15:
	}}		}}

	[[File:XQJ-Architecture.svg\|thumb\|275px\|~~014658_7-&~~ ~~268&8+6~~ ~~Arvind~~ ~~Ritu~~]]		[[File:XQJ-Architecture.svg\|thumb\|275px\|General architecture of how an XQJ driver is used to communicate with an XML Database from Java Applications.]]

			'''XQuery API for Java''' ('''XQJ''') refers to the common [[Java API]] for the [[W3C]] [[XQuery]] 1.0 specification.
	.

			The XQJ API enables Java programmers to execute [[XQuery]] against an [[XML]] data source (e.g. an [[XML database]]) while reducing or eliminating [[Vendor lock-in\|vendor lock in]].
	The

	The XQJ API provides Java developers with an interface to the XQuery Data Model.<ref name="XQueryDataModel">[http://www.w3.org/TR/xpath-datamodel/ XQuery 1.0 and XPath 2.0 Data Model (XDM)]</ref> Its design is similar to the [[Java Database Connectivity\|JDBC API]] which has a client/server feel and as such lends itself well to Server-based [[XML database\|XML Databases]] and less well to client-side [[XQuery]] processors, although the "[[Database connection\|connection]]" part is a very minor part of the entire API. Users of the XQJ API can bind [[Java (programming language)\|Java]] values to [[XQuery]] expressions, preventing [[Code injection\|code injection attacks]].<ref>[http://www.cfoster.net/articles/xqj-tutorial/binding-java-variables.xml Binding Java Variables]</ref> Also, multiple [[XQuery]] expressions can be executed as part of an [[atomic transaction]].		The XQJ API provides Java developers with an interface to the XQuery Data Model.<ref name="XQueryDataModel">[http://www.w3.org/TR/xpath-datamodel/ XQuery 1.0 and XPath 2.0 Data Model (XDM)]</ref> Its design is similar to the [[Java Database Connectivity\|JDBC API]] which has a client/server feel and as such lends itself well to Server-based [[XML database\|XML Databases]] and less well to client-side [[XQuery]] processors, although the "[[Database connection\|connection]]" part is a very minor part of the entire API. Users of the XQJ API can bind [[Java (programming language)\|Java]] values to [[XQuery]] expressions, preventing [[Code injection\|code injection attacks]].<ref>[http://www.cfoster.net/articles/xqj-tutorial/binding-java-variables.xml Binding Java Variables]</ref> Also, multiple [[XQuery]] expressions can be executed as part of an [[atomic transaction]].

← Previous revision		Revision as of 02:35, 13 November 2022
Line 45:		Line 45:
	[[XQuery]] expressions return a result sequence of XDM<ref name="XQueryDataModel"/> items which in XQJ are represented through the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> interface. The programmer can use an <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> to walk over individual XDM<ref name="XQueryDataModel"/> items in the result sequence. Each item in the sequence has XDM<ref name="XQueryDataModel"/> type information associated with it, such as its node type e.g. {{code\|element()}}, {{code\|document-node()}} or an XDM atomic type such as {{code\|xs:string}}, {{code\|xs:integer}} or {{code\|xs:dateTime}}. XDM type information in XQJ can be retrieved via the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemType.html XQItemType]</code> interface.		[[XQuery]] expressions return a result sequence of XDM<ref name="XQueryDataModel"/> items which in XQJ are represented through the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> interface. The programmer can use an <code>[http://xqj.net/javadoc/javax/xml/xquery/XQResultSequence.html XQResultSequence]</code> to walk over individual XDM<ref name="XQueryDataModel"/> items in the result sequence. Each item in the sequence has XDM<ref name="XQueryDataModel"/> type information associated with it, such as its node type e.g. {{code\|element()}}, {{code\|document-node()}} or an XDM atomic type such as {{code\|xs:string}}, {{code\|xs:integer}} or {{code\|xs:dateTime}}. XDM type information in XQJ can be retrieved via the <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemType.html XQItemType]</code> interface.

	Atomic [[XQuery]] items can be easily cast to [[Java (programming language)\|Java]] primitives via <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html XQItemAccessor]</code> methods such as <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getByte() getByte()]</code> and <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getFloat() getFloat()]</code>. Also [[XQuery]] items and sequences can be serialized to [[Document Object Model\|DOM]] {{Javadoc:SE\|org/w3c/dom\|Node}}, [[Simple API for XML\|SAX]] {{Javadoc:SE\|org/xml/sax\|ContentHandler}}, [[StAX]] {{Javadoc:SE\|javax/xml/stream\|XMLStreamReader}} and the generic IO {{Javadoc:SE\|java/io\|Reader}} and {{Javadoc:SE\|java/io\|InputStream}} classes.		Atomic [[XQuery]] items can be easily cast to [[Java (programming language)\|Java]] primitives via <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html XQItemAccessor]</code> methods such as <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getByte() getByte()]</code> and <code>[http://xqj.net/javadoc/javax/xml/xquery/XQItemAccessor.html#getFloat() getFloat()]</code>. Also [[XQuery]] items and sequences can be serialized to [[Document Object Model\|DOM]] {{Javadoc:SE\|org/w3c/dom\|Node\|module=java.xml}}, [[Simple API for XML\|SAX]] {{Javadoc:SE\|org/xml/sax\|ContentHandler\|module=java.xml}}, [[StAX]] {{Javadoc:SE\|javax/xml/stream\|XMLStreamReader\|module=java.xml}} and the generic IO {{Javadoc:SE\|java/io\|Reader}} and {{Javadoc:SE\|java/io\|InputStream}} classes.

	==Examples==		==Examples==
Line 165:		Line 165:
	\| {{code\|xs:integer}}		\| {{code\|xs:integer}}
	\|-		\|-
	\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|~~Duration~~}}		\|rowspan="3"\| {{Javadoc:SE\|javax/xml/datatype\|Duratio\|module=java.xmln}}
	\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}		\| {{code\|xs:dayTimeDuration}} if the {{code\|Duration}} Object's state is {{code\|xs:dayTimeDuration}}
	\|-		\|-
Line 172:		Line 172:
	\| {{code\|xs:duration}} if the {{code\|Duration}} Object's state is {{code\|xs:duration}}		\| {{code\|xs:duration}} if the {{code\|Duration}} Object's state is {{code\|xs:duration}}
	\|-		\|-
	\|rowspan="8"\| {{Javadoc:SE\|javax/xml/datatype\|XMLGregorianCalendar}}		\|rowspan="8"\| {{Javadoc:SE\|javax/xml/datatype\|XMLGregorianCalendar\|module=java.xml}}
	\| {{code\|xs:date}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:date}}		\| {{code\|xs:date}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:date}}
	\|-		\|-
Line 189:		Line 189:
	\| {{code\|xs:time}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:time}}		\| {{code\|xs:time}} if the {{code\|XMLGregorianCalendar}} Object's state is {{code\|xs:time}}
	\|-		\|-
	\| {{Javadoc:SE\|javax/xml/namespace\|QName}}		\| {{Javadoc:SE\|javax/xml/namespace\|QName\|module=java.xml}}
	\| {{code\|xs:QName}}		\| {{code\|xs:QName}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Document}}		\| {{Javadoc:SE\|org/w3c/dom\|Document\|module=java.xml}}
	\| {{code\|document-node(element(*, xs:untyped))}}		\| {{code\|document-node(element(*, xs:untyped))}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|DocumentFragment}}		\| {{Javadoc:SE\|org/w3c/dom\|DocumentFragment\|module=java.xml}}
	\| {{code\|document-node(element(*, xs:untyped))}}		\| {{code\|document-node(element(*, xs:untyped))}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Element}}		\| {{Javadoc:SE\|org/w3c/dom\|Element\|module=java.xml}}
	\| {{code\|element(*, xs:untyped)}}		\| {{code\|element(*, xs:untyped)}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Attr}}		\| {{Javadoc:SE\|org/w3c/dom\|Attr\|module=java.xml}}
	\| {{code\|attribute(*, xs:untypedAtomic)}}		\| {{code\|attribute(*, xs:untypedAtomic)}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Comment}}		\| {{Javadoc:SE\|org/w3c/dom\|Comment\|module=java.xml}}
	\| {{code\|comment()}}		\| {{code\|comment()}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|ProcessingInstruction}}		\| {{Javadoc:SE\|org/w3c/dom\|ProcessingInstruction\|module=java.xml}}
	\| {{code\|processing-instruction()}}		\| {{code\|processing-instruction()}}
	\|-		\|-
	\| {{Javadoc:SE\|org/w3c/dom\|Text}}		\| {{Javadoc:SE\|org/w3c/dom\|Text\|module=java.xml}}
	\| {{code\|text()}}		\| {{code\|text()}}
	\|-		\|-