[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: NCName restriction to avoid "." (was: [Fwd: BPEL Schema question])
+1 from me ;)
This would also apply to the implicit variables created by a
<fromPart> nested within an onEvent.
I'll open an issue on this. From: Alex Yiu [mailto:alex.yiu@oracle.com] Sent: Sunday, June 04, 2006 5:38 PM To: wsbpeltc Cc: Mark Ford; Alex Yiu Subject: NCName restriction to avoid "." (was: [Fwd: BPEL Schema question]) Hi guys, Mark has the following suggestion to use the data type other than NCName to restrict the "." usage in variable names. I am OK with it. Thought? Thanks! Regards, Alex Yiu -------- Original Message --------
Hi Alex, What do you think about changing the data type of a variable's name to be a restriction of NCName to disallow the "." as described in Section 8.1? The dot is a legal value for NCNames but disallowed for Xpath binding purposes of message variables. This also applies to the name of the counter attribute on a <forEach>. I'd prefer to catch these types of errors with the XSD as opposed to having to write code to catch them during static analysis. Thanks. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]