[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Fw: [wsbpel] Issue - 157 - conf call brief recap ... and carry forward ...
Hi Ron, Right, you would also have child elements separating
the text (as per Alex’s elaboration of my example, thanks Alex). What
I was getting at is that there are many cases where /a/b/text() would produce
more than one text node (or zero) and produce a selectionFailure. On your second point… Hmmm, I
am not sure what you mean by target variable. Do you mean the result of
the <to>, which could be an EII, AII or TII? If so then I think we
are on the same page and yes I agree with your statement. It shows why
the replace part of the <copy> description should be described as replace
contents, since you treat the return of <to> as a variable of some xml
type itself. If I have an element of type xsd:int and an attribute of type
xsd:int, I should be able to copy from that source element to that attribute or
vice versa. This is at the heart of the table that Alex produced. - Chris From: Ron Ten-Hove [mailto:Ronald.Ten-Hove@Sun.COM] Chris, "Character data is grouped into text nodes. As
much character data as possible is grouped into each text node: a text node
never has an immediately following or preceding sibling that is a text node.
The string-value of a
text node is the character data. A text node always has at least one character
of data." [XPath 1.0 Section 5.7 Text Nodes] Back to Rania's question: the
inability to insert infoset items, of whatever flavour, into the target is a
basic restriction of the <copy> mechanism. I must have a target variable
that has virtually exactly same XML form (morphology) as the desired
end-result. Is this a fair statement, do you think? Hi Rania,
It would result in a selectionFailure as there are no text nodes beneath element a. Also in other cases you may end up with more than one text node which could cause a selectionFaiilure. For example using CDATA for part of an elements text to avoid escaping characters, the following case may return 3 text nodes:
<a> ... <![CDATA[...bunch of characters I don't want to escape...]]> ... </a>
- Chris
-----Original Message----- From: Rania Khalaf [mailto:rkhalaf@watson.ibm.com] Sent: Monday, June 20, 2005 9:59 AM To: Alex Yiu Cc: rkhalaf@us.ibm.com; Charlton Barreto; wsbpeltc; jwillis@exchange.microsoft.com Subject: Re: Fw: [wsbpel] Issue - 157 - conf call brief recap ... and carry forward ...
Hi Alex,
In the discussion on the call, someone mentioned that 'text' can be used to get to the value of an attribute or the CDATA children of an element (the 123 of <a>123</a>).
What happens if I used it on an element <a/> ? If I am trying to copy '123' into '<a/>' to get <a>123</a>, does this cause selectionFailure ?
thanks, Rania
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]