Basic Soap requests in Flex (without WSDL)

Hi,
I have just started to use Flex, so everything is really new
to me.
I am meant to write a Flex application that requests data
from a Java SOAP service which is currently written by a colleague.
We do not have a WSDL specification (yet), as the content
format is not yet agreed on and might be extended frequently (Also,
the Service will only ever be used by my flex app)
Unfortunately I could only find SOAP tutorials for Flex that
use WSDL.
It would be great if anyone could give me some ideas on how
to get started on using SOAP within Flex without the WSDL part.
Thanks a lot in advance.

Yes I think your app will perform better using remote objects, there's 
a great app to test that named Census you can get it and do your own 
tests or play with it on James Ward's blog.
Sincerely,
Michael
El 22/04/2009, a las 12:24, ijmarrero <[email protected]> escribió:
>
We are developing a middle sized application using Flex and Axis 
Webservices. On the client side we AS code generated using Flex 
Builder 3.0 and the WSDL. On the server side we have Java  code 
generated with Axis 1.3 using the same WSDL. The problems occurs 
when the server sends a 290Kb response to the Client. Flex spends 10 
seconds (obtained from mx.rpc.* log facility) in deserialing this 
SOAP message. My question is:
>
¿Could I improve the performance of the deserialization?
>
Due to the fact that this is an unaceptable delay and that we have a 
code of 70.000 lines ¿what choices we have? ¿Should we use remote ob
jects?
>
Thank you
>

