Hi Srinath, Basically, for data services input parameters, what we support are scalar variables and arrays. In the future, we are going to support providing complex types as input (shown in the WSDL), but that will also be converted to a set of scalar variables to be mapped into data services parameters using xpath. So at the end, for the actual service call, we won't have complex values as such.
So as you mentioned, actually array values can be given in the way as you suggested, where all the child elements from the xpath expression can be treated as array elements. Cheers, Anjana. On Thu, Jan 19, 2012 at 6:03 AM, Srinath Perera <srin...@wso2.com> wrote: > Also if I am giving the value inline, how can I express the complex types? > > --Srinath > > On Thu, Jan 19, 2012 at 6:02 AM, Srinath Perera <srin...@wso2.com> wrote: > > Couple of Qs > > > > if ESB and DS are two nodes, I assume this will do a SOAP call and still > work? > > > > if the parameter is a complex type in the ESB message, and if I refer > > to it though a XPath, will that be copied completely? > > > > for example, if the ESB message is > > > > > > <Envelope> > > <Body> > > <foo> > > <bar> > > <bar1> ... </bar1> > > ..... > > </bar> > > </foo> > > > > </Body> > > > > <Envelope> > > > > Now if I refer to this as <param xpath="//foo/bar" /> .. will that > > copy all its subelements as well? > > > > --Srinath > > > > On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka <dinu...@wso2.com> > wrote: > >> Hi All, > >> > >> We are going to develop a ESB mediator which can be shipped as a > feature and > >> once this feature is installed within ESB, the DS mediator can be used > to > >> make data services calls in-line, without making actual SOAP requests, > but > >> it will use in-memory calls to invoke data service operations. > >> > >> So this will add the capability to have .dbs file in registry or some > other > >> file location and invoke the data-service operations without deploying > the > >> .dbs as a data-service and process the response within the ESB. > >> > >> Possible mediator configuration will look as follows: > >> > >> <!-- normal request --> > >> <dsCall serviceName/servicePath="..."> <!-- > serviceName > >> is used when calling to a actually deployed data-service within current > >> service configuration & > >> > >> servicePath is used to invoke a operation from .dbs file which has not > >> deployed --> > >> <operation/resource name/path=".." /> <!-- > operation > >> name or resource path to be invoke --> > >> <params expression="xpath"> <!-- > xpath > >> expression is optional, which can be defined to take all input > parameters. > >> --> > >> <param name="name1" value="value1" /> <!-- if the > xpath > >> expression in "params" is not provided then provide the parameters in > line > >> --> > >> <param name="arrayName1" value="arrayVal1" /> > >> <param name="arrayName1" value="arrayVal2" /> > >> <param name=".." expression="xpath" /> <!-- inline > >> parameter value can be provided through xpath --> > >> <params> > >> </operation> > >> <target expression="xpath" /> <!-- > If > >> the xpath is not provided, response message after invoking the operation > >> will added as fist child element of > >> > >> the SOAP body. If an xpath expression is provided then it will set in > the > >> given location. > >> </dsCall> > >> > >> <!-- batch request --> > >> <dsCall serviceName/servicePath="..."> > >> <operation/resource name/path=".."/> > >> <params expression="xpath"> > >> <batch expression="xpath"> <!-- > xpath > >> expression can be used to define parameter set for a one batch --> > >> <param name="name1" value="value1" /> > >> <param name="arrayName1" value="arrayVal1" /> > >> <param name="arrayName1" value="arrayVal2" /> > >> <param name=".." expression="xpath" /> > >> <batch> > >> <batch ..>...</batch> > >> <params> > >> > >> </dsCall> > >> > >> <!-- boxcarring --> > >> <dsCall serviceName/servicePath="..."> > >> <boxcarring> > >> <request> > >> <operation/resource name/path=".." /> > >> <params expression="xpath"> > >> <param name="name1" value="value1" /> > >> <param name="arrayName1" value="arrayVal1" /> > >> <param name="arrayName1" value="arrayVal2" /> > >> <param name=".." expression="xpath" /> > >> <params> > >> </operation> > >> </request> > >> <request ...></request> > >> </boxcarring> > >> > >> <target expression="xpath" /> > >> > >> </dsCall> > >> > >> Appreciate any feedback and ideas. > >> > >> Regards, > >> Dinusha. > >> > >> _______________________________________________ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > > > > > > > > -- > > ============================ > > Srinath Perera, Ph.D. > > http://www.cs.indiana.edu/~hperera/ > > http://srinathsview.blogspot.com/ > > > > -- > ============================ > Srinath Perera, Ph.D. > http://www.cs.indiana.edu/~hperera/ > http://srinathsview.blogspot.com/ > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- *Anjana Fernando* Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
