The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

siamackj (32) [Avatar] Offline
Section 9.1.2

1) the <> element is configured manually with the uri of the end point that that is to...

You have an extra "that" there.

2) Well the WSDL document is a generic mechanism for describing service interfaces and is not bound directly the web services ...

should be changed to "is not bound directly to the web" ...

3) You may be wondering how Tuscany SCA runtime is able to find the WSDL file when this composite file only references it by QName and not by physical location.

not sure what do you mean by "QName"?

4) When Tuscany first reads the contribution is indexes all the artifacts ...

should be changed to :
When Tuscany first reads the contribution, it indexes all the artifacts ...
simon.nash (37) [Avatar] Offline
Re: More Typos
A QName is an XML qualified name with a namespace part and a local part. Here's an example from chapter 3 (listing 3.10):

<composite xmlns="" >

<component name="Customer">
< class="com.example.Customer" />
<property name="businessAddress">
<street>123 Main Street</street>
<city>New York</city>

In the above XML, "t:address" is a QName. Its namespace is "" and its local part is "address". The prefix "t" is not part of the QName; it's used as a shorthand for convenience in writing QNames in XML documents.