Re: [wsbpel] Issue - 11 Your opinion requested

[David RR Webber - XML ebusiness <Gnosis_@compuserve.com>]

Danny,

OK!  I'm having to piece together the requirements here having
not read every message in toto.

My sudden and instant thought is that if the input and output are
the same - and you want to change some content - say confirm
an order and mark the supplier name and item price :- then you 
specify that like this:

<ExternalMapping>
 <ContentAssociation>
  <Description>Product List</Description>
  <InputSource input="as:default" structure="as:default"/>
  <OutputStore type="XML" location="as:InputSource"/>
  <RulesSet>
   <MapRule output="/Products_List/*" input="@STARTGRP()"/>
   <MapRule output="type"
	input="CONFIRMED"/>
   <MapRule output="manufacturer"
	input="YOUR BEST PRICE INC"/>	
   <MapRule output="value"
	input="/Product/Item@bidprice"/>
   <MapRule output="currency"
	input="USD"/>
   <MapRule output="Products_List" input="@ENDGRP()"/>
  </RulesSet>
 </ContentAssociation>
</ExternalMapping>

and so forth.  If you need a lookup - then the @lookup() function
can be configured to pull external output from a local source
(such as RDBMS lookup of price based on partnumber, et al).

I suspect the @lookup() function also covers off the multiple
input source requirement in practice - since there's normally
a chunk of master driver data - and then ancillary content that
is referenced from there...

Thnaks, DW.

Message text written by Danny van der Rijn
> 
david-

this looks interesting, but i still don't see the manipulations happening
"in-place."  i'm probably not understanding this well enough, but it looks
like a new XML output structure is being created.

don't get me wrong - if something is out there that can do fine-grained
manipulations in-place, then i'd propose to fully do away with <assign>

danny
<