[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue 11 - Call for Discussion
That makes sense. The <remove> construct would be relevant as well. Setting an attribute regardless of it is there or not would probably not work in <copy> according to the current semantics since the XPath expression in the "query" attribute must always select one node, which would not be the case if there was no attribute node on the element already. I am not sure if assigning attributes is supported or not; I could not find anything in the specification that either specifically states that attribute assignment is supported or not. Kristofer -----Original Message----- From: Danny van der Rijn [mailto:dannyv@tibco.com] Sent: Monday, February 23, 2004 6:25 PM To: 'Wsbpel@Lists. Oasis-Open. Org (E-mail)' Subject: Re: [wsbpel] Issue 11 - Call for Discussion i would think that in that case, you would use <copy> (if it's supported). i will defer the question of whether that would work in <copy> to those who know better. danny ----- Original Message ----- From: "Kristofer Agren" <kagren@pakalert.com> To: "'Danny van der Rijn'" <dannyv@tibco.com>; "'Wsbpel@Lists. Oasis-Open. Org (E-mail)'" <wsbpel@lists.oasis-open.org> Sent: Monday, February 23, 2004 3:20 PM Subject: RE: [wsbpel] Issue 11 - Call for Discussion > Could this handle attribute assignment as well? > > For example > > <assign> > <append> > <from expression="'my value'"/> > <to variable="myVariable" > select="/ns:myElement/@ns:myAttribute"/> > </append> > </assign> > > For attributes, you rarely want to use positioned inserts, though, and most > of the times you simply want to "set" an attribute regardless if the > attribute node is there or not. > > Kristofer > > -----Original Message----- > From: Danny van der Rijn [mailto:dannyv@tibco.com] > Sent: Monday, February 23, 2004 1:29 PM > To: 'Wsbpel@Lists. Oasis-Open. Org (E-mail)' > Subject: [wsbpel] Issue 11 - Call for Discussion > > maybe people are as tired of discussing issue 11 as I am, but if it stays > this quiet, I may just have to put up a proposal for vote. Here's the > current proposal, which includes additions inspired by Glenn Mi. > > > under the <assign> element, there will be 6 possible > elements, where now there is only 1. > > <copy> > <from/> > <to/> > </copy> > as current. > ----------------------------- > <insertBefore> > <from/> > <to select="XPath Expression evaluates to one node"/> > </insertBefore> > > creates a sibling before the select expression > ----------------------------- > <insertAfter> > <from/> > <to select="XPath Expression evaluates to one node"/> > </insertAfter> > > creates a sibling after the select expression > ----------------------------- > <append> > <from/> > <to select="XPath Expression evaluates to one node" > child="integer XPath expression"? /> > <append> > > creates a child of select expression at the child-th position. child > defaults to last(). > ----------------------------- > <remove select="XPath expression evaluates to one node"?> > > removes a node > > ----- Original Message ----- > From: "Danny van der Rijn" <dannyv@tibco.com> > To: "'Wsbpel@Lists. Oasis-Open. Org (E-mail)'" <wsbpel@lists.oasis-open.org> > Sent: Wednesday, February 18, 2004 5:10 PM > Subject: Re: [wsbpel] Issue 11 - It's Baaaack > > > > > > ----- Original Message ----- > > From: "Glenn Mi" <gmi@collaxa.com> > > To: "Danny van der Rijn" <dannyv@tibco.com>; "'Wsbpel@Lists. Oasis-Open. > Org > > (E-mail)'" <wsbpel@lists.oasis-open.org> > > Sent: Wednesday, February 18, 2004 4:54 PM > > Subject: RE: [wsbpel] Issue 11 - It's Baaaack > > > > > > > Danny: > > > > > > I start to like your proposal more now. Two points I want to add: > > > > > > 1) In your <to> construct, it seems that we can just use > > > one of > > > > > > <to variable="ncname" property="qname"/> and > > > <to variable="ncname" part="ncname"? query="queryString"?/> > > > > > > Or does your select="XPath Expression evaluates to one node" > > > actually mean the normal to-spec construct ? > > > > yes. the normal to-spec, but restricted to variables, and their parts. > > i.e. not partnerlinks, etc. in the spec, this is the "first" form of the > > to-spec referred to in 9.3, and extended for executable processes in 14.3 > > > > > > > > 2) And there are cases to insert and remove part of a message variable > > > (varable defined as <variable name="abc" messageType="ns:xyz"/>). In > those > > > cases you don't need query string and you don't care about the order. > > > So it make sense to have something like: > > > > > > <insert> > > > <from .../> > > > <to variable="abc" part="def"/> > > > </insert> > > > > unless i'm mistaken, <copy> can be used here. > > > > > > > > and > > > > > > <remove variable="abc" part="def"/>. > > > > you are correct. this should be added. i believe that this is the only > one > > of the new 4, though, that should have "select" be optional. > > > > > > > > > > > > > Glenn > > > > > > -----Original Message----- > > > From: Danny van der Rijn [mailto:dannyv@tibco.com] > > > Sent: Wednesday, February 18, 2004 3:19 PM > > > To: 'Wsbpel@Lists. Oasis-Open. Org (E-mail)' > > > Subject: Re: [wsbpel] Issue 11 - It's Baaaack > > > > > > > > > to preempt the pedantic among us, there's a copy/paste error in the > > > proposal. it should read: > > > "under the <assign> element, there will be 5 possible elements, where > now > > > there is only 1." > > > > > > ----- Original Message ----- > > > From: "Danny van der Rijn" <dannyv@tibco.com> > > > To: "'Wsbpel@Lists. Oasis-Open. Org (E-mail)'" > > <wsbpel@lists.oasis-open.org> > > > Sent: Wednesday, February 18, 2004 3:16 PM > > > Subject: [wsbpel] Issue 11 - It's Baaaack > > > > > > > > > > during today's conference call, we took a straw poll, where > > approximately > > > > 2/3 voted to attempt to resolve issue 11. (i'll leave the exact count > > to > > > > the minutes). i would like to resurrect a large part of my previous > > > > proposal (i'll drop "rename"). to me, this is a viable proposal, and > i > > > > would be satisifed if it ended up being adopted into the spec. > however, > > > > maybe in the months since we last thought about it, someone else has a > > > > reasonable alternative. > > > > > > > > danny > > > > > > > > My proposal: under the <assign> element, there will be 6 possible > > > > elements, where now there is only 1. > > > > > > > > <copy> > > > > <from/> > > > > <to/> > > > > </copy> > > > > as current. > > > > ----------------------------- > > > > <insertBefore> > > > > <from/> > > > > <to select="XPath Expression evaluates to one node"/> > > > > </insertBefore> > > > > > > > > creates a sibling before the select expression > > > > ----------------------------- > > > > <insertAfter> > > > > <from/> > > > > <to select="XPath Expression evaluates to one node"/> > > > > </insertAfter> > > > > > > > > creates a sibling after the select expression > > > > ----------------------------- > > > > <append> > > > > <from/> > > > > <to select="XPath Expression evaluates to one node" > > > > child="integer XPath expression"? /> > > > > <append> > > > > > > > > creates a child of select expression at the child-th position. child > > > > defaults to last(). > > > > ----------------------------- > > > > <remove select="XPath expression evaluates to one node"> > > > > > > > > removes a node > > > > > > > > > > > > To unsubscribe from this mailing list (and be removed from the roster > of > > > the OASIS TC), go to > > > > > > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. > > > php. > > > > > > > > > > > > > To unsubscribe from this mailing list (and be removed from the roster of > > the > > > OASIS TC), go to > > > > > > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. > > > php. > > > > > > > > > > > > > > > > > > To unsubscribe from this mailing list (and be removed from the roster of > > the OASIS TC), go to > > > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. > php. > > > > > > > > > To unsubscribe from this mailing list (and be removed from the roster of > the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. > php. > > > > > To unsubscribe from this mailing list (and be removed from the roster of the > OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. > php. > > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. php. > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]