How to bind complex input/output types in web service data control

Hi,
I have created data control using external web service for simple input & output data type and its working fine.
But I don't know how it can be done for complex data types.
My external Web services have complex input & output types. Such as java object which contains another java object again it contains another java object or arry or java collection etc.
Each my service has one complex input data type and for this no user input is require so how I can do it without using any component for it.
I want to bind my page components with this input & output type.
What is the best approach to do this and how to bind screen component.
Regards,
Devang

Hi,
Thanks frank.
I already check this link before posting this so if you have any other link then kindly reply.
Regards,
Devang

Similar Messages

Binding LinkedList to ADF Web Service Data Control

Hi guys,
I would like to ask about how to bind a LinkedList (consumed from webservice) to ADF web service data control, in order to display it in JSF page. This LinkedList contains java beans that hold information I need. I've tried to ask google and search this forum, but still got no luck.
<p>
Yes I found article about dealing with complex input params, but seems not what I'm looking for.
<p>
Anybody has hint or idea on this ?
<p>
Thanks

Take a look at this blog entry from Susan Duncan: Dealing with Complex Input Params in ADF Web Service Data Controls.
It looks like what you are asking for.
Hope it helps,
-Eric

Web Services Data Control - Complex type bindings

I am calling a web services using the web service data control. The request object is a complex type. I observed that some data managed to bind but some failed to bind (empty value on the outbound SOAP payload). Specifically, all the "scalar" elements within the complex type managed to bind. For example the following element snippet within the overall complex data did not bind the value entered to the SOAP payload:
<xsd:element minOccurs="0" name="zones">
<xsd:annotation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="zone"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
While the following complex element within the same payload managed to bind value entered:
<xsd:element minOccurs="0" name="orderBy">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="orderByItem">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="fieldName"/>
<xsd:element type="xsd:boolean" name="ascending"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Any bug report of this?
Cheers
Boon

Hi Frank,
Thanks for the response. I looked further into the problem. This is what I found.
This is error message:
javax.xml.ws.soap.SOAPFaultException: Foundation Engine Error: '' is an Invalid search zone. Valid zones include: 'id_object','name','published.name','comment_text','published.comment_text','note','document_extension','published.document_extension','physical_id','file_title','published.created_by','content'
I turned on the trace and found the following message:
[SRC_METHOD: parse] [225] No XML file /ObjectiveSearch/send/params/searchRequest/searchInput/searchInfo/zones/zones.xml for metaobject ObjectiveSearch.send.params.searchRequest.searchInput.searchInfo.zones.zones
But when I looked into the model directory, I only able to find:
H:\JDeveloper\AdvancedSearch\Model\adfmsrc\ObjectiveSearch\send\params\searchRequest\searchInput\searchInfo\zones\zone.xml
It seems that WS data controller adapter is looking for zones/zones.xml. The wsdl specify zones with sub-elements(sequence) of zone (see wsdl below). The correct structure (zones/zone) is shown on the web service data control pallete and I can bind it to a JSF page.
wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:tns="urn:objective.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xi="http://www.w3.org/2001/XInclude" targetNamespace="urn:objective.com" name="searchService">
<wsp:Policy wsu:Id="WSSPortBindingInputPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding>
<wsp:Policy>
<wsp:All>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:Strict/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
</wsp:All>
</wsp:Policy>
</sp:TransportBinding>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:WssX509V3Token10/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:SignedSupportingTokens>
<wsp:Policy>
<wsp:All>
<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:NoPassword/>
</wsp:Policy>
</sp:UsernameToken>
</wsp:All>
</wsp:Policy>
</sp:SignedSupportingTokens>
<sp:Wss11>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefKeyIdentifier/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="WSSPortBindingOutputPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Always">
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:WssX509V3Token10/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:Wss11>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefKeyIdentifier/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<types>
<xsd:schema targetNamespace="urn:objective.com">
<xsd:simpleType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="logicalOperatorType">
<xsd:annotation>
<xsd:documentation>The type of join of the condition 'and' 'or'.
               </xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="and"/>
