Xmlstring as input to webservice from flex

hi ,
i want to send xml string as input to a webservice .i had a
problem with this. iam pasting the code iam using.
public var sResult:String="<?xml version='1.0'
encoding='UTF-8' ?>
<root><sample><id>8098</id><type>CD</type><unit>nm</unit></sample></root>";
<mx:WebService id="myws"
wsdl="
http://localhost:8080/myws/method?wsdl"
useProxy="false">
<mx:operation name="getCD" result="resultHandler(event)"
fault="Alert.show(event.fault.message)">
<mx:request>
<String_1> {sResult} </String_1>
</mx:request>
</mx:operation>
</mx:WebService>
<mx:Panel width="652" height="408">
<mx:Button x="368" y="2" label="Lot_id" id="mybutton"
click="myws.getCD.send()"/>
</mx:Panel>
when i use any string for sResult .it is working fine.but
when i use xml string it is giving the error SOAP request error.
i need ur help.

this is the complete trace of error iam getting
ERROR [SOAPFaultExceptionHelper] SOAP request exception
javax.xml.rpc.JAXRPCException:
org.jboss.ws.binding.BindingException:
org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: {
http://www.w3.org/2001/XMLSchema}string
type of element {
http://webservice.autoee/jaws}String_1
should be complex and contain root as a child element.
at
org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:303)
at
org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233 )
at
org.jboss.ws.binding.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:103)
at
org.jboss.ws.binding.EndpointInvocation.getRequestPayload(EndpointInvocation.java:117)
at
org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvoke rJSE.java:94)
at
org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:115)
at
org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209)
at
org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java :355)
at
org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Htt p11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.ws.binding.BindingException:
org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: {
http://www.w3.org/2001/XMLSchema}string
type of element {
http://webservice.autoee/jaws}String_1
should be complex and contain root as a child element.
at
org.jboss.ws.jaxrpc.encoding.JAXBDeserializer.deserialize(JAXBDeserializer.java:100)
at
org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:235)
... 30 more
Caused by: org.jboss.ws.jaxb.UnmarshalException: Failed to
parse source: {
http://www.w3.org/2001/XMLSchema}string
type of element {
http://webservice.autoee/jaws}String_1
should be complex and contain root as a child element.
at
org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:67)
at
org.jboss.ws.jaxrpc.encoding.JAXBDeserializer.deserialize(JAXBDeserializer.java:92)
... 31 more
Caused by: org.jboss.xb.binding.JBossXBException: Failed to
parse source: {
http://www.w3.org/2001/XMLSchema}string
type of element {
http://webservice.autoee/jaws}String_1
should be complex and contain root as a child element.
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:156)
at
org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
at
org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:63)
... 32 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {
http://www.w3.org/2001/XMLSchema}string
type of element {
http://webservice.autoee/jaws}String_1
should be complex and contain root as a child element.
at
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContent Handler.java:187)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(Sa xJBossXBParser.java:301)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch( Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:152)
... 34 more

Similar Messages

  • Calling webservice from Flex?

    Hi,
    I get the error when I call webservice from Flex.Can you tell
    me why this happen?
    Thanks
    Mark
    [RPC Fault faultString="Security error accessing url"
    faultCode="Channel.Security.Error" faultDetail="Destination:
    DefaultHTTP"]
    at mx.rpc::AbstractInvoker/
    http://www.adobe.com/2006/flex/mx/internal::faultHandler()
    at mx.rpc::Responder/fault()
    at mx.rpc::AsyncRequest/fault()
    at DirectHTTPMessageResponder/securityErrorHandler()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/redirectEvent()

    I think this means that the source of the web service does
    not have a crossdomain.xml file on it allowing access from your
    site. Try adding one to the root of the server and see if that
    fixes the problem.
    hth,
    matt horn
    flex docs

  • Problem accessing Webservices from Flex

    Hi All,
    I have created a Webservice in Abap and configured it using
    SOAMANAGER transaction. I am able to succesfully test the Web serivice which I have created in 'Soamanager ' transaction.
    But when I am calling this Webservice from Flex application I am getting an error as " FAULT : faultCode:WSDLError faultString:'Runtime exception Error #1009' faultDetail:'null' "
    We tried calling the Webservice  outside SAP from the FLex application, it is working fine.
    Please let me know how to rectify this error . It's an urgent requirement.
    Thanks and regards,
    Uma.

    hi
      when you create your destinations for your webservices in the SOAMANAGER-> Destination Template
      you would be providing wsdl url and destination , and in the below you can
      find the username and pwd that need to set , you need to select the radio buttons with logon tickets ,
    username , password , there , re-check the username and pwd by selecting the radio button with selecting the
    radio button username password ,  and even check the webservice in the WSNAVIGATOR , whether its working
    fine , and other thing is  there is situation where your webservice may work fine inthe wsnavigator  even then there would
    be some problem inthe webservice , even check this scenario.
    Thanks

  • Flex 3 : Accessing Rest Ful  Webservices from Flex

    Hi ,
    I am new to this term RestFul Webservices .
    I am using FlexBuilder 3.
    For accesing Restful web services , what is the Component Required , is it <mx:HttpService> or the
    <mx:Webservice>
    Please clarify , Thanks .

    You have to use HTTPService

  • Webservices with Flex

    Is there any way to consume webservices from flex without
    using LCDS or FDS. Thanks in advance

    Hi,
    You don't need LCDS/FDS/BlazeDS to consume a web service. All
    you need to do is to use the WebService component.
    Hope this helps.

  • Calling Web Service from Flex (to PeopleSoft)

    I'm new to Flex and web services. I've created a web service
    in PeopleSoft and successfully imported the WSDL into Flex so that
    it has contacted the PS server and returned data (using
    mx:WebService and mx:Operation code I found examples of). However,
    I have been unable to pass a parameter to the service from Flex
    using that code. I then discovered and followed the sample code in
    the Flex-generated package, but no matter what I do I cannot
    successfully supply the "myValue" in the sample shown below. Here
    is Flex's own text in my GetInfo.as file built by Flex:
    * MXML sample code:
    * First you need to map the package where the files were
    generated to a namespace, usually on the <mx:Application>
    tag, like this: xmlns:ws="com.draper.*"
    * Define the service and within its tags set the request
    wrapper for the desired operation
    * <ws:GetInfo id="myService">
    * <ws:FindID_request_var><ws:FindID_request
    Find__CompIntfc__DL_TREE_IB_CI=myValue/>
    * </ws:FindID_request_var>
    * </ws:GetInfo>
    * Then call the operation for which you have set the request
    wrapper value above, like this:
    * <mx:Button id="myButton" label="Call operation"
    click="myService.FindID_send()" />
    My code is:
    <ws:GetInfo id="userRequest">
    <ws:findID_request_var><ws:FindID_request
    Find__CompIntfc__DL_TREE_IB_CI="X"/>
    </ws:findID_request_var>
    </ws:GetInfo>
    When I try to run it, Flex is unhappy with the value I am
    assigning ("X" above) no matter what I put there. If I omit the
    double quotes and try to assign a text input field value (which is
    my goal here), it complains that it expects a double quote. If I
    put almost anything else there, it complains either:
    Initializer for 'Find__CompIntfc__DL_TREE_IB_CI'; values of
    type com.draper.Find__CompIntfc__DL_TREE_IB_CITypeShape cannot be
    represented as text.
    or, if I try this line, where I attempt to pass a text input
    field:
    <ws:FindID_request
    Find__CompIntfc__DL_TREE_IB_CI="{compID.text}"/>
    then I get:
    1067: Implicit coercion of a value of type String to an
    unrelated type com.draper:Find__CompIntfc__DL_TREE_IB_CITypeShape
    Can anyone help with this please?
    Thanks
    Jim

    Chris,
    Thanks. That is what I *was* doing, that got me all data
    returned. The parameter never gets passed in the XML. It acts as if
    a blank was passed and returns everything (just as you would expect
    in the PeopleSoft search page when you just click Find without
    specifying a key). It is expecting a partial key and will return
    all keys that match (find method).
    PS expects the key DL_CS_COMPID, and in Flex I've seen
    Find__CompIntfc__DL_TREE_IB_CI also. So I've tried:
    <mx:request>
    <!-- <DL_CS_COMPID> -->
    <Find__CompIntfc__DL_TREE_IB_CI>
    {compID.text}
    </Find__CompIntfc__DL_TREE_IB_CI>
    <!-- </DL_CS_COMPID> -->
    </mx:request>
    (You can see I currently have dl_cs_compid commented out).
    Both behave identically - they are ignored in the XML that is sent
    from Flex. Here is a sample of what was received in PS:
    <?xml version="1.0"?>
    <M540564.V1:Find__CompIntfc__DL_TREE_IB_CI
    xmlns:M540564.V1="
    http://xmlns.oracle.com/Enterprise/Tools/schemas/M540564.V1"
    xmlns:SOAP-ENV="
    http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="
    http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="
    http://www.w3.org/2001/XMLSchema-instance"/>
    I believe there should be a
    <DL_CS_COMPID>value</DL_CS_COMPID> string in there.

  • Special Character XML Web Service call from Flex

    Hi,
    Let me first give a little background.
    I have to query and return data in XML format. To do so, I have created a custom DSC component. In cases where XML has special characters, LC throws error saying that XML is not properly formed. To over come this issue I used CDATA tag at DSC component. Now LC works as it should and I returns correct result.
    I have a web service call from Flex to get this XML result. Every time i trigger this web service I get an error message saying </document> tag is missing.
    I understand in Flex, web service returned data is wrapped in CDATA tag, thats what i causing all this issue.
    I am not sure, how to handle this situation, I am sure this is a common problem and there should be ways to work around it.
    I would really appreciate if any one could point me in the right direction.
    Thank you ..

    The web service has four operations in it, I need pingQuery operation execution code since it doesnot need any input value.
    I have used code something like this.. Any one please correct me if I am wrong..
    <mx:WebService 
    <mx:WebService> id="webService" wsdl=""https://hydrogen.csd.sc.edu/axis2/services/AcademicHistoryService?wsdl
    >
    <mx:operation name="pingQuery"resultFormat="
    object"result="resultHandler(event);"
    fault="faultHandler(event);"
    >
    <mx:request>
    <PingQuerySpecification>
    <value>
    fsdf
    </value>
    </PingQuerySpecification>
    </mx:request>
    </mx:operation>
    </mx:WebService>
    private function resultHandler(evt:ResultEvent):void {Alert.show(ObjectUtil.toString(evt.result));
    private function faultHandler(evt:FaultEvent):void {Alert.show(evt.message.toString());

  • Error while calling webservice in flex

    Hi,
    I have done one sample application like adding the 2 no. But
    i dont know how to pass the parameter from webservice to flex. I
    have attached my code here. Plz reply.Its showing the error as
    Required parameter 'a' not found in input arguments."

    add this to get your reply from web service.
    private function
    configureListeners(dispatcher:IEventDispatcher):void {
    // Override xml socket event listeners with custom functions
    // Reference the XML Socket API for Event descritpions
    xml_s.addEventListener(Event.CLOSE, onClose);
    xml_s.addEventListener(Event.CONNECT, onConnect);
    xml_s.addEventListener(DataEvent.DATA, onData);
    xml_s.addEventListener(IOErrorEvent.IO_ERROR, onIOError);
    xml_s.addEventListener(SecurityErrorEvent.SECURITY_ERROR,
    onSecurityError);
    // below is where you will receive your results from the web
    service
    public function onData(event:DataEvent):void
    // do something with data
    // i.e. indata.text = event.text;

  • How can I call a stateful webservice from a user-defined XPath function?

    I'm calling a stateful webservice from a BPEL process using a PartnerLink which implements Custom Header Handler classes to handle the session state, storing the cookie as a property of the PartnerLink.
    I'd also like to call this same stateful webservice, in the same session, from a user-defined XPath function enabling me to call this from an XSL Transformation.
    Is this in any way possible? Can I access the cookie and attach it to the webservice call made by the user-defined XPath function?

    Actually, as long as the servlet returns valid javascript, you can indeed "call it" from the client. It will initiate a request and return the result to the browser.
    This example uses Perl, but it could be easily modified to go to a servlet instead.
    Note that it is only supported in DOM browsers (IE6+/NN6+/etc)
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
    <html>
    <head>
    <title> Test server-side JS </title>
    </head>
    <body>
    <script type="text/javascript">
    function checkIt(variable, value)
    var newScript = "cgi-bin/validateJS.cgi?"+variable+"="+value;
    var body = document.getElementsByTagName('body').item(0)
    var scriptTag = document.getElementById('loadScript');
    if(scriptTag) body.removeChild(scriptTag);
    script = document.createElement('script');
    script.src = newScript;
         script.type = 'text/javascript';
         script.id = 'loadScript';
         body.appendChild(script)
    </script>
    <p>Test.</p>
    <form id="f1" action="">
    <input type="text" name="t1" id="t1" onChange="checkIt(this.name, this.value)">
    </body>
    </html>
    validateJS.cgi
    #!/opt/x11r6/bin/perl
    use CGI qw(:all);
    my @valArray = split(/=/,$ENV{QUERY_STRING});
    print "Content-type: text/javascript\n\n";
    # myPass is the password
    $myPass = "foobar";
    if ("$valArray[1]" eq "$myPass")
    print "alert(\"Success!!\")";
    else
    print "alert(\"Failure!!\")";

  • How To : Call External Webservice from BPEL and pass SOAP Message to the WS

    Hello All-
    Greetings to all BPEL gurus. I am currently facing difficulties in calling an External Webservice from my BPEL Process and passing SOAP Message to it. The details are below:
    <strong>1. The BPEL process, using database polling feature of DB Adapter, will get the records from the database.</strong>
    <strong>2. Transform the message</strong>
    <strong>3. Call the External Webservice and pass the transformed message as the input to it. However the Webservice expects the BPEL process to send SOAP headers in the input message.</strong>
    I am struggling on how to put the transformed message within a SOAP envelope in the BPEL process.
    If anyone had similar requirements and have successfully been able to send SOAP messages from BPEL process to an external webservice, kindly let me know.
    Also if there is some kind of documentation or any link in the forum that I can refer, please let me know that as well.
    I am new to Webservice integration using BPEL and would really appreciate your help.
    Thanks In Advance
    Regards,
    Dibya

    Hi Dharmendra,
    I am trying to send a SOAP message from my BPEL process to a web service. I have a complete SOAP message in a complex variable defined in the wsdl for the partnerlink (web service). My problem is that when I invoke the partnerlink it fails even though the content shown in the BPEL console looks valid.
    I have set up obtunnel to see what I am actually sending out from BPEL. You mention that BPEL creates the SOAP envelope automatically.
    I think that my problem is a result of this automatic SOAP envelope that BPEL is creating. Do you know if there is a way to turn it off?
    This is what I see in the TCP monitor, please note the double SOAP env:Body:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Body> <RCMR_IN000002NR01 xmlns="urn:hl7-org:v3" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <env:Header>
    <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://testhost/CCS/Service_Endpoint</wsa:To>
    <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsa:Address>http://localhost/CCS/Service_Endpoint</wsa:Address>
    <wsa:Metadata>
    <device xmlns:hl7="urn:hl7-org:v3">
    </device>
    </wsa:Metadata>
    </env:Header>
    <env:Body>
    <RCMR_IN000002NR01>
    </RCMR_IN000002NR01>
    </env:Body>
    </RCMR_IN000002NR01>
    </env:Body>
    </env:Envelope>
    Any help is appreciated.
    Regards,
    Aagaard
    Edited by: Aagaard on Oct 30, 2008 8:59 PM
    Should have mentioned. I am using BPEL 10.1.3.4
    Edited by: Aagaard on Oct 31, 2008 8:43 AM
    I have opened a new thread for this question so as to not confuse the issue more than necessary.
    How many SOAP envelopes do you really need?

  • Calling a webservice from webdynpro ABAP.

    Hi,
    Anybody have doc/material with screenshots on calling a webservice from webdynpro ABAP (In WAS 7.0 version using service calls )  with clear steps ?
    Thanks in advance. Ponts will not be a constraint for right answers
    Praveen
    Edited by: Praveen kumar Kadi on Feb 23, 2009 11:19 AM

    Hi Praveen,
    1st Step : configure Logical Port
    http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
    2nd Step : Generate Proxy Object
    http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
    3rd Step : Instantiating the proxy object & calling the methods exposed by webservice
    data: sys_exception type ref to cx_ai_system_fault,
          sys_exception2 type ref to cx_ai_application_fault,
          client_proxy type ref to zco_myesa, "MY PROXY CLASS
          lv_ret_code type int4,
          lv_input type zsend_email_input,
          lv_response type zsend_email_response.
    data: lv_from type string,
          lv_from_address type string,
          lv_to type string,
          lv_to_address type string,
          lv_subject type string,
          lv_msg type string.
    lv_input-from = 'MYSAPTEST'.
    lv_input-from_address = '<someAddress>'.
    lv_input-to = 'Prashant'.
    lv_input-to_address = '<someAddress>'.
    lv_input-subject = ' TEST'.
    lv_input-msg_body = ' Hi this is wonderfull to see it work'.
    try.
    create object client_proxy
    exporting
    logical_port_name = 'BASIC'. " Basic is a TYPE G RFC Destination
    call method client_proxy->send_email
       exporting
         input  = lv_input
       importing
         output = lv_response    .
      catch cx_ai_system_fault  into sys_exception .
        data lv_err type string.
         lv_err = sys_exception->if_message~get_text( ).
         write: / lv_err.
      catch cx_ai_application_fault into sys_exception2  .
         lv_err = sys_exception->if_message~get_text( ).
         write: / lv_err.
    endtry.
    if lv_response is initial.
       write: /'Not Executed'.
    else.
       write: /'Did Execute'.
    endif.
    Greetings
    Prashant

  • Facing issue in invoking an external webservice from 11G Bpel

    Hi,
    I am facing an issue in Invoking PIM webservice from 11G soa.. getting the following error in the invoke activity(Invoke calls PIM webservice).. the same thing used to work in 10.1.3.4 where i set username/pwd in the bpel.xml for that partnerlink. here in 11G i did it through "Configure WS policy"     and setting oracle/wss_username_token_client_policy to true..
    the error message is
    <messages>
    <input>
    <PublicationService_GetBatchSystems_InputVariable>
    <part name="body">
    <PublicationService_GetBatchSystems>
    <batchAndLang>
    <BatchId>1543</BatchId>
    </batchAndLang>
    </PublicationService_GetBatchSystems>
    </part>
    <part name="header">
    <ServiceBean_Header/>
    </part>
    </PublicationService_GetBatchSystems_InputVariable>
    </input>
    <fault>
    <bpelFault>
    <faultType>
    <message>0</message>
    </faultType>
    <remoteFault>
    <part name="summary">
    <summary>InvalidHeader: Invalid or missing header in request.</summary>
    </part>
    <part name="detail">
    <detail>javax.xml.ws.soap.SOAPFaultException: InvalidHeader: Invalid or missing header in request.</detail>
    </part>
    <part name="code">
    <code>null</code>
    </part>
    </remoteFault>
    </bpelFault>
    </fault>
    <faultType>
    <message>0</message>
    </faultType>
    </messages>
    i compared the payload from 10G and 11G the only difference i could find is the order of soap body and header is different.. is it because of this??
    i checked in wsdlt the order is correctly declared (first header then body).. but whenever i am creating a variable on this Msg type.. and expanding the variable in jdev the order is getting reveresed.. not sure why?? there is no change in the flow from 10G to 11G.. apart from the migration.

    Thanks.. This works..
    But it gets lost whenever we redeploy that process..
    And of course even though I am seeing http user & http password can be configured in composite.xml.. It is not taking effect..
    After redeploy, still the HTTP UserName & Password is blank.
    <reference name="ABC"
    ui:wsdlLocation="ABC.wsdl">
    <interface.wsdl interface="http://oracle.abc/#wsdl.interface(WSDL_INTERFACE)"/>
    <binding.ws port="http://oracle.abc/#wsdl.endpoint(ABC/ABCHttpPort)"
    location="ABC.wsdl">
    <wsp:PolicyReference URI="oracle/wss_username_token_client_policy"
    orawsp:category="security" orawsp:status="enabled"/>
    <wsp:PolicyReference URI="oracle/log_policy" orawsp:category="management"
    orawsp:status="enabled"/>
    </binding.ws>
    <property name="oracle.webservices.auth.username" type="xs:string"
    many="false" override="may">username</property>
    <property name="oracle.webservices.auth.password" type="xs:string"
    many="false" override="may">password.xxxxx</property>
    </reference>
    Client is interested in solving only through code not through UI..
    Any thoughts..
    Edited by: Raj.Sunnyvale on Mar 24, 2010 11:26 AM

  • Problem in calling Webservice from Webdynpro ABAP

    I want to call a BAPI FM which is available in SAP ECC server when user is clicking on a button in a web dynpro application which is available in SAP Portal server.
    For example,
    Portal server name is DVP-EPP &
    ECC server name is DVP-ECC
    I have the done the following steps to achieve it,
    In Server DVP ECC:
    1) Created Web service from the standard BAPI FM (SE37-->Utilities-->More Utilities-->Create WebService --> From the the Func.Module)
    2) Downloaded the WebService as WSDL file from SOAMANAGER
    3) Tested the Web service through SE80, it is correctly calling the BAPI & creating necessary data.
    In Server DVP EPP:
    4) Created a Proxy class as follows,
    a) SE80 --> Package --> Create --> Enterprise service
    b) Selected Object type "Service Consumer"
    c) Selected Service Consumer "Local File"
    d) Browsed and selected WSDL file downloaded from DVP ECC
    e) Selected the Package, Prefix, Request, Completed the process & Activated it.
    5) Configured the Logical port as follows,
    a) Selected my Proxy class through F4
    b) Wrote a name for Logical port, Selected 'Default port' checkbox and selected 'Create'
    c) In the next screen, in 'Call parameters' tab, selected the 'URL' radio button & mentioned the URL of the WSDL-Document created in DVP-ECC system
    d) Saved the data & activated it
    5) Now, tested the service through (SE80-->Package-->Enterprise Services-->Client Proxy) option.
    6) When I test it, system prompts a dialog box for User-Name & Password (as available in DVP-ECC system).
    After the details are given, system throws the Information message as "SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/" - Exception of class CX_AI_SYSTEM_FAULT
    No record is created in DVP-ECC through the WebService BAPI.
    Please tell me whether the steps that I followed are correct as per my requirement and a solution for the above interruption.
    Thanks in advance

    Good day guys,
    Somehow I managed to resolve the above error.
    Now in DVP-EPP system, I am able to Test the Web service Client Proxy (through SE80) and a record is successfully created in destination system (DVP-ECC).
    Now, in Webdynpro I am unable to call this webservice proxy class.
    System throws the error,
    Error (id=SoapFaultCode:5): Web service processing error; more details in the
    web service error log on provider side (UTC timestamp 20141006045544;
    Transaction ID 9A144DE49C12F1B5A6B9E41F137BE3CC)
    I just created a sample WDA application and on click of a button I am calling the Webservice Proxy class as follows,
    Method on_submit_click().
    TRY.
          CREATE OBJECT wd_assist
            EXPORTING
              logical_port_name = 'ZLOG_PORT'. "Logic port creatd for Proxy class (in SOAMANAGER)
          CALL METHOD wd_assist->bus1240create     "Method available in generated Proxy Class
            EXPORTING
              input  = ls_inp                                        
            IMPORTING
              output = ls_outp.
        CATCH cx_ai_system_fault.
      ENDTRY.
    ENDMETHOD.
    Do I have to do any thing additionally in order to call the WebService in WDA?? Because, in the same system, if I test it in SE80, record is perfectly created in destination server.
    Also please suggest if I have to do any other configuration changes related to this.
    Keenly awaiting your reply.
    Have a nice day .
    Thank you.

  • Java Webservice and Flex

    Hello All,
    I am stuck at getting webservice result from flex. I have
    created a webservice which has following method:
    @WebMethod
    public String Login(@WebParam(name = "userID") String
    userID, @WebParam(name = "password") String password) {
    // TODO Store privilege and user ID in session
    String privilege =
    UserManager.getInstance().validateUserLoginInfo(userID,password);
    return privilege;
    I was getting correct response from this service(as object
    format) untill I defined
    @WebResult(name="userPrivilege") in the method. after that I
    am getting null if I defined Web service defination in flex MXML as
    follows:
    <mx:WebService id="wsLogin"
    service="NMSMainServiceService" port="NMSMainServicePort"
    wsdl="
    http://localhost:8080/NMS/NMSMainService?wsdl"
    >
    <mx:operation name="Login"
    result="loginResultHandler(event)"
    fault="loginFaultHandler(event)">
    <mx:request>
    <userID>{userID.text}</userID>
    <password>{password.text}</password>
    </mx:request>
    </mx:operation>
    </mx:WebService>
    I don't know any reason, then if I define resultFormat="xml"
    or "e4x" I do get response by event.result however I can not access
    a node in the response array or xml.
    private function loginResultHandler(event:ResultEvent):void{
    //var myXML:Array = event.result as Array;
    var can:String = event.result.LoginResponse.userPrivilege;
    Alert.show(can);
    is giving me error saying : A term is undefined. When I
    checked response in log file it is :
    <ns2:LoginResponse xmlns:ns2="
    http://service.nms.satpath.com/"
    xmlns:S="
    http://schemas.xmlsoap.org/soap/envelope/">
    <userPrivilege>manager</userPrivilege>
    </ns2:LoginResponse>
    I have created namespace too
    private var ns2:Namespace = new Namespace("
    http://service.nms.satpath.com/");
    private var S:Namespace = new Namespace("
    http://schemas.xmlsoap.org/soap/envelope/");
    but no luck.
    I would really appreciate if somone could help me this,
    please do let me know if you need any more information. Please
    help, its urgent.
    Thanks.

    Thanks for your response Sujit, however in this case I can
    not store complex results like this:
    <S:Envelope xmlns:S="
    http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <ns2:GetUsersResponse xmlns:ns2="urn:satpath/service">
    <users>
    <active>No</active>
    <address>----</address>
    <createdBy>----</createdBy>
    <department>----</department>
    <email>----</email>
    <loginID>admin</loginID>
    <phone>----</phone>
    <privilege>Manager</privilege>
    <superVisor>----</superVisor>
    <userName>----</userName>
    </users>
    <users>
    <active>No</active>
    <address>----</address>
    <createdBy>----</createdBy>
    <department>----</department>
    <email>----</email>
    <loginID>meena</loginID>
    <phone>----</phone>
    <privilege>Network Operator</privilege>
    <superVisor>----</superVisor>
    <userName>----</userName>
    </users>
    </ns2:GetUsersResponse>
    </S:Body>
    </S:Envelope>
    Actually I have a data grid in which I am displaying results
    obtained by web service, result is a bean which has all the details
    related to a user in the system like userName, loginID, Address,
    phone etc. I am getting all the result and displaying them by
    <mx:Datagrid dataprovider="myService.myOperation.lastResult"
    > and its working fine.
    Now I want to display 3 columns (user name, log in id and
    user privilege) when I click on one row I want to use states and
    transictions so that I can display user deatils (all other
    information obtained from the web service) for that I have to store
    the result somewhere possibly in a bean so that I can fetch it in
    the changed state( which is user detail) based on user has selected
    which row.
    I don't know how can I store the result in the bean at flex
    side, if I declare resultFormat as object I am unable to typecast
    it in some collection, if I take xml as result format soap headers
    are creating problem. Or should I follow some other approach?
    Please help its really urgent.
    Thanks for all the help & support.

  • Consume webservice from ABAP : SoapFaultCode:4

    Hi ,
        I need your valuable ideas in overcoming the problem mentioned below.
        This problem relates to consumption of a webservice from ABAP - Client Proxy without XI. The system is WAS 6.40.
    I had created a client proxy (along with the corresponding methods) using a WSDL file pasted below. I had also created a logical port for the proxy class generated.
    When I test the interface for one of the methods , I get the following error message.
    <u>Error Message</u>
    <?xml version="1.0" encoding="utf-8" ?>
    - <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    - <asx:values>
      <SYSTEMFAULT href="#o103" />
      </asx:values>
    - <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
    - <cls:CX_AI_SYSTEM_FAULT id="o103">
    - <CX_ROOT>
      <TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
      <PREVIOUS />
      <KERNEL_ERRID />
    - <INTERNAL_SOURCE_POS>
      <PROGID>193</PROGID>
      <CONTID>1050</CONTID>
      </INTERNAL_SOURCE_POS>
      </CX_ROOT>
      <CX_STATIC_CHECK />
    - <CX_AI_SYSTEM_FAULT>
      <CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
      <CODE>SoapFaultCode:4</CODE>
      <ERRORTEXT>System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: //10.136.129.245/PinnacleWebServices/DatabaseAvailable. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</ERRORTEXT>
      <LANGUAGE />
      </CX_AI_SYSTEM_FAULT>
      </cls:CX_AI_SYSTEM_FAULT>
      </asx:heap>
      </asx:abap>
    <u>WDSL file used for creating the Client Proxy</u>
    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="//10.136.129.245/PinnacleWebServices" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="//10.136.129.245/PinnacleWebServices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
       <wsdl:types>
          <s:schema elementFormDefault="qualified" targetNamespace="//10.136.129.245/PinnacleWebServices">
             <s:element name="DatabaseAvailable">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="DatabaseAvailableResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="DatabaseAvailableResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddCustomers">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddCustomersResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddCustomersResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddContracts">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddContractsResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddContractsResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddInstalledEquipment">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddInstalledEquipmentResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddInstalledEquipmentResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddProducts">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddProductsResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddProductsResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddCreditAlerts">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                      <s:element minOccurs="1" maxOccurs="1" name="bool_updatecustomers" type="s:boolean" />
                      <s:element minOccurs="1" maxOccurs="1" name="bool_updatecontracts" type="s:boolean" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddCreditAlertsResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddCreditAlertsResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddStockFigures">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                      <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="AddStockFiguresResponse">
                <s:complexType>
                   <s:sequence>
                      <s:element minOccurs="0" maxOccurs="1" name="AddStockFiguresResult" type="s:string" />
                   </s:sequence>
                </s:complexType>
             </s:element>
             <s:element name="string" nillable="true" type="s:string" />
          </s:schema>
       </wsdl:types>
       <wsdl:message name="DatabaseAvailableSoapIn">
          <wsdl:part name="parameters" element="tns:DatabaseAvailable" />
       </wsdl:message>
       <wsdl:message name="DatabaseAvailableSoapOut">
          <wsdl:part name="parameters" element="tns:DatabaseAvailableResponse" />
       </wsdl:message>
       <wsdl:message name="AddCustomersSoapIn">
          <wsdl:part name="parameters" element="tns:AddCustomers" />
       </wsdl:message>
       <wsdl:message name="AddCustomersSoapOut">
          <wsdl:part name="parameters" element="tns:AddCustomersResponse" />
       </wsdl:message>
       <wsdl:message name="AddContractsSoapIn">
          <wsdl:part name="parameters" element="tns:AddContracts" />
       </wsdl:message>
       <wsdl:message name="AddContractsSoapOut">
          <wsdl:part name="parameters" element="tns:AddContractsResponse" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentSoapIn">
          <wsdl:part name="parameters" element="tns:AddInstalledEquipment" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentSoapOut">
          <wsdl:part name="parameters" element="tns:AddInstalledEquipmentResponse" />
       </wsdl:message>
       <wsdl:message name="AddProductsSoapIn">
          <wsdl:part name="parameters" element="tns:AddProducts" />
       </wsdl:message>
       <wsdl:message name="AddProductsSoapOut">
          <wsdl:part name="parameters" element="tns:AddProductsResponse" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsSoapIn">
          <wsdl:part name="parameters" element="tns:AddCreditAlerts" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsSoapOut">
          <wsdl:part name="parameters" element="tns:AddCreditAlertsResponse" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresSoapIn">
          <wsdl:part name="parameters" element="tns:AddStockFigures" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresSoapOut">
          <wsdl:part name="parameters" element="tns:AddStockFiguresResponse" />
       </wsdl:message>
       <wsdl:message name="DatabaseAvailableHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
       </wsdl:message>
       <wsdl:message name="DatabaseAvailableHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddCustomersHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddCustomersHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddContractsHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddContractsHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddProductsHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddProductsHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
          <wsdl:part name="bool_updatecustomers" type="s:string" />
          <wsdl:part name="bool_updatecontracts" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresHttpGetIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresHttpGetOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="DatabaseAvailableHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
       </wsdl:message>
       <wsdl:message name="DatabaseAvailableHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddCustomersHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddCustomersHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddContractsHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddContractsHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddInstalledEquipmentHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddProductsHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddProductsHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
          <wsdl:part name="bool_updatecustomers" type="s:string" />
          <wsdl:part name="bool_updatecontracts" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddCreditAlertsHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresHttpPostIn">
          <wsdl:part name="s_dbalias" type="s:string" />
          <wsdl:part name="s_xml" type="s:string" />
       </wsdl:message>
       <wsdl:message name="AddStockFiguresHttpPostOut">
          <wsdl:part name="Body" element="tns:string" />
       </wsdl:message>
       <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesSoap">
          <wsdl:operation name="DatabaseAvailable">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
             <wsdl:input message="tns:DatabaseAvailableSoapIn" />
             <wsdl:output message="tns:DatabaseAvailableSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
             <wsdl:input message="tns:AddCustomersSoapIn" />
             <wsdl:output message="tns:AddCustomersSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
             <wsdl:input message="tns:AddContractsSoapIn" />
             <wsdl:output message="tns:AddContractsSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
             <wsdl:input message="tns:AddInstalledEquipmentSoapIn" />
             <wsdl:output message="tns:AddInstalledEquipmentSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
             <wsdl:input message="tns:AddProductsSoapIn" />
             <wsdl:output message="tns:AddProductsSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
             <wsdl:input message="tns:AddCreditAlertsSoapIn" />
             <wsdl:output message="tns:AddCreditAlertsSoapOut" />
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
             <wsdl:input message="tns:AddStockFiguresSoapIn" />
             <wsdl:output message="tns:AddStockFiguresSoapOut" />
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpGet">
          <wsdl:operation name="DatabaseAvailable">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
             <wsdl:input message="tns:DatabaseAvailableHttpGetIn" />
             <wsdl:output message="tns:DatabaseAvailableHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
             <wsdl:input message="tns:AddCustomersHttpGetIn" />
             <wsdl:output message="tns:AddCustomersHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
             <wsdl:input message="tns:AddContractsHttpGetIn" />
             <wsdl:output message="tns:AddContractsHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
             <wsdl:input message="tns:AddInstalledEquipmentHttpGetIn" />
             <wsdl:output message="tns:AddInstalledEquipmentHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
             <wsdl:input message="tns:AddProductsHttpGetIn" />
             <wsdl:output message="tns:AddProductsHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
             <wsdl:input message="tns:AddCreditAlertsHttpGetIn" />
             <wsdl:output message="tns:AddCreditAlertsHttpGetOut" />
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
             <wsdl:input message="tns:AddStockFiguresHttpGetIn" />
             <wsdl:output message="tns:AddStockFiguresHttpGetOut" />
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpPost">
          <wsdl:operation name="DatabaseAvailable">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
             <wsdl:input message="tns:DatabaseAvailableHttpPostIn" />
             <wsdl:output message="tns:DatabaseAvailableHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
             <wsdl:input message="tns:AddCustomersHttpPostIn" />
             <wsdl:output message="tns:AddCustomersHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
             <wsdl:input message="tns:AddContractsHttpPostIn" />
             <wsdl:output message="tns:AddContractsHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
             <wsdl:input message="tns:AddInstalledEquipmentHttpPostIn" />
             <wsdl:output message="tns:AddInstalledEquipmentHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
             <wsdl:input message="tns:AddProductsHttpPostIn" />
             <wsdl:output message="tns:AddProductsHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
             <wsdl:input message="tns:AddCreditAlertsHttpPostIn" />
             <wsdl:output message="tns:AddCreditAlertsHttpPostOut" />
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
             <wsdl:input message="tns:AddStockFiguresHttpPostIn" />
             <wsdl:output message="tns:AddStockFiguresHttpPostOut" />
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesSoap" type="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
          <wsdl:operation name="DatabaseAvailable">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/DatabaseAvailable" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCustomers" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddContracts" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddInstalledEquipment" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddProducts" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCreditAlerts" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddStockFigures" style="document" />
             <wsdl:input>
                <soap:body use="literal" />
             </wsdl:input>
             <wsdl:output>
                <soap:body use="literal" />
             </wsdl:output>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
          <http:binding verb="GET" />
          <wsdl:operation name="DatabaseAvailable">
             <http:operation location="/DatabaseAvailable" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <http:operation location="/AddCustomers" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <http:operation location="/AddContracts" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <http:operation location="/AddInstalledEquipment" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <http:operation location="/AddProducts" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <http:operation location="/AddCreditAlerts" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <http:operation location="/AddStockFigures" />
             <wsdl:input>
                <http:urlEncoded />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
          <http:binding verb="POST" />
          <wsdl:operation name="DatabaseAvailable">
             <http:operation location="/DatabaseAvailable" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCustomers">
             <http:operation location="/AddCustomers" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddContracts">
             <http:operation location="/AddContracts" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddInstalledEquipment">
             <http:operation location="/AddInstalledEquipment" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddProducts">
             <http:operation location="/AddProducts" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddCreditAlerts">
             <http:operation location="/AddCreditAlerts" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="AddStockFigures">
             <http:operation location="/AddStockFigures" />
             <wsdl:input>
                <mime:content type="application/x-www-form-urlencoded" />
             </wsdl:input>
             <wsdl:output>
                <mime:mimeXml part="Body" />
             </wsdl:output>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:service name="Pinnacle_x0020_Web_x0020_Services">
          <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesSoap" binding="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
             <soap:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
          </wsdl:port>
          <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
             <http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
          </wsdl:port>
          <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
             <http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
          </wsdl:port>
       </wsdl:service>
    </wsdl:definitions>
    Thanks in advance.

    Hi Raja,
                  Thanks for your prompt reply. I tried changing in the WSDL file the SOAP action parameters (http) like you said and still I got the same error message while testing the interface.
                  I have corrected the problem by trying a different approach. Earlier I used file option for Client Proxy creation and I got the error message.
    Now I created the Client Proxy by using the option URL/HTTP destination ( which was also showing errors earlier but it is OK now after our Network Specialists opened the concerned port.)
                    Your reply was usefull as it helped me to check the  "Soap Action" in the "OPERATIONS" tab of the "LOGICAL PORT" for the client proxy. I have awarded the points for that.
                    I have seen your Blogs and the your replies to the questions in this form. I would like to thank you and all the like minded contributors of this forum. Keep up the good work.
    Regards.
    François

Maybe you are looking for

  • Downloads of Legacy HP Laserjet drivers for Win 7 32 bit

    Using the Win 7 update function to automatically download the needed printer drivers does not meet my needs.  I am a volunteer who provides support to shut-ins and handicapped individuals who may or may not have any access to the Internet.  So, I nee

  • Adding PDF-document in portal

    hi there, we will start with our portal in 2 weeks. (ESS). i have some documentation for users in PDF-files. what is the easiest way to put a link into the portal to display the pdf's via acrobat reader ? where this documents can be stored ? best reg

  • Shortcut to show the Page Thumbnail panel

    I want to know if there's a keyboard shortcut equivalent to clicking the Page Thumbnails button to show the Page Thumbnails panel, and if so - what is it? I'm constantly clicking the Page Thumbs button. A keystroke would be great to have. BEFORE CLIC

  • Need help with formulae

    Post Author: Charles Denight CA Forum: Formula I work for a Tribal casino and I'm using CR to analyze play, using revenue figures we call theoretical win (Twin) and cash in. Both measure currency.  I'm new to this. I'm making a lot of customer lists

  • Does anyone know when ASA Version 8.0 will be released?

    Any info is appreicated