[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - 11 Your opinion requested
Message text written by Danny van der Rijn > neither proposal was meant to do the things that XSLT can do. i fully support the issue to add XSLT support to BPEL. however, there is, IMO, a great need for something to provide small, local manipulations to XML trees. something along the lines of the <assign> activity, but not quite so crippled. XSLT is too heavyweight to use for a simple append operation, for instance. <<<<<<<<<<<<<<<<<< Danny, The ExternalMapping section of CAM could be utilized for this - where you are simply moving content around, there's also a set of manipulation functions if modest rendering is needed. The <AssemblyStructure> section can be used to reference the structure layout(s) as needed - and could reference an XSD. Here's an example of the mapping section, using XPath locators for the source and target locations: <ExternalMapping> <ContentAssociation> <Description>Product List</Description> <InputSource input="as:default" structure="as:default"/> <OutputStore type="XML" location="as:product_table"/> <RulesSet> <MapRule output="/Products_List/*" input="@STARTGRP()"/> <MapRule output="type" input="Sales/Company/Year/Qtr/Product@type"/> <MapRule output="name" input="@trim(Sales/Company/Year/Qtr/Product/Item@name)"/> <MapRule output="manufacturer" input="Sales/Company/Year/Qtr/Product/Item@manufacturer"/> <MapRule output="value" input="Sales/Company/Year/Qtr/Product/Item@value"/> <MapRule output="sold" input="Sales/Company/Year/Qtr/Product/Item@sold"/> <MapRule output="Products_List" input="@ENDGRP()"/> </RulesSet> </ContentAssociation> </ExternalMapping> Thanks, DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]