Similar Messages

  • Flex sending corrupt SOAP request

    I've created a PHP5 SOAP webservice and am trying to call a
    method from flex. I get a fault from the Flex app that says
    faultString="HTTP request error"
    faultCode="Server.Error.Request"
    The SOAP request received by the server is as follows (which
    I think explains why the server responded with an error):
    <SOAP-ENV:Envelope 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">
    <SOAP-ENV:Body/>
    </SOAP-ENV:Envelope>
    It is missing all the body parameters. What could cause an
    empty request like this?
    The relevant AS:
    public var _webServiceLoaded:Boolean = false; // flag noting
    when wsdl has been loaded
    public var _myService:WebService = new WebService();
    public function initWS():void {
    _myService.wsdl = "
    http://foreignserver.com/seminar_service.wsdl";
    _myService.loadWSDL();
    _myService.echoArgs.addEventListener("result",
    echoResultHandler);
    _myService.addEventListener("fault", faultHandler);
    _myService.addEventListener('load',WSLoad);
    public function send_attendee_email():void {
    _myService.echoo("qwerty"); // should just return the same
    string we send; echoo spelled with extra o
    And my wsdl:
    <?xml version="1.0"?>
    <definitions
    xmlns="
    http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="
    http://www.w3.org/2001/XMLSchema"
    xmlns:tns="
    http://foreignserver.com/seminar_service.php"
    xmlns:soap="
    http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsdl="
    http://schemas.xmlsoap.org/wsdl/"
    xmlns:soapenc="
    http://schemas.xmlsoap.org/soap/encoding/"
    targetNamespace="
    http://foreignserver.com/seminar_service.php">
    <message name="echooInput">
    <part name="echo" type="xsd:string"/>
    </message>
    <message name="send_attendee_emailInput">
    <part name="sem_date" type="xsd:string"/>
    <part name="sem_first" type="xsd:string"/>
    <part name="sem_last" type="xsd:string"/>
    <part name="sem_title" type="xsd:string"/>
    <part name="sem_company" type="xsd:string"/>
    <part name="sem_phone" type="xsd:string"/>
    <part name="sem_email" type="xsd:string"/>
    <part name="pdf_filename" type="xsd:string"/>
    </message>
    <message name="echooOutput">
    <part name="return" type="xsd:string"/>
    </message>
    <message name="send_attendee_emailOutput">
    <part name="return" type="xsd:string"/>
    </message>
    <portType name="seminarPortType">
    <operation name="echoo">
    <input message="tns:echooInput"/>
    <output message="tns:echooOutput"/>
    </operation>
    <operation name="send_attendee_email">
    <input message="tns:send_attendee_emailInput"/>
    <output message="tns:send_attendee_emailOutput"/>
    </operation>
    </portType>
    <binding name="seminarBinding"
    type="tns:seminarPortType">
    <soap:binding xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    style="rpc" transport="
    http://schemas.xmlsoap.org/soap/http"/>
    <operation xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/"
    name="echoo">
    <input xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/">
    <soap:body xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    use="encoded" encodingStyle="
    http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/">
    <soap:body xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    use="encoded" encodingStyle="
    http://schemas.xmlsoap.org/soap/encoding/"/>
    </output>
    </operation>
    <operation xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/"
    name="send_attendee_email">
    <input xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/">
    <soap:body xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    use="encoded" encodingStyle="
    http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/">
    <soap:body xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    use="encoded" encodingStyle="
    http://schemas.xmlsoap.org/soap/encoding/"/>
    </output>
    </operation>
    </binding>
    <service name="seminarService">
    <port xmlns:default="
    http://schemas.xmlsoap.org/wsdl/soap/"
    name="seminarPort" binding="tns:seminarBinding">
    <soap:address xmlns="
    http://schemas.xmlsoap.org/wsdl/soap/"
    location="
    http://foreignserver.com/seminar_service.php"/>
    </port>
    </service>
    </definitions>

    This behavior (empty SOAP request sent to server) stemmed
    somehow from my wsdl file. I'm uncertain what the specific problem
    was, but when I rebuilt the wsdl from scratch using a different
    model, the SOAP request from Flex was properly formed.

  • How to create a standard SOAP request message from a given WSDL file?

    Hello,
    If I have a WSDL file (either from a .net web service or from the famous Amazon web services), what is the best way to generate a SOAP compliant request message?
    I am having trouble understanding the role of WSDL file in a given web service.
    Question 1:
    If I have a web service that is implemented using jaxm, how do I create/publish a WSDL file that describes the web service?
    Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)
    Question 2:
    If I have a web service that is implemented using JAX-RPC, based on the WSDL file, can I simply generate a valid SOAP message (by some JAVA api) and get the response message directly?
    thanks...

    I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
    Have you already found an answer to this?

  • How to pack attribute values in a soap request?

    Hello,
    We are trying to make an external webservice call through GWWS.
    The (soap) request contains an element which looks like:
    +<Request Version="1.0" RequestID="11111111" TypeOfRequest="type1" Echo="false">+
    +<Info>+
    +<Account xmlns="http://something.com/Domain1/">ABCD1234</Account>+
    +</Info>+
    +</Request>+
    We had created this soap request based on the WSDL provided to us by the webservice host.
    We used a tool (like soapui) to generate the the above request.
    To be able to make a service call to this webserive, we used the wsdlcvt to generate the fml32 field headers as:
    wsdlcvt -i <provided wsdl> -o <baseoutput name>
    However we could not find a way to pack in the the information related to the attributes.
    In vain, we tried to use the option [-m] with wsdlcvt.
    Since there are no field headers generated by the wsdlcvt for the attributes, we do not know how do we put values of "Version", "RequestID", "TypeofRequest", "Echo" attributes of the "Request" element in the webservice request.
    Are we missing something here?
    How can we populate/put information in the attributes of an element in a request?
    Thank you.
    Sincere Regards,
    Mrugendra

    Hello Xu,
    We have a simple test wsdl as follows
    +<?xml version="1.0" encoding="UTF-8"?>+
    +<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://new.webservice.namespace" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://new.webservice.namespace">+
    +<wsdl:types>+
    +<xsd:schema targetNamespace="http://new.webservice.namespace" xmlns="http://new.webservice.namespace" elementFormDefault="unqualified" attributeFormDefault="unqualified">+
    +<xsd:complexType name="Service_Type">+
    +<xsd:sequence>+
    +<xsd:element name="DateTime" type="xs:dateTime" nillable="true">+
    +</xsd:element>+
    +<xsd:element name="UUID" type="xs:string" nillable="true">+
    +</xsd:element>+
    +<xsd:element name="Status" nillable="true" minOccurs="0" maxOccurs="unbounded">+
    +<xsd:complexType>+
    +<xs:sequence>+
    +<xs:element name="StatusDesc" type="xs:string">+
    +</xs:element>+
    +</xs:sequence>+
    +<xsd:attribute name="StatusTyp" type="xs:string" use="required">+
    +</xsd:attribute>+
    +</xsd:complexType>+
    +</xsd:element>+
    +</xsd:sequence>+
    +<xsd:attribute name="Version" type="xs:string" use="required">+
    +</xsd:attribute>+
    +<xsd:attribute name="Name" type="xs:string" use="required">+
    +</xsd:attribute>+
    +</xsd:complexType>+
    +</xsd:schema>+
    +</wsdl:types>+
    +<wsdl:message name="GetServiceReq">+
    +<wsdl:part name="ServiceReq" type="tns:Service_Type"/>+
    +</wsdl:message>+
    +<wsdl:message name="GetServiceRes">+
    +<wsdl:part name="ServiceRes" type="tns:Service_Type"/>+
    +</wsdl:message>+
    +<wsdl:portType name="ServicePortType">+
    +<wsdl:operation name="getService">+
    +<wsdl:input message="tns:GetServiceReq"/>+
    +<wsdl:output message="tns:GetServiceRes"/>+
    +</wsdl:operation>+
    +</wsdl:portType>+
    +<wsdl:binding name="ServiceBinding" type="tns:ServicePortType">+
    +<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>+
    +<wsdl:operation name="getService">+
    +<soap:operation soapAction="getService"/>+
    +<wsdl:input>+
    +<soap:body use="literal"/>+
    +</wsdl:input>+
    +<wsdl:output>+
    +<soap:body use="literal"/>+
    +</wsdl:output>+
    +</wsdl:operation>+
    +</wsdl:binding>+
    +<wsdl:service name="Service">+
    +<wsdl:port name="getService" binding="tns:ServiceBinding">+
    +<soap:address location="No Target Adress"/>+
    +</wsdl:port>+
    +</wsdl:service>+
    +</wsdl:definitions>+
    When we create a soap request (Using soapiu) from the above wsdl we get:
    +<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
    +<soapenv:Header/>+
    +<soapenv:Body>+
    +<ServiceReq Version="?" Name="?">+
    +<DateTime>?</DateTime>+
    +<UUID>?</UUID>+
    +<!--Zero or more repetitions:-->+
    +<Status StatusTyp="?">+
    +<StatusDesc>?</StatusDesc>+
    +</Status>+
    +</ServiceReq>+
    +</soapenv:Body>+
    +</soapenv:Envelope>+
    As you can see that ServiceReq has attributes Version and Name
    However, wsdlcvt (with -m) creates the following fml32 headers
    DateTime        1       string  -       fullname=DateTime, schema=xs:dateTime
    ServiceReq      2       fml32   -       fullname=ServiceReq, schema=tns:Service_Type
    ServiceRes      3       fml32   -       fullname=ServiceRes, schema=tns:Service_Type
    Status  4       fml32   -       fullname=Status, schema=tns:Status
    StatusDesc      5       mbstring        -       fullname=StatusDesc, schema=xs:string
    UUID    6       mbstring        -       fullname=UUID, schema=xs:string
    The points that we did not understand:
    1. You mentioned: "SALT will map the *whole* request to FLD_MBSTRING
    It is not so in this case.
    Did we miss something?
    2. Going by your suggestion in your last reply how do we create the FML32 buffer (specifically for the "ServiceReq" element, with attributes) for the sample we have?
    Thank you.
    Sincere Regards,
    Mrugendra

  • SOAP RECEIVER and WSDL-what specifies how my SOAP REQUEST should look like?

    Hi
    I am sending a request to a webservice (SOAP RECEIVER) but the webservice in question does not have a wsdl. I have created my own wsdl based on another example but when mapping to the REQUEST part of this and routing it through my SOAP RECEIVER channel it appears that it has NO SOAP-ENV only the pure XML in the request sent to the webservice.
    I have UNTICKED the "No SOAP envelope.." so all is pretty basic.
    What specifies how the REQUEST sent to the webservice through the SOAP RECEIVER comm channel should look like?
    I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
    Cheers

    > I thought that the SOAP RECEIVER ADAPTER did this automatically, but in my scenariao, it looks as if it something else as well? Is it the XSD or WSDL that dictates how the SOAP REQUEST should look like?
    No. The SOAP adapter adds the SOAP enveloped, no matter how the WSDL looks like.
    I have no idea why this does not work for you. Check whether the channel is active and the cache is refreshed.
    Regards
    Stefan

  • Using SOAP without WSDL?

    Newbie to SOAP and Flex and I have a small pilot project to
    access a company's SOAP 1.1 web services. I am given the sample
    SOAP request/response messages embedded in HTTP. It seems Flex
    requires WSDL file for communication but I don't have it. Do I need
    it to work in Flex, or in general as a matter of fact.
    Thanks.

    Yes. If you do not have it, you cannot:
    -either set up the webservice class
    -or feed it to Flex Builder.
    You therefore need it (which is quite logical since it IS a contract between a server and a client...)

  • HTTP error while sending SOAP request using wsdl file

    We created SOAP request using the wsdl file ; while sending SOAP request from Altova XMLSpy, we are getting the below error.
    HTTP error: could not post file
    Can you please explain how to resolve this issue
    Regards,
    Sanghamitra

    there is very little information to help you here.
    Can you confirm if this is a SOAP sender scenario or SOAP receiver scenario?
    Also do go to thru these links to help you out;
    Troubleshooting
    Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
    RFC -> SOAP
    RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
    RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
    SOAP <-> XI <-> RFC/BAPI
    Walkthrough - SOAP  XI  RFC/BAPI

  • WSDL TO SOAP Request

    I Need to dynamically generate a SOAP request from the WSDL file.
    What should be my approach , is there any API which could help me in theis WSDL to SOAP conversion ?

    HI,
    WSDL to SOAPThere are tools like SoapUI and Altova's tools that generate sample SOAP requests for operations defined in a WSDL and I am looking to do similar thing.
    Same thing Discuss in another Forums
    http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=51&t=004863Some Related Links
    WSDL to SOAP
    http://www.iona.com/solutions/opensource/prodsol/cxf.htm
    Apache CXF 2.0
    http://incubator.apache.org/projects/cxf.htmlMessage was edited by:
    drvijayy2k2
    *********Duck**********

  • XFIRE - Java class from wsdl and soap request from java class

    Hi,
    Firstly i'm newbie programmer with little experience, so please help me if u can.
    I have found an example on how to create java classes from WSDL under maven:
    (...)<taskdef classname="org.codehaus.xfire.gen.WsGenTask" name="wsgen">(...)
    I've created the below java class and I create new object of this class: UploadChunk up = new UploadChunk()
    and up.setSomething(123) etc....
    I have some service for which I have to prepare soap request manually - suitable for my service requests.
    I'm doing it using dom4j to create xml documents and i rewrite values to it from my variable up.
    I wonder if it is possible to do it automatically - I have UploadChunk object and I want do use xFire library somehow to produce ready or almost ready soap request. I want to do it in my code, no some ant or maven task.
    So I propably need a couple line of code, when I have:
    up.setSomething(123);
    //////CONVERTION - CAN U TELL ME HOW TO DO THAT PLEASE? I haven't found the way :( it seems I need your help.
    //////Document result =....
    callService(result,namespace,qname);
    import javax.xml.bind.annotation.XmlAccessType;
    import javax.xml.bind.annotation.XmlAccessorType;
    import javax.xml.bind.annotation.XmlElement;
    import javax.xml.bind.annotation.XmlType;
    * <p>Java class for UploadChunk complex type.
    * <p>The following schema fragment specifies the expected content contained within this class.
    * <pre>
    * <complexType name="UploadChunk">
    *   <complexContent>
    *     <restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
    *       <sequence>
    *         <element name="SessionID" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/>
    *         <element name="InputFileName" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/>
    *         <element name="Buffer" type="{http://www.w3.org/2001/XMLSchema}base64Binary" minOccurs="0"/>
    *         <element name="Offset" type="{http://www.w3.org/2001/XMLSchema}long"/>
    *         <element name="BytesRead" type="{http://www.w3.org/2001/XMLSchema}int"/>
    *       </sequence>
    *     </restriction>
    *   </complexContent>
    * </complexType>
    * </pre>
    @XmlAccessorType(XmlAccessType.FIELD)
    @XmlType(name = "UploadChunk", propOrder = {
        "sessionID",
        "inputFileName",
        "buffer",
        "offset",
        "bytesRead"
    public class UploadChunk {
        @XmlElement(name = "SessionID")
        protected String sessionID;
        @XmlElement(name = "InputFileName")
        protected String inputFileName;
        @XmlElement(name = "Buffer")
        protected byte[] buffer;
        @XmlElement(name = "Offset")
        protected long offset;
        @XmlElement(name = "BytesRead")
        protected int bytesRead;
         * Gets the value of the sessionID property.
         * @return
         *     possible object is
         *     {@link String }
        public String getSessionID() {
            return sessionID;
         * Sets the value of the sessionID property.
         * @param value
         *     allowed object is
         *     {@link String }
        public void setSessionID(String value) {
            this.sessionID = value;
         * Gets the value of the inputFileName property.
         * @return
         *     possible object is
         *     {@link String }
        public String getInputFileName() {
            return inputFileName;
         * Sets the value of the inputFileName property.
         * @param value
         *     allowed object is
         *     {@link String }
        public void setInputFileName(String value) {
            this.inputFileName = value;
         * Gets the value of the buffer property.
         * @return
         *     possible object is
         *     byte[]
        public byte[] getBuffer() {
            return buffer;
         * Sets the value of the buffer property.
         * @param value
         *     allowed object is
         *     byte[]
        public void setBuffer(byte[] value) {
            this.buffer = ((byte[]) value);
         * Gets the value of the offset property.
        public long getOffset() {
            return offset;
         * Sets the value of the offset property.
        public void setOffset(long value) {
            this.offset = value;
         * Gets the value of the bytesRead property.
        public int getBytesRead() {
            return bytesRead;
         * Sets the value of the bytesRead property.
        public void setBytesRead(int value) {
            this.bytesRead = value;
    }

    Hi,
    Can u Please post the WSDL..here. I remember long back i resolved this kind of issue...when i was getting "*parameters is already defined in - - -*" while using ClientGen.
    Once i will get the WSDL may be i can recall it...
    If u have any problem in Posting the WSDL..in Forums .. then let me know I will send my E-Mail Address...
    As far as i remember ..it usually happens when we Run ClientGen task of WLS81 ON the WebService/WSDL generated by WebLogic 9.x or Above. Please let me know if this is the Case with you as well... . I remember there is a Patch for it...for WLS8 ClientGen task...I dont remember the Patch Number Exactly.
    Just For testing:
    Just Use WLS9.x ClientGen task On the Same WSDL
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    I am sure you will not see this issue... because the issue is there only with WLS8 Clientgen...
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
    Edited by: Jay SenSharma on Jan 8, 2010 4:32 PM
    Edited by: Jay SenSharma on Jan 8, 2010 4:34 PM

  • Create WSDL from SOAP request, response and endpoint URL

    We have a program that does not create WSDL for us but we do have a SOAP request, response XML file and the endpoint URL as well.
    How can I create WSDL file from these?
    If that is not possible, how can I create a Java web service client (JEE 5.0) when I have only the SOAP request and response XML and the endpoint URL? Some tutorial or any explanation to point me to the right direction would be highly appreciated.
    Thank you very much,
    Genti

    The endpoint is:
    http://servername/appname/service/rpcrouter
    and we have SOAP request and repsonse that we can build from the application but also the documentation that is provided
    The documentation says about the web service:
    Built on top of a pre-Axis version of Apache SOAP
    No WSDL support
    Uses literal encoding for Web Service calls
    Adding WSDL at the end of the endpoint does nothing at this point.
    Thank you for the reply though,

  • Calling SOAP Request from XML Spy

    I have published PLSQL web service at Oracle 10g AS.
    The web service runs at http://localhost:7201/reqProcess with processRequest as method being exposed.
    This web service takes the string as input and return XMLTYPE as out parameter.
    Now When I am trying to pass SOAP XML from XMLSPY to above url I am getting folloing errors.
    1) I get http error: couldnot post the file /reqProcess/ on server 'localhost' (500)
    2) I get SOAP Error as
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <SOAP-ENV:Fault>
                   <faultcode>SOAP-ENV:Client</faultcode>
                   <faultstring>No Deserializer found to deserialize a &apos;http://wsi.nat.zz.com/2005/06/StandardHeader/:m0:standardHeader&apos; using encoding style &apos;null&apos;. [java.lang.IllegalArgumentException]</faultstring>
                   <faultactor>/reqProcess</faultactor>
              </SOAP-ENV:Fault>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Please help..

    Hi Quwang ur help needed
    My requirement ...
    1) PLSQL as web service : I succesffuly deployed PLSQL Procedure as Web service at 10 10g. The PLSQL takes string (CLOB) as input convert that into XML and store in table and return XMLTYPE as output.
    When I am accesing PLSQL WS using browser I am able to send string (basically XML format) as a input and able to receive the result back (SOAP envelop)
    2)WS Invocation : After PLSQL WS published I need to pass the SOAP XML which is generated from XYX wsdl file to the PLSQL WS published above. For this req I was using XML Spy to test this. (In actual the clinet will be Sieble that will send SOAP XML to PLSQL WS).
    Initially I was generating the SOAP XML from XYZ.wsdl and was directly sending that to PLSQL URL. I was getting error as I described initially.
    Next I tried to generate the SOAP request from the PLSQL WS wsdl file and inside the parameter I am sending the SOAP XML as string to the IN paramater of PLSQL WS. This time I am getting some different errors. The first error is same as http error: couldnot post the file /balprocess/balprocess/operation?processRequest on server 'localhost' (500)
    and second error is SOAP fault as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <SOAP-ENV:Fault>
                   <faultcode>SOAP-ENV:Server</faultcode>
                   <faultstring>java.sql.SQLException: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00210: expected &apos;<&apos; instead of &apos;"&apos;
    Error at line 1
    ORA-06512: at "SYS.XMLTYPE", line 0
    ORA-06512: at "SCOTT.BAL_A_PROCESS", line 16
    ORA-06512: at line 1
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)</faultstring>
                   <faultactor>/balprocess/balprocess</faultactor>
              </SOAP-ENV:Fault>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    For ur reference I am pasting the PLSQL WSDL file and the SOAP request xml that I am sending to PLSQL WS URL.
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="bal_a_process"
    targetNamespace="http://bal.request.process/bal_a_process.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://bal.request.process/bal_a_process.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd1="http://bal.request.process/bal_a_process.xsd" >
    <documentation>
    WSDL for Service: bal_a_process, generated by Oracle WSDL toolkit (version: 1.1)
    </documentation>
    <types>
    <schema targetNamespace="http://bal.request.process/bal_a_process.xsd" xmlns:tns="http://bal.request.process/bal_a_process.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:dom="http://xmlns.oracle.com/2001/XMLSchema/DOM">
    <complexType name="bal_request_process_bal_a_processUser_processRequest_Out">
    <all>
    <element name="outresponsexmlOut" type="dom:org.w3c.dom.DocumentFragment"/>
    </all>
    </complexType>
    </schema>
    </types>
    <message name="processRequestOutput">
    <part name="return" type="xsd1:bal_request_process_bal_a_processUser_processRequest_Out"/>
    </message>
    <message name="processRequestInput">
    <part name="param0" type="xsd:string"/>
    </message>
    <portType name="bal_a_processPortType">
    <operation name="processRequest">
    <input message="tns:processRequestInput"/>
    <output message="tns:processRequestOutput"/>
    </operation>
    </portType>
    <binding name="bal_a_processBinding" type="tns:bal_a_processPortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <operation name="processRequest">
    <soap:operation soapAction="urn:bal-request-process-bal_a_process/processRequest"/>
    <input>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
    </input>
    <output>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
    </output>
    </operation>
    </binding>
    <service name="bal_a_process">
    <port name="bal_a_processPort" binding="tns:bal_a_processBinding">
    <soap:address location="http://localhost:7200/balprocess/balprocess"/>
    </port>
    </service>
    </definitions>
    Request I am sending to PLSLQ WS URL
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <SOAP-ENV:Body>
              <processRequest xmlns:m="urn:bal-request-process-bal_a_process" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <param0 xsi:type="xsd:string">     "<a>"aaa"</a>"     </param0>
              </processRequest>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I above SOAP request XML i m testing "<a>"aaa"</a>" as XML string. but this is also getting failed. In actual this will be SOAP XML request from some other XYZ wsdl file.
    Quwang ur help needed urgently.
    Regards

  • Blank SOAP Action in Soap Request- Portal Service calling Web Service

    Hi
    I'm trying to access an Web Service through a client portal service which was generated by NWDS. I called this service from a basic component and tried to execute the WS function after populating all the needed fields. When I started the component I encountered the following error.
    java.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method..
    I initially thought it was because I was downloading the WSDL to my local and using that in the portal service generation. Maybe not all the information about the web service was being obtained. I tried it again after generating the portal service from the WSDL online but still obtained the same error.
    Any insight on what's causing the error would be appreciated. Thanks!

    Dear expert.
    i got the same problem with Reyes. anyone can solve this issue?
    thank in advance.

  • NameSpace Prefix in SOAP Request

    How can I create SOAP Request without namespace prefix from a WSDL file.
    I am using ClientGen (WL 7.0, SP2)
    My Application doesn't accept namespace prefix.
    Thanks

    How can I create SOAP Request without namespace prefix from a WSDL file.
    I am using ClientGen (WL 7.0, SP2)
    My Application doesn't accept namespace prefix.
    Thanks

  • Implement a SOAP Request in an SSIS Package that sends a SOAP Message (Env) with Authentication Info, Receives XML FIle?

    We need a small SSIS package to pass a SOAP message to a SOAP server and receive the response xml message. 
    We have the SOAP Endpoint, SOAP Action, and SOAP Message (which contains authentication elements). They work in a Talend Data Integration job (using
    Talend's tSOAP component). A screenshot showing the Talend job and the configuration of the tSOAP component
    is attached.
    We need to implement the same thing in a Microsoft SQL Server 2012 SSIS package but haven't been able to get an SSIS Web Services task to work. 
    We haven't been able to configure it to pass the SOAP Action and SOAP Message.  
    How should this be accomplished in SSIS?
    kholberger

    I guess I was not clear.  The Talend job works perfectly (and it took only a few minutes to configure). 
    I need to replicate the SOAP request function in an SSIS package.  I've been trying to configure an SSIS Web Services Task to do that without success. 
    The SSIS Web Service Task asks for the .wsdl file, which I provide (though the Talend component
    does not ask for it), but the SSIS WST does not ask for the SOAP Action or SOAP message.  The target web service is protected by a security gateway that rejects the SSIS WST request.  Somehow, the Talend tSOAP component sends the
    SOAP message, which contains the security definition and authentication credentials (you can see part of that in the screen shot) which the endpoint accepts.
    The question is: "How does one implement a SOAP web service request in an SSIS package that sends the SOAP Message".
    Thanks.
    kholberger

  • SOA Soap request

    Hi Friends,
    Newer to soa suite 11g
    1>I have craated small soa 11g app. i send small xml request in EM and I get xml response in EM TESTER. so far good (This is NOT how internet websites work. They work in HTML rendered in browser for Request and Response)
    My question is, how does this behave in REAL world. Meaning, a website has a form that user would fill - in and submit. Then, what happens ? "Who and How" does those submitted form values get converted into XML format (ofcourse adhering to XSD) for my soa application to consume ? and How would the XML response coming from soa application again get converted into HTML so that the website user can view it in browser ?
    2> Second, if I want to collect the submitted user values and create a XML, is it sufficient to use just XML (without referring to any XSD) and let it talk to the soa application (that talks to external webservice and gets the response). If not using any xsd then how do i MAP incoming request values to reference exposed webservice WSDL ? OR is it that XSD is must for the incoming SOAP request so that data mapping can be done with the referenced WSDL ?
    thx
    pp

    Hi,
    Regarding your first question, there are two ways to achieve your desired behaviour. The first one is to create a proxy, using that proxy to create a data control using the web service you have created, and then using an adf form, create a form, that you take care of the submission. In a similar way, you can capture the response back and display it as you would like.
    You could create your own input form, and then create your xml request message (based on the web service schema) and submit it. Popular techniques include JAX-RPC, REST Services, etc. I believe this answers your second question. Calling synchronous web services is quite easy, as your just wait for a response. Calling asynchronous web services is a bit tricky if implemented programmatically.
    Antonis

Maybe you are looking for