Note
that every BPEL process should start with a receive or a pick activity.
The purpose of static analysis is to detect any undefined semantics or
invalid semantics within a process definition that was not detected during
the schema validation. Any process definition that fails one or more of
these checks must be rejected by the WS-BPEL processor. That means,
if you have invalid semantics in your BPEL process, the process header
turns red.
When a BPEL process is created by the New BPEL Process wizard, it creates an
empty activity:
The following code shows the source of the empty BPEL process:
name="BP_Reservation"
targetNamespace=
"http://airalliance.org/bpel/BPEL_Reservation/BP_Reservation"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Chapter 10
[ 211 ]
xmlns:tns=
"http://airalliance.org/bpel/BPEL_Reservation/BP_Reservation">
Now, drag-and-drop the NorthAir Web Service implementation from your project
panel into the BPEL diagram. This action will import the public interfaces of
NorthAir Web Service into the Process Files | Partners folder. You need to create
a partner link for invoking this Web Service.
Pages:
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193