To help when defining WSDL messages, we recommend using a naming
strategy to improve readability when accessing messages within a BPEL
process. For example:
Append Request to input message names.
Append Reply to output request names.
Append Fault to fault message names.
Chapter 9
[ 183 ]
As you would expect, when defining a new WSDL document within NetBeans, the
New WSDL Document wizard allows faults to be defined at document creation time
(see Chapter 6 for details on creating WSDL documents within NetBeans).
When an operation described in WSDL returns a fault both, the fault type and a
description are returned to the client. In the case of a SOAP message, a returned fault
code may look like the following XML fragment.
SOAP-ENV:Client
notFriendFault
That person is not in your friend
list.
Handling Events
[ 184 ]
Now that we have discussed how faults are specified within WSDL documents
and how they are represented within XML results, let's discuss the different event
handlers available to BPEL processes, and in particular fault handlers that allow
developers to manage any faults that are thrown during BPEL process.
BPEL Handlers
Within NetBeans, four different types of handlers are available for use within the
BPEL process designer.
Pages:
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168