Errata

It shows mismatched tags in the XML.

It has:

<coffee>Latte</order>

surely it should be:

<coffee>Latte</coffee>

As the <order> and </order> tags are already present.

Note from the Author or Editor:
Figure 1.4 is yet another case of the O'Reilly in house art team providing inferior diagrams and introducing mistakes compared to the original provided by the authors.

Please replace the line in the XML in the green box from:

<coffee>latte</order>

To:

<coffee>latte</coffee>

The green box representing state 3 shows links to states 1 and 5. However the link to state 5 (pink) actually points back to the pink box that represents state 6. I suggest correcting the numeral 5 in the pink link and in the black text below the box to 6, that would fix it.

Note from the Author or Editor:
The numeral "5" on top of the pink link inside the green box should be changed to "6", as per the reader's suggestion.

</order) should be </order>;
<invoice) should be </invoice>

Note from the Author or Editor:
In the diagram 2.1 where the customer figure talks to the waiter figure, the final character in each speech bubble is a standard closing bracket )

It should be a closing angle bracket >

I wonder whether a <status/> field is missing in Ex 4-7. Maybe
<status>paid</status>?

Note from the Author or Editor:
This is an accurate error. Example 4-7 should read:

HTTP/1.1 200 OK Content-Length: 241 Content-Type: application/xml Date: Wed, 19 Nov 2008 21:48:10 GMT
<order xmlns=&#8242;&#8242;http://schemas.restbucks.com/order&#8242;&#8242;> <location>takeAway</location> <items>
<item> <name>latte</name> <quantity>1</quantity> <milk>whole</milk> <size>small</size>
</item> </items>
<status>paid</status>
</order>

Example 4-12 should be able to throw different exceptions to represent an order being not found and some other internal server error. However the line throw new WebApplicationException(Response.Status.NOT_FOUND) is inside a try-block which will catch and rethrow, so it's impossible for a not-found-error to escape.

Note from the Author or Editor:
Example 4-12 should be changed to read exactly as follows:

@Path("/order")
public class OrderingService {
@GET
@Produces("application/xml")
@Path("/{orderId}")
public String getOrder(@PathParam("orderId") String orderId) {

Order order = OrderDatabase.getDatabase().getOrder(orderId);

if (order == null) {
throw new WebApplicationException(Response.Status.NOT_FOUND);
} else {
try {
return xstream.toXML(order);
} catch (Exception e) {
throw new WebApplicationException(Response.Status.INTERNAL_SERVER_ERROR);
}
}
}
// Remainder of implementation omitted for brevity
}

<status>pending</preparing> -- not sure if the content should be "pending" or "preparing", but the end tag </preparing> is definitely wrong and should be replaced with a </status> tag.

Note from the Author or Editor:
Please replace figure 4-29 as follows:

PUT /order/1234 HTTP/1.1
Host: restbucks.com
If-Match: "72232bd0daafa12f7e2d1561c81cd082"

<order xmlns="http://schemas.restbucks.com/order"">
<location>takeAway</location>
<items>
<item>
<milk>skim</milk>
<name>cappuccino</name>
<quantity>2</quantity>
<size>large</size>
</item>
</items>
<status>pending</status>
</order>

URI template {/orderId} should be /{orderId}

Note from the Author or Editor:
p.67 print edition, last bullet point: {/orderId} should be /{orderId}

The last end-tag should be </order> instead of </entry>.

Note from the Author or Editor:
Example 5-5 needs to be changed to be as follows:

<order xmlns=&#8242;&#8242;http://schemas.restbucks.com&#8242;&#8242;>
<location>takeAway</location>
<item>
<name>latte</name>
<quantity>1</quantity>
<milk>whole</milk>
<size>small</size>
</item>
<cost>2.0</cost>
<status>payment-expected</status>
<link rel="http://relations.restbucks.com/payment"
href="https://restbucks.com/payment/1234"/>
<link rel="http://relations.restbucks.com/special-offer"
href="http://restbucks.com/offers/cookie/1234"/>
</order>

I think this piece of code

if (validStartAndEndEntries(startPos, endPos)) {
// Bad URI - the paramters don't align with our feeds
return Response.status(Status.NOT_FOUND).build();
}

should be

if (!validStartAndEndEntries(startPos, endPos)) {
// Bad URI - the parameters don't align with our feeds
return Response.status(Status.NOT_FOUND).build();
}

because it should return a 404 when the URI is invalid.

Note from the Author or Editor:
Example 7-7 should read:

