Errata

The publisher, Apress, maintains the official site for submitting and tracking errata. You can find the Apress errata information at: http://www.apress.com/book/errata/1055

The Oracle Service Bus book was written before the final product was released. As a result, there have been some changes in the product that could not be documented in the book itself. I have created this page to document the differences between the book and the released product.

OSB 10gR3

Page 42 - Creating a Proxy Service

The product designers have modified the shortcut for creating a proxy service from a business service. The good news is that the new process is actually more intuitive! Replace steps 1 - 4 in the book with the following:

Right-click on the business service HelloWorldBiz in the Project Explorer window on the left side of the Workshop IDE.
From the popup menu, select Oracle Service Bus -> Generate Proxy Service
In the dialog that comes up, select HelloWorld_SB as the parent folder. Name the proxy service HelloWorld. Press the Finish button.
The proxy service will be created and will open up on the main window of the Workshop IDE. Click on the Transport tab at the bottom of the main window and set the Endpoint URI to
```
/esb/HelloWorld
```

Chapter 6, page 107, step 16

The expression shown in the book is missing the namespaces. The correct expression should be:

$soapResponseBody/alsb:getCreditRatingResponse/alsb:return/text()

and it will work.

Chapter 10 Page 216 - Missing build.xml file

The build.xml file referred to on page 216 does not exist in the source code. When I was originally writing the second edition of the book, I was using ANT files extensively for client-side programs. With the ALSB 3.0 release (at the time of my writing) the product improved (in my opinion) the creation of these client programs, making it easy to do from within the IDE itself. When that happened, the need for the build.xml file disappeared and I deleted the file, apparently without updating the book's text.

My apologies for the confusion. The good news is that you don't need the build.xml file.

Page 381 Problems importing the projects

Some users are getting an error when importing the project into the sample production environment. The error message is:

Problem invoking WLST - Traceback (innermost last):

File "c:\Beacon\Workspaces\Middleware\ALSB\import.py", line 7, in ?

ImportError: No module named wli

Line 7 in the import.py file is:

   from com.bea.wli.sb.util import Refs

The Refs object in the script maps to the com.bea.wli.sb.util.Refs.class file in the osb_10.3\lib\sb-kernel-api.jar file.

The root of the problem seems to reside in the build.xml file in the ExportImport folder of the Administration project. Check to be sure the bea.com property is set correctly to your system (line 8 in the build.xml file). Its default setting is:

<property name="bea.home" value="C:/BEAHome/alsb30" />

A little further down in the file we define the wlst.class.path ANT variable. Modify it to point to the correct sb-kernel-api.jar file. For example, the original is:

<path id="wlst.class.path">

    <fileset dir="${bea.home}/alsb_3.0/lib">

        <include name="sb-kernel-api.jar" />

    </fileset>

Modify it to become

<path id="wlst.class.path">

    <fileset dir="${bea.home}/osb_10.3/lib">

       <include name="sb-kernel-api.jar" />

    </fileset>