<xsd:enumeration value="or"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="expressionType">
<xsd:sequence>
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element maxOccurs="unbounded" minOccurs="0" type="tns:expressionType" name="expression"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" type="tns:metadataCondition" name="condition"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="metadataCondition">
<xsd:annotation>
<xsd:documentation>
</xsd:documentation>
</xsd:annotation>
<xsd:all>
<xsd:element type="tns:logicalOperatorType" name="logicalOperator"/>
<xsd:element type="xsd:string" name="field"/>
<xsd:element type="xsd:string" name="operator"/>
<xsd:element minOccurs="0" type="xsd:string" name="value"/>
</xsd:all>
</xsd:complexType>
<xsd:element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="searchRequest">
<xsd:annotation>
<xsd:documentation>
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:all>
<xsd:element name="searchInput">
<xsd:complexType>
<xsd:all>
<xsd:element name="searchInfo">
<xsd:complexType>
<xsd:all>
<xsd:element minOccurs="0" name="objectTypes">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" type="xsd:string" name="objectType">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:int" name="numResults">
<xsd:annotation>
<xsd:documentation>The maximum number of results to     search for.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:boolean" name="showDeleted">
<xsd:annotation>
<xsd:documentation>Show deleted objects in the search results?</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="textQuery">
<xsd:annotation>
<xsd:documentation>A Verity text query, by default the     syntax of the query is "Internet" but can also be changed     to 'Verity' via the query syntax argument.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:string" minOccurs="0" name="syntax">
<xsd:annotation>
<xsd:documentation>The syntax of the search query either
                                                                 'Internet' (default) or 'Verity'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="searchScopes">
<xsd:annotation>
<xsd:documentation>Search scopes to include in the
                                                                 search.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="searchScope"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="zones">
<xsd:annotation>
<xsd:documentation>Search zones to include in the
                                                                 search.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="zone"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element type="xsd:string" minOccurs="0" name="attributes">
<xsd:annotation>
<xsd:documentation>The attributes used when fetching
                                                                 results (these attributes are passed to inspect).
                                                            </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="behaviours">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="sections">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="orderBy">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="orderByItem">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="fieldName"/>
<xsd:element type="xsd:boolean" name="ascending"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="searchRoot">
<xsd:annotation>
<xsd:documentation>The root container of the search, for a constrained search.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="depth">
<xsd:annotation>
<xsd:documentation>The depth to traverse.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="searchResult">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="resultId">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:int" name="numberOfResults">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:boolean" name="sorted">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="sortError">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:all>
<xsd:attribute name="instanceDomain" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="searchRequest">
<part name="searchRequest" element="tns:searchRequest"/>
</message>
<message name="searchResult">
<part name="searchResult" element="tns:searchResult"/>
</message>
<portType name="searchPortType">
<operation name="send">
<input message="tns:searchRequest"/>
<output message="tns:searchResult"/>
</operation>
</portType>
<binding name="searchBinding" type="tns:searchPortType">
<wsp:PolicyReference URI="#WSSPortBindingInputPolicy"/>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="send">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<wsp:PolicyReference URI="#WSSPortBindingOutputPolicy"/>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="searchService">
<documentation>"search" service.</documentation>
<port name="searchPort" binding="tns:searchBinding">
<soap:address location="https://youContentServer:443/services/search"/>
</port>
</service>
</definitions>
Cheers
Boon

How can I create a query with web service data control?

I need to create a query with web service data control, in WSDL, it's query operation, there is a parameter message with the possible query criteria and a return message contains the results. I googled, but cannot find anything on the query with web service. I cannot find a "Named Criteria" in web service data control like normal data control. In Shay's blog, I saw the topics on update with web service data control. How can I create a query with web service data control? Thanks.

Hi,
This might help
*054. Search form using ADF WS Data Control and Complex input types*
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/index-101235.html

Dynamic pagination using inputs from a Web Service data control

I am in process of creating a pagination UI component , much similiar to the one used in Oracle forums eg: Pages: 100 [1 2 3 4 5 | Next ]
I am making use of a Web Service to get the following details for my search results :
a) Number of search result rows (100) ,
b) total number of rows to be shown on one page (5)
c) Total number of pages
I am wondering how to create the pagination UI control in my ADF Faces page and How can I bind the web service data control to the pagination component for a simple dynamic navigation
Please advice. I am new to ADF development, so looking inputs for approach to the above elucidated problem (Code not required)

