Errata

eXist

Errata for eXist

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
PDF
Page 16
2nd to last bulleted item

The comma before "eXist" is missplaced: "The XQuery wikibook is an excellent resource for XQuery and ***eXist ,with***
the majority of the examples developed for eXist." Should read "eXist, with"

Note from the Author or Editor:
Change location of ,

 Joe Wicentowski  Dec 29, 2014  Mar 06, 2015
PDF
Page 32
middle of page

The URLs on these pages "http://localhost:8080/exist/rest/apps/" may technically work, but really should have a "/db" between "/exist" and "rest/". In other words, the URLs here should be: "http://localhost:8080/exist/rest/db/apps/". The rest of the book is consistently correct in this. The only errors like this are on this page.

Note from the Author or Editor:
Please change URL-s as indicated

 Joe Wicentowski  Dec 29, 2014  Mar 06, 2015
PDF
Page 46
2nd to last paragraph

The sentence in question is: "Using the `/text` function will ensure we get the result as a text node." There should be no slash preceding "text". Also, `text` is not an XQuery/XPath function, but rather a node test. A more accurate description of `text` here would be:

"Using the text node test will ensure that text node(s) are returned rather than the `TITLE` element."

As the parenthetical plural in this revised version suggests, the text() node test can return 0 or more items. In this example's sample data, there is only one text node, but this is not always the case. So an even better example would use the XPath "string" function instead of the "text" node text. So I would suggest this:

1. Replace "/text()" with "string()" in the source code

2. Use this explanation: "The `string` function converts its argument to a string, ensuring we get only the string and not the `TITLE` element. In the case of an element node like the `TITLE` element, its string-value is the concatenation of the string-values of all its descendant text nodes."

This is a common source of confusion for new and seasoned users, and this book is a good tool for setting people on the correct course. See this article for more discussion: http://developer.marklogic.com/blog/text-is-a-code-smell.

Note from the Author or Editor:
To be rewritten on a major update of the book.

Joe Wicentowski  Dec 29, 2014 
PDF
Page 52
3rd bullet point

"couningt" is misspelled. Should be "counting".

Note from the Author or Editor:
Please change couningt to counting

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 52
3rd dashed item

In the sentence:

"The regular expression '\s+' signifies a sequence"

The single quotes surrounding "\s+" should be removed. The regular expression here is \s+, not '\s+'.

Note from the Author or Editor:
Please remove the quotes around '\s+' in the sentence: The regular expression '\s+' signifies a sequence of ...

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 53
Inside the "local:word-count" function

The regular expression used here is "\W+", but on the previous 2 pages, the regular expression used was "\s+". No explanation is provided for the sudden switch from "\W" to "\s". This is confusing.

Note from the Author or Editor:
Change "\W+" into "\s+"in example 3-7

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 59
Example 3-10

In the <index> element, the TEI namespace definition is extraneous and should be deleted, since it is not used in any of the child elements of this index definition:

<index “xmlns:tei="http://www.tei-c.org/ns/1.0”>

Note from the Author or Editor:
Please remove xmlns:tei="http://www.tei-c.org/ns/1.0" from example 3-10

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 61
Middle of the page

The line of code starting,

if(doc-available($logfile-full))then

uses a non-standard coding style for XQuery. The standard form has whitespace surrounding "if" and "then":

if (doc-available($logfile-full)) then

This form appears elsewhere in the book, but actually the book is inconsistent in formatting if-then-else expressions.

I derive my sense of XQuery style from O'Reilly's own book on _XQuery_ - see page 35 of Walmsley. Seconded by the XQuery Style document at http://xqdoc.org/xquery-style.pdf - see page 16.

Even though _eXist_ isn't a book *on* XQuery, it should guide users in the proper use and styling of it.

Note from the Author or Editor:
Please insert space after the if and before the then in the specified example

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 78
Figure 4-9

In the image, "soylent green" is misspelled as "solent green". The context here is clearly movies.

Note from the Author or Editor:
Probably needs change but is in afigure so its a bit more difficult than just a text change. Not very important, do this on a majour update?

 Joe Wicentowski  Dec 31, 2014 
PDF
Page 94
Middle of page, section entitled "The doc function"

Reading this leaves the reader with the erroneous impression that there's no way to tell if a document exists or not. This would have been a good opportunity to briefly introduce the "doc-available" function. See http://www.w3.org/TR/xpath-functions/#func-doc-available.

Note from the Author or Editor:
Add this when we do a major upgrade of the book.

 Joe Wicentowski  Dec 31, 2014 
Printed, PDF, ePub
Page 98
2nd half of page

Really should have an example of a GET request, it would clear up possible confusion as to how to place the parameters - are they part of the URL or part of the httpclient command? Surprising that there is an example of the simpler PUT request and not a GET request.

Note from the Author or Editor:
This is something I would like to postpone to a major new revision of the book. I currently don't have time to do this.

 ihe onwuka  Jan 23, 2015 
PDF
Page 123
1st paragraph

"Wicentowski" is misspelled as "Wictenowski". (The t should be moved.)

Note from the Author or Editor:
Please change spelling as indicated

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 232
Numbered item 3

"childelement" should be split into two words: "child" and "element"

Note from the Author or Editor:
Please insert space at specified location

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
PDF
Page 272
Line 2 of paragraph 1