@GET
@Path("/{startPos},{endPos}")
@Produces("application/atom+xml")
public Response getSpecificFeed(@PathParam("startPos") int startPos, @PathParam("endPos") int endPos) {

if (invalidStartAndEndEntries(startPos, endPos)) {
// Bad URI - the paramters don't align with our feeds
return Response.status(Status.NOT_FOUND).build();
}

if(workingFeedRequested(startPos)) {
return getWorkingFeed();
}

EventFeedGenerator generator = new
EventFeedGenerator(uriInfo.getRequestUri(), ENTRIES_PER_FEED);
Feed feed = generator.feedFor(startPos);
return Response.ok().entity(stringify(feed)).header(CACHE_CONTROL_HEADER,
cacheDirective(CachePolicy.getArchiveFeedLifetime()))
.type(ATOM_MEDIA_TYPE).build();
}

private Response getWorkingFeed() {
EventFeedGenerator generator = new
EventFeedGenerator(uriInfo.getRequestUri(),
ENTRIES_PER_FEED);
Feed feed = generator.getWorkingFeed();

return Response.ok().entity(stringify(feed))
.header(CACHE_CONTROL_HEADER,
cacheDirective(CachePolicy.getWorkingFeedLifetime()))
.type(ATOM_MEDIA_TYPE).build();
}

The product and region elements are in the http://www.w3.org/2005/Atom namespace while they belong in the http://schemas.restbucks.com/promotion namespace. The elements <ns2:product ..> and <ns2:region .. > should be replaced by <product ..> and <region ..>.

The attribute "xmlns:ns2" on the parent promotion element on page 216 is thereby unnecessary and can be removed.

Note from the Author or Editor:
Example 7-16 should be changed to read exactly as follows (maintaining all bold formatting):


HTTP/1.1 200 OK
server: grizzly/1.8.1
Cache-Control: max-age=2592000
Content-Type: application/atom+xml

�
<entry>
<title>product</title>
<link rel="self"
href="http://restbucks.com/product-catalog/notifications/notifications/120" />
<link rel="related" href="http://restbucks.com/products/2012703733" />
<category term="product"
scheme="http://restbucks.com/product-catalog/notifications/categories/type" />
<category term="new"
scheme="http://restbucks.com/product-catalog/notifications/categories/status" />
<id>tag:restbucks.com,2009-08-15:120</id>
<updated>2008-04-04T16:24:02Z</updated>
<content type="application/vnd.restbucks+xml">
<product xmlns="http://schemas.restbucks.com/product"
href="http://restbucks.com/products/2012703733">
<name>product name 543809053</name>
<price>2.34</price>
</product>
</content>
</entry>
<entry>
<title>promotion</title>
<link rel="self"
href="http://restbucks.com/product-catalog/notifications/notifications/148" />
<link rel="related" href="http://restbucks.com/promotions/1669488880" />
<category term="promotion"
scheme="http://restbucks.com/product-catalog/notifications/categories/type" />
<category term="new"
scheme="http://restbucks.com/product-catalog/notifications/categories/status" />
<id>tag:restbucks.com,2009-08-15:148</id>
<updated>2008-04-04T16:24:02Z</updated>
<content type="application/vnd.restbucks+xml">
<promotion xmlns="http://schemas.restbucks.com/promotion"
href="http://restbucks.com/promotions/1669488880">
<effective>2009-08-15</effective>
<product type="application/vnd.restbucks+xml"
href="http://restbucks.com/products/1995649500" />
<region type="application/vnd.restbucks+xml"
href="http://restbucks.com/regions/2140798621" />
</promotion>
</content>
</entry>
�

I think there is an typo in the HTTP header WWW-Authenticate. There is an 'u' missing. Same problem in example 9-4 on page 287.

Note from the Author or Editor:
Please change figure 9-2 to read:

401 Unauthorized
WWW-Authenticate: Basic realm=′′payments@restbucks.com′′

URL for currency should be "http://restbuck.com/vocab#uk-pounds" instead of "http://restbuck.com/vocab#latte".

Note from the Author or Editor:
Yes, this problem must have been introduced during the figure designs.

Here, even after stating that POST will be used for updates to an order, this figure indicates using PUT. The authors clearly changed their minds along the way somewhere.

Note from the Author or Editor:
In Figure 5-7, change:

Update (PUT)

to

Update (POST)

(Page number is Kindle location.)

Coffee card link should be rel="self"

Note from the Author or Editor:
Example 5-15 should read as follows:


HTTP/1.1 200 OK
Content-Length: 239
Content-Type: application/vnd.restbucks+xml
Date: Sun, 21 Mar 2010 19:07:33 GMT

<coffeeCard xmlns="http://schemas.restbucks.com">
<link rel="self"
href="http://restbucks.com/coffeecard/4456afd23">
<tamperProof>fff405268fea556a351459e7368bc1d3</tamperProof>
<numberOfCoffees>2</numberOfCoffees>
</coffeeCard>

<atom:generated> should be <atom:generator>. (Example 7-1 itself is correct.)

Note from the Author or Editor:
On page 188 (eBook at least) the string:

atom:generated

should be

atom:generator