<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>BPEL4WS - Expressions - getVariableData</title>
		<link>http://ws-engineer.wikidot.com/forum/t-936/bpel4ws-expressions-getvariabledata</link>
		<description>Posts in the discussion thread &quot;BPEL4WS - Expressions - getVariableData&quot; - Number of parameters supported</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://ws-engineer.wikidot.com/forum/t-936#post-1786</guid>
				<title>BPEL4WS - 14.1.Expressions &amp; getVariableData</title>
				<link>http://ws-engineer.wikidot.com/forum/t-936/bpel4ws-expressions-getvariabledata#post-1786</link>
				<description></description>
				<pubDate>Tue, 24 Oct 2006 20:51:39 +0000</pubDate>
				<wikidot:authorName>wsengineer</wikidot:authorName>				<wikidot:authorUserId>2107</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p> I have just found a bug in the tool for translation of "getVariableData" and the permissable "extensions"…. whilst trying some more samples I encountered<br /> a translation error on the following snipit: </p> <p> bpws:getVariableData('input','payload', '/global:PhilosopherRequest/global:iterations') </p> <p> Section 14.1 of the BPEL4WS spec <a href="http://www-128.ibm.com/developerworks/library/specification/ws-bpel/">WS-BPEL1.1</a> explains…. </p> <p> Expressions </p> <p> These extensions refer to the Expressions feature of BPEL4WS. </p> <p> The first extension defines a standard fault for erroneous use of the XPath 1.0 function defined for extracting global property values from variables. </p> <p> bpws:getVariableProperty ('variableName', 'propertyName') </p> <p> The first argument names the source variable for the data and the second is the qualified name (QName) of the global property to select from that variable (see Message Properties). If the given property does not appear in any of the parts of the variable's message type or the given property definition selects a node set of a size other than one, then the standard fault bpws:selectionFailure MUST be thrown by a compliant implementation. </p> <p> The second extension defines an additional XPath 1.0 function usable only in executable processes. This function extracts arbitrary values from variables. </p> <p> bpws:getVariableData ('variableName', 'partName', 'locationPath'?) </p> <p> The first argument names the source variable for the data, the second names the part to select from that variable, and the third optional argument, when present, provides an absolute location path (with '/' meaning the root of the document fragment representing the entire part) to identify the root of a subtree within the document fragment representing the part. The return value of this function is a node set containing the single node representing either an entire part (if the third argument is absent) or the result of the selection based on the locationPath. If the given locationPath selects a node set of a size other than one during execution, then the standard fault bpws:selectionFailure MUST be thrown by a compliant implementation. </p> <p> I am working on a patch and will roll out asap. </p>
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>