上一篇文章开了一个小头,这次继续写一些自己读WS-BPEL2.0的心得体会,供大家分享
业务逻辑Business Process单独进行定义,该部分主要使用以下的XML元素,以及嵌套关系,其中这个并不是标准的XML只是为了方便说明其中的关系和结构
其中
?表示(0或1)
*表示(0或更多)
+表示(1或更多)
<process name="NCName" targetNamespace="anyURI"
![](/Images/OutliningIndicators/None.gif)
queryLanguage="anyURI"?
![](/Images/OutliningIndicators/None.gif)
expressionLanguage="anyURI"?
![](/Images/OutliningIndicators/None.gif)
suppressJoinFailure="yes|no"?
![](/Images/OutliningIndicators/None.gif)
exitOnStandardFault="yes|no"?
![](/Images/OutliningIndicators/None.gif)
xmlns="http://schemas.xmlsoap.org/ws/2004/03/business-process/">
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<import namespace="anyURI"?
![](/Images/OutliningIndicators/None.gif)
location="anyURI"?
![](/Images/OutliningIndicators/None.gif)
importType="anyURI" />*
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<extensions>?
![](/Images/OutliningIndicators/None.gif)
<extension namespace="anyURI" mustUnderstand="yes|no" />*
![](/Images/OutliningIndicators/None.gif)
</extensions>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<partnerLinks>?
![](/Images/OutliningIndicators/None.gif)
<!-- Note: At least one role must be specified. -->
![](/Images/OutliningIndicators/None.gif)
<partnerLink name="NCName"
![](/Images/OutliningIndicators/None.gif)
partnerLinkType="QName"
![](/Images/OutliningIndicators/None.gif)
myRole="NCName"?
![](/Images/OutliningIndicators/None.gif)
partnerRole="NCName"?
![](/Images/OutliningIndicators/None.gif)
initializePartnerRole="yes|no"?>+
![](/Images/OutliningIndicators/None.gif)
</partnerLink>
![](/Images/OutliningIndicators/None.gif)
</partnerLinks>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<messageExchanges>?
![](/Images/OutliningIndicators/None.gif)
<messageExchange name="NCName" />+
![](/Images/OutliningIndicators/None.gif)
</messageExchanges>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<variables>?
![](/Images/OutliningIndicators/None.gif)
<variable name="BPELVariableName"
![](/Images/OutliningIndicators/None.gif)
messageType="QName"?
![](/Images/OutliningIndicators/None.gif)
type="QName"?
![](/Images/OutliningIndicators/None.gif)
element="QName"? />+
![](/Images/OutliningIndicators/None.gif)
</variables>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<correlationSets>?
![](/Images/OutliningIndicators/None.gif)
<correlationSet name="NCName" properties="QName-list" />+
![](/Images/OutliningIndicators/None.gif)
</correlationSets>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<faultHandlers>?
![](/Images/OutliningIndicators/None.gif)
<!-- Note: There must be at least one faultHandler -->
![](/Images/OutliningIndicators/None.gif)
<catch faultName="QName"?
![](/Images/OutliningIndicators/None.gif)
faultVariable="BPELVariableName"?
![](/Images/OutliningIndicators/None.gif)
( faultMessageType="QName" | faultElement="QName" )? >*
![](/Images/OutliningIndicators/None.gif)
activity
![](/Images/OutliningIndicators/None.gif)
</catch>
![](/Images/OutliningIndicators/None.gif)
<catchAll>?
![](/Images/OutliningIndicators/None.gif)
activity
![](/Images/OutliningIndicators/None.gif)
</catchAll>
![](/Images/OutliningIndicators/None.gif)
</faultHandlers>
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
<eventHandlers>?
![](/Images/OutliningIndicators/None.gif)
<!-- Note: There must be at least one onEvent or onAlarm. -->
![](/Images/OutliningIndicators/None.gif)
<onEvent partnerLink="NCName"
![](/Images/OutliningIndicators/None.gif)
portType="QName"?
![](/Images/OutliningIndicators/None.gif)
operation="NCName"
![](/Images/OutliningIndicators/None.gif)
( messageType="QName" | element="QName" )?
![](/Images/OutliningIndicators/None.gif)
variable="BPELVariableName"?
![](/Images/OutliningIndicators/None.gif)
messageExchange="NCName"?>*
![](/Images/OutliningIndicators/None.gif)
<correlations>?
![](/Images/OutliningIndicators/None.gif)
<correlation set="NCName" initiate="yes|join|no"? />+
![](/Images/OutliningIndicators/None.gif)
</correlations>
![](/Images/OutliningIndicators/None.gif)
<fromParts>?
![](/Images/OutliningIndicators/None.gif)
<fromPart part="NCName" toVariable="BPELVariableName" />+
![](/Images/OutliningIndicators/None.gif)
</fromParts>
![](/Images/OutliningIndicators/None.gif)
<scope
>
</scope>
![](/Images/OutliningIndicators/None.gif)
</onEvent>
![](/Images/OutliningIndicators/None.gif)
<onAlarm>*
![](/Images/OutliningIndicators/None.gif)
<!-- Note: There must be at least one expression. -->
![](/Images/OutliningIndicators/None.gif)
(
![](/Images/OutliningIndicators/None.gif)
<for expressionLanguage="anyURI"?>duration-expr</for>
![](/Images/OutliningIndicators/None.gif)
|
![](/Images/OutliningIndicators/None.gif)
<until expressionLanguage="anyURI"?>deadline-expr</until>
![](/Images/OutliningIndicators/None.gif)
)?
![](/Images/OutliningIndicators/None.gif)
<repeatEvery expressionLanguage="anyURI"?>
![](/Images/OutliningIndicators/None.gif)
duration-expr
![](/Images/OutliningIndicators/None.gif)
</repeatEvery>?
![](/Images/OutliningIndicators/None.gif)
<scope
>
</scope>
![](/Images/OutliningIndicators/None.gif)
</onAlarm>
![](/Images/OutliningIndicators/None.gif)
</eventHandlers>
![](/Images/OutliningIndicators/None.gif)
activity
![](/Images/OutliningIndicators/None.gif)
</process>
![](/Images/OutliningIndicators/None.gif)
这其中
queryLanguage表示在整个流程中的查询语言默认值为"urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0", 表示使用ws-bpel2.0并附加XPath1.0
expressionLanguage. 表示在<process>中使用的默认表达语言. 该属性的默认值为"urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"
... ...
一个ws-bpel可以使用如下的标签定义:
· <receive>允许业务过程等待相匹配的消息到达,当消息到达时该活动才可以完成,其中的<portType>是可选的,但是当<portType>以后<portType>的InputValue的类型必须和<partTypeLink>中的对应规则相符messageExcage属性也是可选的,可以与一个<replay>活动相关联.
· <reply>允许业务过程发送一个消息来回复来自于IMA的邦定消息,IMA的类型包括<receive>,<onMessage>,<onEvent>,与<recieve>相仿<messageExchange>同样用来关联消息获得方,包括上面说的三种类型
· <invoke> 允许业务流程产生一个单方面的或者是应答式的活动,这主要根据<portType>的定义
· <assign>主要用来在业务流程中分配变量的值
· <throw>产生错误并将错误抛出
· <exit>
· <wait>用于使业务流程等待一段时间
· <empty>表示不进行任何操作,这对并行操作的活动非常有帮助
· <sequence>用来定义一组活动顺序发生
· <if>可定义活动的条件状态
· <while>循环,与高级语言中的while相仿
· <repeatUntil>另一种循环,与高级语言中的until相仿
· <forEach>循环,C#有相同的定义形式
· <pick>用来等待一组消息中的任何一个到达,或者到达超时时间以后开始激发
· <flow>用来定义并行发生的动作
· <scope>用来定义嵌套的活动
· <compensate>该标签必须使用在错误处理句柄中,用来在发生错误的时候进行补偿操作
· <compensateScope> 同上,但是只能发生在特定的内部<scope>中
· <rethrow>也必须在错误处理句柄中使用,抛异常
· <validate>通过变量相关的XML或者WSDL验证变量的值
· <extensionActivity>通过该标签扩展用户自己的活动
continue ... ...