Hi Alex,

Do you want me to replace URLLoader.load with DirectHTTPChannel.createURLRequest ?

Thanks,
Serkan

17.01.2019 06:24 tarihinde Serkan Taş yazdı:
I can say that server side does not get data, so I am sure that it is not sent.

The point is where it is lost.

I am going to check your point.

Thanks,
Serkan

Android için Outlook <https://aka.ms/ghei36> uygulamasını edinin




On Wed, Jan 16, 2019 at 11:42 PM +0300, "Alex Harui" <aha...@adobe.com <mailto:aha...@adobe.com>> wrote:

    Try DirectHTTPChannel’s createURLRequest.

    *From: *Alex Harui <aha...@adobe.com>
    *Reply-To: *"users@royale.apache.org" <users@royale.apache.org>
    *Date: *Wednesday, January 16, 2019 at 12:22 PM
    *To: *"users@royale.apache.org" <users@royale.apache.org>
    *Subject: *Re: Work on Emulation

    I haven’t looked at the code, but I would imagine data was set on
    the request before it got passed into load?  Or data is set on the
    URLLoader by some other code and you can set a breakpoint on the
    data setter.

    -Alex

    *From: *Serkan Taş <serkan....@likyateknoloji.com>
    *Reply-To: *"users@royale.apache.org" <users@royale.apache.org>
    *Date: *Wednesday, January 16, 2019 at 12:03 PM
    *To: *"users@royale.apache.org" <users@royale.apache.org>
    *Subject: *Re: Work on Emulation

    Hi Alex,

    Sorry for the delay, here is the debug screen-shots. Just trying
    to recover from flu

    The picture below show the places where the post request is sent:
    element.send()

    cid:part1.B62196BD.66A79116@likyateknoloji.com


    And here are the values of request and the element :

    cid:part2.BB4EE043.35BE4B87@likyateknoloji.com

    cid:part3.B23DA06F.5E8F1667@likyateknoloji.com

    I can see in the debug view that the method an the url is set
    correctly for element but can not see where the data is set. Even
    in URLLoader.as JS compiler section has no setting for request data.

    May be I am missing something.

    Thanks,
    Serkan

    14.01.2019 08:08 tarihinde serkan....@likyateknoloji.com
    <mailto:serkan....@likyateknoloji.com> yazdı:


        I drilled in to the DirectChannel apply method and saw the
        same picture that all the values are as expected. I am going
        to prepare the case and the screenshot later today.

        Thanks,
        Serkan

        Alinti Alex Harui <aha...@adobe.com> <mailto:aha...@adobe.com>



            I think there is a good chance that that AbstractOperation
            doesn't work (or the AbstractInvoker it calls isn't
            working).  I would recommend that you debug in that area
            first.

            -Alex

            On 1/13/19, 8:36 PM, "serkan....@likyateknoloji.com"
            <mailto:serkan....@likyateknoloji.com>
            <serkan....@likyateknoloji.com>
            <mailto:serkan....@likyateknoloji.com> wrote:

                Sure not Alex,

                I am going through my application workflow.

                If you need to know, than I may prepare an application
            to see if it is or not.

                I think you are wondering about the emulated classes
            causing the issue.

                Thanks,
                Serkan

                Alinti Alex Harui <aha...@adobe.com>
            <mailto:aha...@adobe.com>

                > Hi Serkan,
                >
                > Have you seen AbstractOperation (for HTTP) work
            without XML?
                >
                > -Alex
                >
                > From: Serkan Taş <serkan....@likyateknoloji.com>
            <mailto:serkan....@likyateknoloji.com>
                > Reply-To: "users@royale.apache.org"
            <mailto:users@royale.apache.org> <users@royale.apache.org>
            <mailto:users@royale.apache.org>
                > Date: Sunday, January 13, 2019 at 11:01 AM
                > To: "users@royale.apache.org"
            <mailto:users@royale.apache.org> <users@royale.apache.org>
            <mailto:users@royale.apache.org>
                > Subject: Re: Work on Emulation
                >
                > Hi Alex,
                >
                > Adding the part below worked for text conversion.
                >
                >             if (ctype == CONTENT_TYPE_XML)
                >             {
                >                 paramsToSend =
            parameters.toXMLString();
                >
                > I am not sure but I guess this time the data is not
            sent to the
                > server side. I debugged the code and see that it is
            all set.
                >
                > Here is the capture of the debug, you can see the
            watch expression
                > and the parameters which are all correct.
                >
                > [cid:part1.6700F27F.BB28F758@likyateknoloji.com]
                >
                >
                > 13.01.2019 14:35 tarihinde Serkan Taş yazdı:
                > Hi Alex,
                >
                > parameters is XML. It is the return of
                >
                > XML.conversion("username=" +
                >
            
com.likya.pinara.model.ModelLocator.getInstance().currentUser.username);

                >
                > Yes the request use POST. I am going to try
            toXMLString.
                >
                > Thanks,
                > Serkan
                >
                > 13.01.2019 10:01 tarihinde Alex Harui yazdı:
                > Hi Serkan,
                >
                > What is parameters?  Isn’t it XML or an Array with
            one XML element?
                > If so, “as String” will return null since neither
            XML or Array is a
                > String.  I think the commented code calls
            toXMLString on an XML
                > instance,  I think that’s what you want to do.  I
            think the code
                > also switches to POST as well.
                >
                > HTH,
                > -Alex


                --
                Serkan Taş
                Mobil : +90 532 250 07 71
                Likya Bilgi Teknolojileri
                ve İletişim Hiz. Ltd. Şti.
            
https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&amp;data=02%7C01%7Caharui%40adobe.com%7Cf63c32d6d50541ee5e4708d679d9e4db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636830374110739512&amp;sdata=gD5MNvTJP%2FrA5DjVt3RFnfHzZHRLOCvb9%2BM1o%2BkKOqQ%3D&amp;reserved=0
            
<https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&data=02%7C01%7Caharui%40adobe.com%7Cd786c9b9f4c34d2c714608d67bf052e6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832669447736144&sdata=KXjFo358QdgwFSn2wdPpNRrJr6xCtYfa%2BvuPDe2e5UA%3D&reserved=0>

                --------------------------------------
                Bu elektronik posta ve onunla iletilen bütün dosyalar
            gizlidir. Sadece
                yukarıda isimleri belirtilen kişiler arasında özel
            haberleşme amacını
                taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik
            postanın
                içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve
            kullanmanız
                kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve
            sisteminizden
                siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz.
            Ltd. Şti. bu
                mesajın içeriği ile ilgili olarak hiç bir hukuksal
            sorumluluğu kabul
                etmez.

                This electronic mail and any files transmitted with it
            are intended
                for the private use of  the persons named above. If
            you received this
                message in error, forwarding, copying or use of any of
            the information
                is strictly prohibited. Please immediately notify the
            sender and
                delete it from your system. Likya Bilgi Teknolojileri
            ve İletişim Hiz.
                Ltd. Şti. does not accept legal responsibility for the
            contents of
                this message.
                --------------------------------------





Reply via email to