Yes I am using <af:commandLink > component
<af:forEach
var="list" items="#{NavBean.list}">
<af:spacer width="5" height="10" id="s1"/>
<af:panelGroupLayout id="pgl2" layout="horizontal"
halign="center"
inlineStyle="#{list.found ? 'background-color:#aeccd8;' : 'background-color:white;'} text-align:center; width:15px; ">
<af:commandLink text="#{list.character}" id="cl1"
partialSubmit="true"
disabled="#{list.found ? false : true}"
actionListener="#{NavBean.onIndexSelected}">
<f:attribute name="indxKey" value="#{list.character}"/>
</af:commandLink>
</af:panelGroupLayout>
</af:forEach>
I have created a NavBean managed bean with some methods and foll set of instance variable:
List<IndexCharacterObject> list = null;
int startRow;
int endRow;
int pageNumber;
int numPages;
int totalRows;
I want these variables in the Managed bean class to be automatically populated from the Web Service data control .. Not sure how to go about binding these values ?

Web service data control with complex input parameter problem

Hi!
I'm making ADF web app, using JDev 11.1.1.2.0. I have to call a web service (using a data control), which has complex input parameter (array of complex objects).
I followed steps from Susan Duncan blog: http://susanduncan.blogspot.com/2006/09/dealing-with-complex-input-params-in.html , but I ran into a problem.
As Susan wrote, I changed submit's button action binding to an operation in a managed bean, which returns array of objects and everything works fine. I can call a WS and my table shows the result.
The problem is, that after I change button's action binding to my manage bean, row selection in result table doesn't work anymore (I allways get NullPointerException).
What can be done here?
Can somebody please help?

Hi,
I also have similar type of problem where I need to invoke a Web service with Complex input parameters.
I followed Susan's blog but I stuck at a point where methos getItem is created.
Can anyone tell me how to get that method for my requirement.
If possible can you guys share your solutions here.
Thanks in advance.

CAPS - how to provide two input files for a web service

Hi,
We have a web service that takes two parameters. Each of those parameters come from a different file. When we provided two files corresponding to two parameters it reads the first input file but not the second. Can you please tell us how to achieve this.
Thanks
-Rao

Hi,
In eInsight Business Process under Branching Activities you can select the "Flow Activity", using this acitivity you can achieve the solution for your problem.
Thanks,
Madan

Links to Web Service Data Control for complex data types

Hello Forum members,
Could anyone please post good reference links to docs/blogs illustrating how to create and use a Data Control for a Web Serice Proxy Client providing interfcae for a complex xml schema ?
Any help highly appreciated :)

http://blogs.oracle.com/shay/2010/05/updateinsert_with_adf_web_serv.html

Mapping input values for a web service connection to a range of cells

I've created a web service connection in Xcelsius data manager. My web service requires an array of integer as input parameter. How do I map input values for a web service connection to read from a range of cells in the spreadsheet, e.g. $A$2:$A$20, in similar way of mapping output values to write to a range of cells in the spreadsheet?
For output values of the web service, I can specify to map the output values to write to a range of cells. However, it doesn't seem to work for reading the input values.
I can map input values for each node to a single cell, e.g. $A$2, in the spreadsheet. However, when I set the "Read From" field to a range of cells, e.g. $A$2:$A$20, it only reads in the first value in the range.
Is there any way that we can do this mapping for input values as we do for output values?
Your assistance is very much appreciated.
Regards,
Van

Van,
There is a workaround for that...
Example:
My Webservice accepts input data range in a specific format with " :" symbol, i.e. 072008:082008
Now what i do is
A1 = 072008
A2 = 082008
A3 = CONCATENATE(A1,":",A2)
so A3 = 072008:082008
Now i map the input value in web service to cell A3
P.S have 2 input box components and map it to cells A1 and A2, i.e you are giving users an option to enter the range of values...then web service will capture the range and refreshes data with the range of values user entered.
hope this helps..
-Anil

Problem on ADF binding with BPEL process composed as web service

I have an ADF page which has its own EO, AM and VO (view1), after I created a web service data control for an existing BPEL process and a command button for it, I found in the binding section, the view1 doesn't contain all its table column attributes, all it has is some attributes such as attributeDef, currentRow, error etc. Can you please let me know what is missing here? What I'm trying to do is bind table attributes to BPEL input variables and call the BPEL process.
Thanks
Tony

