Please also find the raw tab of soapui for proxy service.
With Regards, Aditya On Mon, Mar 26, 2018 at 9:33 AM, aditya shivankar < [email protected]> wrote: > Please find the error logs attached. > > With Regards, > Aditya > > On Mon, Mar 26, 2018 at 7:50 AM, Himasha Guruge <[email protected]> wrote: > >> Hi Aditya, >> >> Could you attach the error log you are getting? Probably some required >> header is missing in this case. What you could do is enable wire logs and >> send the request (through the proxy) and compare it with the raw request >> sent from SoapUI. ('raw' tab in SoapUI request provides the exact headers >> that are passed) >> >> Thanks, >> Himasha >> >> On Sun, Mar 25, 2018 at 9:16 PM, aditya shivankar < >> [email protected]> wrote: >> >>> Respected Madam/Sir, >>> >>> I am not able to get why I am getting this error, When I am invoking >>> from using vfs file trigger. While the same flow works good when I am >>> invoking from soapui . >>> The request going to dataservice looks same to me both times. Please >>> Guide. >>> >>> >>> With Regards, >>> Aditya >>> >>> On Thu, Mar 22, 2018 at 5:46 PM, aditya shivankar < >>> [email protected]> wrote: >>> >>>> Hi Himasha, >>>> >>>> Please find dataMapper output attached in each of the case. >>>> >>>> With Regards, >>>> Aditya >>>> >>>> >>>> On Thu, Mar 22, 2018 at 5:15 PM, aditya shivankar < >>>> [email protected]> wrote: >>>> >>>>> Hi Himasha, >>>>> >>>>> I have logged the payload after datamapper. >>>>> >>>>> I compared the output of logger , When I am invoking from soapui and , >>>>> When I am invoking from using vfs file trigger. >>>>> Both times ,datamapper output logged look the same. >>>>> But for soapui invocation it is working and for vfs file trigger it is >>>>> throwing error. >>>>> >>>>> With Regards, >>>>> Aditya >>>>> >>>>> On Thu, Mar 22, 2018 at 4:47 PM, Himasha Guruge <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Aditya, >>>>>> >>>>>> Have you constructed your payload appropriately, before invoking data >>>>>> service? In SOAPUI request following format is maintained. >>>>>> >>>>>> <dat:UserOP_batch_req> >>>>>> <dat:UserOP>...</dat:UserOP> >>>>>> </dat:UserOP_batch_req> >>>>>> >>>>>> Thanks, >>>>>> Himasha >>>>>> >>>>>> On Thu, Mar 22, 2018 at 4:14 PM, aditya shivankar < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Himasha, >>>>>>> >>>>>>> Please find the modified proxy service " WriteToDB2.xml" attached. >>>>>>> After adding below line. >>>>>>> <property name="SOAPAction" scope="transport" >>>>>>> value="urn:request_box"/> >>>>>>> >>>>>>> But it is still giving the same error. >>>>>>> >>>>>>> With Regards, >>>>>>> Aditya >>>>>>> >>>>>>> On Thu, Mar 22, 2018 at 4:03 PM, aditya shivankar < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Himasha, >>>>>>>> >>>>>>>> Added below line >>>>>>>> >>>>>>>> But still getting the same error. >>>>>>>> >>>>>>>> <property name="SOAPAction" scope="transport" >>>>>>>> value="urn:request_box"/> >>>>>>>> >>>>>>>> >>>>>>>> With Regards, >>>>>>>> Aditya >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Himasha Guruge >>>>>> Senior Software Engineer >>>>>> WS*O2* *Inc.* >>>>>> Mobile: +94 777459299 <+94%2077%20745%209299> >>>>>> [email protected] >>>>>> >>>>> >>>>> >>>> >>> >> >> >> -- >> Himasha Guruge >> Senior Software Engineer >> WS*O2* *Inc.* >> Mobile: +94 777459299 >> [email protected] >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