A space is missing following the close parens:

... (see “Accompanying Source Code” on page 15)in the

Note from the Author or Editor:
Please insert space at specified location

 Joe Wicentowski  Dec 31, 2014  Mar 06, 2015
Printed
Page 274
1st paragraph

Say "see Accompanying Source Code on page 15" - There is no such section on page 15.

Note from the Author or Editor:
This link is to page xv not to page 15.
Can this be changed?

 Ihe Onwuka  Jan 22, 2015  Mar 06, 2015
PDF
Page 285
Introductory paragraph

The introduction to Chapter 12 on eXist's full-text indexing facilities should make mention that there is a W3C recommendation for full-text indexing that eXist does *not* implement. See http://www.w3.org/TR/xpath-full-text-10/. It would be worthwhile to add a brief discussion of the unique abilities of eXist's full-text facilities, compared to the W3C standard. (A pros and cons list, perhaps?)

Note from the Author or Editor:
This is a request for additional information that is IMHO in the "nice to have" category. Maybe we should add something when a major update of the book is done? We should review it then.

 Joe Wicentowski  Dec 31, 2014 
PDF
Page 292
1st paragraph of "Lucene's native query syntax" section

The text says, "Lucene has a native query syntax for defining full-text searches. Its full definition can be found at http://lucene.apache.org/core/3_6_1/queryparsersyntax.html."

The document cited for Lucene query syntax is out of date. eXist has been on Lucene 4.x for over a year. (See https://github.com/eXist-db/exist/tree/develop/extensions/indexes/lucene/lib.)

This URL should be replaced with one from 4.x, e.g.:

http://lucene.apache.org/core/4_10_3/queryparser/org/apache/lucene/queryparser/classic/package-summary.html

Note from the Author or Editor:
Please change URL

 Joe Wicentowski  Jan 09, 2015  Mar 06, 2015
PDF
Page 292
Last list item on page

In "You can also do a proximity searche", "searche" should be corrected to be "search". (Remove the trailing "e".)

Note from the Author or Editor:
Confirmed, please change.

 Joseph Wicentowski  Jan 09, 2015  Mar 06, 2015
PDF
Page 303
1st paragraph

In the phrase, "at least one of them is already supported fin the system", "fin" should be corrected to read "in". (Remove "f".)

 Joseph Wicentowski  Jan 09, 2015  Mar 06, 2015
Printed, PDF
Page 359
middle of page

Internal link in book was not rendered correctly. The question marks should be replaced with the second code callout icon (and thus refer the reader to code callout #2).

 O'Reilly Media
 		 Dec 09, 2014  Dec 09, 2014
PDF
Page 369
1st paragraph of new section

"PiotrKaminski" needs a space - should be changed to "Piotr Kaminski"

 Joe Wicentowski  Jan 11, 2015  Mar 06, 2015
PDF
Page 388
2nd sentence of 1st full paragraph

In the sentence beginning, "The eXist documentation for JMX is itself very reasonable," I would suggest that the word "reasonable" is an odd choice (a slightly overused word in this book, but here it's just not helpful), and would be better replaced by "complete."

 Joe Wicentowski  Jan 11, 2015  Mar 06, 2015
PDF
Page 410
1st paragraph in "eXist AMI" section

In the sentence, "It is available from the AWS Marketplace free of charge /TBD:", the phrase "/TBD:" should be removed or replaced.

Note from the Author or Editor:
Please remove just the text " /TBD:"

 Joe Wicentowski  Jan 11, 2015  Mar 06, 2015
PDF
Page 451
XML sample in middle of page

Namespace of <collection> element contains a typo:

<collection xmlns="http://;exist-db.org/collection-config/1.0">

namespace here has an erroneous semi-colon:

http://;exist-db.org

The semicolon should be removed.

Note from the Author or Editor:
Please change:

<collection xmlns="http://;exist-db.org/collection-config/1.0">

to:

<collection xmlns="http://exist-db.org/collection-config/1.0">

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015
PDF
Page 491
Final sentence on page

In the sentence,

“Java debugging in itself is a huge and advanced topic ,and...”

There is a space preceding the comma. The space should be moved to after the comma, to read:

“Java debugging in itself is a huge and advanced topic, and...”

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015
PDF
Page 494
Middle of 1st table

In the description of "restxqex", "RESTXQ" is misspelled as "RESTQX":

Module for eXist’s RESTQX resource function registry

should be:

Module for eXist’s RESTXQ resource function registry

Note from the Author or Editor:
COnfirmed, plase change.

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015
PDF
Page 497
1st paragraph of description of "cache" module

"sessionwide" should be spelled with a hyphen: "session-wide"

Note from the Author or Editor:
COnfirmed, please change

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015
Printed, PDF, ePub
Page 523
1st full paragraph

In the sentence,

The two main functions of interest are xqjson:serializejson

This function name is misspelled. There should be a hyphen separating "serialize" and "json":

The two main functions of interest are xqjson:serialize-json

Note from the Author or Editor:
Acknowledged. Please change.

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015
PDF
Page 529
Middle of diagram

There is a typo in the step:

HasCcompiled Query?

This should be:

Has Compiled Query?

 Joe Wicentowski  Jan 18, 2015  Mar 06, 2015