Well, BPEL, as an orchestration language, defines service roles. There is a construct in BPEL called partner link, which models the conversational relationship between two (web) services. Further, it defines the role of each service in the conversation.
Imagine a scenario where a vendor exposes a service to receive orders online. Customers invoke this service to request items. After that, the vendor replies with a quote and a potential delivery date. Since it has to evaluate the order, possibly with human intervention, it doesn't reply immediately. It calls the customer service asynchronously instead. The WSDL interfaces could be something like this: <portType name="provider"> | <operation name="takeOrder"> | <input message="order"/> | </operation> | </portType> | | <portType name="customer"> | <operation name="receiveQuote"> | <input message="quote"/> | </operation> | </portType> A partner link type defines the connection between these two services. Note the two roles in the relationship and how a port type specifies the interface each service presents to the other. <plt:partnerLinkType name="buy-sell"> | <plt:role name="buyer" portType="customer"/> | <plt:role name="seller" portType="provider"/> | </plt:partnerLinkType> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909578#3909578 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909578 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
