Errata

RESTful Java with JAX-RS 2.0

Errata for RESTful Java with JAX-RS 2.0

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.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

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

Version Location Description Submitted by Date submitted
ePub, Mobi Page 1
Cover page

After august 14, 2015 update, the ePub and Mobi version covers have an old Adobe ITC Garamond layout instead of the newer URW Typewriter layout.

 harrijauri  Aug 23, 2015 
Printed, PDF, Page 46
Section starting with @Path Expression annotations

This entire section needs to be rewritten to describe the 'correct' JAX-RS spec behavior. The author acknowledges in his blog, http://bill.burkecentral.com/2013/05/29/the-poor-jax-rs-request-dispatching-algorithm/ , that the RestEasy Precedence rules were mis interpreted AND that they have been adjusted to to allow RestEasy to pass the JAX-RS TCK. As stated in the blog the JAX-RS precedence rules are complex; however, since RestEasy now supports the "correct behavior" you should rewrite portions of this chapter (and examples) related to @PATH expressions and explain the new/updated standard precedence rules. Note: The book is otherwise fantastic.

Note from the Author or Editor:
I don't have time to do this, sorry.

 Henry  Apr 15, 2014 
Printed Page 100
Section "successful responses"

On page 100 the create() method is said to return ALWAYS 200 or 204 if called successfully.

In chapter 3 the create() method returns 201 when a new resource was created.

The return code 201 seems to be missing when explaining succssful responses on page 100.

Please clarify.

 Ulrich Straub  Apr 15, 2019 
ePub Page 118
3rd paragraph

"Here, the client is saying that it wants its response either compressed using GZIP or uncompressed (deflate)."

"deflate" is a compression method, so uncompressed is not the correct term, when deflate is used as an example.

 Felix Schumacher  Oct 03, 2018 
PDF Page 146
last code snippet o the page

UrlBuilder.queryParam() method has 2 parameters.
Books code snippet shows:
...
.queryParam("query={query}");
...

should be
...
.queryParam("query", "{query}");
...

 Marcin Kruglik  Oct 23, 2016 
Printed Page 150
First paragraph

You've mentioned that relativize() method in this scenario returns ../../d/e. However that doesn't seems to be true, as per Java doc (https://jersey.java.net/apidocs/2.6/jersey/index.html)

relativize

URI relativize(URI uri)
Relativize a URI with respect to the current request URI. Relativization works as follows:

If the URI to relativize is already relative, it is first resolved using resolve(java.net.URI).

The resulting URI is relativized with respect to the current request URI. If the two URIs do not share a prefix, the URI computed in step 1 is returned.


Note from the Author or Editor:
I don't have time to look into this one

 Anand Prakash  Feb 28, 2014 
ePub Page 160
3rd paragraph

"The @Priority annotation is actually reused from the injection framework that comes with JDK 7. ..."

The @Priority annotation is part of JEE 7.

 Felix Schumacher  Oct 03, 2018 
Printed Page 189
First Para, source code

There is no close() method defined for any of the exceptions. For instance: there is no WebApplicationException.close().

 Gaurav Khanna  Oct 11, 2015 
ePub Page 191
2nd paragraph

"The nonce and opaqu attributes are special server-generated keys that will be used ..."

"opaqu" is missing an "e".

 Felix Schumacher  Oct 03, 2018