Hi,
if you deployed this to OC4J, open EM
http://server:port/em
and get to the Web service. You can execute it from here to see if generally this is working, or if you have a proxy problem only
Frank

How do automate using two output types in an invoice based on plant

Hello,
Can you tell me how to configure automatically two output types for the same invoice.
My client has business in USA and Europe.We are using only one sales organization. But we need to print invoices in letter size and A4 size depending on whether the invoice is created in europe or in USA. So , I have created two output types, one for letter size and one for A4 size. How do I configure so that if it is based in a plant/shipping point in Europe it is printed using the A4 output type else in letter size. Please suggest.
SAPSDUSER

I do not think you can use plant/shipping point in your access sequence for invoice output on header level, unless you add these fields to header level kommunication structure and populate these fields in userexit.
You can either
1. define requirement routines for your 2 output types which are mutually exclusive (if plant = A routine 1 returns sy-subrc = 0, routine 2 returns sy-subrc <>0, if plant = B routine 1 returns sy-subrc <>0, routine 2 returns sy-subrc = 0). You can assign requirements to output type either in output determination procedure OR in the access sequence. I would do it in output determination procedure. Check transactions NACO or NACE.
OR
2. add your fields to komkbv3 communication structure, populate your fields in thsi structure in userexits which are called from the function module komkbv3_fill and then you can either use then in the access sequence for your output types or create routines as in case 1. but the logic will be a simple check statement since KOMKBV3 is available in these routines.
3. In fact you can use one output type and select your layout in the print program itself... which may be even easier for you. We use this approach to select proper layout for GEOs which may have several layouts depending on region for example... so the output type is defined per country, then layout is selected by print program. (tnapr-fonam = ..., nast-spras = proper language, set country '' to use proper decimal & date format...)
Message was edited by:
Siarhei Mahulenka

How to check current input/output rate on router subintenterface via SNMP?

How to check current input/output rate on router (2821, etc..) subintenterface via SNMP, like cacti monitoring system.
I cant find OID to make this with snmpwalk.
Or there is no way to check current load by this way? Only polling?
P.S. Ethernet subinterface, of course.
With great respect, S.A.

Hi,
Try to use:
1.3.6.1.4.1.9.2.2.1.1.6 - InBitRate
1.3.6.1.4.1.9.2.2.1.1.8 - OutBitRate
1.3.6.1.4.1.9.2.2.1.1.28 - ifDescription

How to create a new output type in inventory management

dear consultants .
how to create a new output type in inventory management...........?
please give me a solution
regards
ratan

Refer:
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/attaching-smartform-to-the-standard-transaction-2316027

How can i find differnet output types for a given sales order ?

hi all,
answer my question please........?
how can i find differnet output types for a given sales order ?

hi
check in NACO transaction if you have assigned access sequence to your output ytpes and if you have ticked checkbox "Access to output conditions" - otherwise it will not even try to access condition records.
From help :
Access to output conditions
Indicates whether the system determines the output by searching for valid
condition records.
Procedure
If you want the system to search condition records for the appropriate
output, mark the field.
Note
If you leave the field blank and if you are processing sales, shipping,
or billing documents, the system automatically determines output from
information stored in the customer master record.
regards
ravish
<b>plz reward points if helpful</b>

Is complex type request supported by web service data set?

I just installed OBIEE 11g and tried to create data models with web services. It works fine for web services that takes simple data types and returns complex data types. But if the request to the web service is a complex type, it doesn't work. On the Edit Data Set page, I selected "true" for Complex Type. After I entered WSDL url, it populated the Web Service dropdown, but not the Method dropdown. Any ideas?
The other problem I am having with web service data set is that it seems to ignore the attributes in the xml response. Only xml element is recognized.
e.g. in <trigger priority="0" font_size="0"/>, priority and font_size are ignored in the data set. Please advise. Thanks.

Hi,
In this usecase , you can DnD the <serviceOperationName>_parameters as an ADF from. Then DnD the operation as a method. The methods input arg value is automatically set to the parameterIterator.currentRow.DataProvider. This works fine.

How to bind complex input/output types in web service data control

Similar Messages

Maybe you are looking for