To use this book efficiently, the required software to be installed is Oracle SOA Suite 11g v11.1.1.6.0. The majority of the recipes also use Oracle JDeveloper 11g v11.1.1.6.0. Some recipes use the Eclipse development environment. Those recipes were developed using Eclipse IDE Juno v4.2 – SR2. For the web services development, we also use Apache Axis2 v1.6.1. For the advanced logging recipes, we use Apache Log4j v1.2.17.

This book is aimed at the Java developers who need to use BPEL programming to develop web services for SOA development. It is assumed that readers have some prior knowledge of SOA development. Developers should be experienced with Java programming, but knowledge of BPEL is not necessarily required. It does not matter if you are an experienced developer or just starting to learn. There are recipes suitable for every knowledge level. For beginners, we provide introductory explanations with references. More experienced developers will find the recipe description of how they work and discussion on how the topic can be further enhanced very useful.

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Let us examine the ClientProxy.java class first. We start, by creating the ServiceClient client and prepare the Options class to configure the ServiceClient client."

A block of code is set as follows:

<element name = "fault">
<complexType>
<sequence>
<element name = "msg" type = "string"/>
</sequence>
</complexType>
</element>

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

@Path("RESTWeatherService")
public class WeatherProvider {
  
  @GET
  @Path("/query")
  @Produces("text/xml")
  public String getWeatherInfo(@QueryParam("name") String name, @QueryParam("zip") String zip) {
    return "<weatherRes>Hello " + name + ". The weather in " + zip + " city cloudy. \n" + "Temperature is 24 degrees Celsius. \n" + "Humidity is 74%</weatherRes>";
    }
  }

Any command-line input or output is written as follows:

Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "C:\Programs\Oracle\Middleware\user_projects\domains\SOA_Dev\servers\AdminServer\dc\soa_8606ace0-2193-4
719-8cd7-08b2f0d57a04"; the exception reported is: java.lang.RuntimeException: failed to compile execlets of BPELProcess2_0
This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "When you double-click on the Java Embedding activity, a new dialog opens where we have to enter the code. We finish configuring the Java Embedding activity by clicking on the OK button."

You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.

Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at <[email protected]> with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.

You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.