Re: [Dev] Issue with ESB 4.8 and SoupUI
Hi Ravi, This issue seemed to be different. Anyway, according to basic profile[1], you can't have multiple root elements inside soap body. So, correct soap body should be soapenv:Header/ soapenv:Body root a1aaa/a1 b1bbb/b1 /root /soapenv:Body /soapenv:Envelope [1] http://www.ws-i.org/profiles/basicprofile-1.1.html R9981 An ENVELOPE MUST have exactly zero or one child elements of the soap:Body element. On Wed, Jan 1, 2014 at 3:45 PM, Ravi Undupitiya r...@wso2.com wrote: Please see https://wso2.org/jira/browse/ESBJAVA-2815 for details on this issue. On Sat, Dec 28, 2013 at 3:17 PM, indika prasad indika@gmail.comwrote: Hi, I have a issue with below proxy and SoupUI. Proxy ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapse; name=souptest transports=https,http statistics=disable trace=disable startOnLoad=true target inSequence payloadFactory media-type=json format{ contentType:linkedin-html, body:update body }/format args/ /payloadFactory property name=messageType value=application/json scope=axis2/ send endpoint address uri=http://localhost:8281/services/jsonService; format=rest/ /endpoint /send /inSequence /target description/ /proxy 01. Using SoupUI with following request send the expected massage to the given endpoint. soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soap request- soapenv:Header/ soapenv:Body a1aaa/a1 /soapenv:Body /soapenv:Envelope TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO 47 { contentType:linkedin-html, body:update body } 0 02. Using SoapUI with following request send the strange massage to the endpoint. Where the payload has replaced by the second element of the soup request! --soup request soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body a1aaa/a1 b1bbb/b1 /soapenv:Body /soapenv:Envelope --- TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO c {b1:bbb} 0 Thanks Indika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712 %2B94%C2%A0772%20930%20712* Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue with ESB 4.8 and SoupUI
This is a bug. For the time being a work around is to wrap the separate elements inside a root element like: root a1aaa/a1 b1bbb/b1 /root On Sat, Dec 28, 2013 at 3:17 PM, indika prasad indika@gmail.com wrote: Hi, I have a issue with below proxy and SoupUI. Proxy ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapse; name=souptest transports=https,http statistics=disable trace=disable startOnLoad=true target inSequence payloadFactory media-type=json format{ contentType:linkedin-html, body:update body }/format args/ /payloadFactory property name=messageType value=application/json scope=axis2/ send endpoint address uri=http://localhost:8281/services/jsonService; format=rest/ /endpoint /send /inSequence /target description/ /proxy 01. Using SoupUI with following request send the expected massage to the given endpoint. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soap request- soapenv:Header/ soapenv:Body a1aaa/a1 /soapenv:Body /soapenv:Envelope TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO 47 { contentType:linkedin-html, body:update body } 0 02. Using SoapUI with following request send the strange massage to the endpoint. Where the payload has replaced by the second element of the soup request! --soup request soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header/ soapenv:Body a1aaa/a1 b1bbb/b1 /soapenv:Body /soapenv:Envelope --- TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO c {b1:bbb} 0 Thanks Indika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712* Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue with ESB 4.8 and SoupUI
Please see https://wso2.org/jira/browse/ESBJAVA-2815 for details on this issue. On Sat, Dec 28, 2013 at 3:17 PM, indika prasad indika@gmail.com wrote: Hi, I have a issue with below proxy and SoupUI. Proxy ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapse; name=souptest transports=https,http statistics=disable trace=disable startOnLoad=true target inSequence payloadFactory media-type=json format{ contentType:linkedin-html, body:update body }/format args/ /payloadFactory property name=messageType value=application/json scope=axis2/ send endpoint address uri=http://localhost:8281/services/jsonService; format=rest/ /endpoint /send /inSequence /target description/ /proxy 01. Using SoupUI with following request send the expected massage to the given endpoint. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soap request- soapenv:Header/ soapenv:Body a1aaa/a1 /soapenv:Body /soapenv:Envelope TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO 47 { contentType:linkedin-html, body:update body } 0 02. Using SoapUI with following request send the strange massage to the endpoint. Where the payload has replaced by the second element of the soup request! --soup request soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header/ soapenv:Body a1aaa/a1 b1bbb/b1 /soapenv:Body /soapenv:Envelope --- TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO c {b1:bbb} 0 Thanks Indika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712* Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue with ESB 4.8 and SoupUI
Hi, I have a issue with below proxy and SoupUI. Proxy ?xml version=1.0 encoding=UTF-8? proxy xmlns=http://ws.apache.org/ns/synapse; name=souptest transports=https,http statistics=disable trace=disable startOnLoad=true target inSequence payloadFactory media-type=json format{ contentType:linkedin-html, body:update body }/format args/ /payloadFactory property name=messageType value=application/json scope=axis2/ send endpoint address uri=http://localhost:8281/services/jsonService; format=rest/ /endpoint /send /inSequence /target description/ /proxy 01. Using SoupUI with following request send the expected massage to the given endpoint. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soap request- soapenv:Header/ soapenv:Body a1aaa/a1 /soapenv:Body /soapenv:Envelope TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO 47 { contentType:linkedin-html, body:update body } 0 02. Using SoapUI with following request send the strange massage to the endpoint. Where the payload has replaced by the second element of the soup request! --soup request soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body a1aaa/a1 b1bbb/b1 /soapenv:Body /soapenv:Envelope --- TCPMon out put- POST /services/jsonService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json SOAPAction: Transfer-Encoding: chunked Host: 127.0.0.1:8281 Connection: Keep-Alive User-Agent: Synapse-PT-HttpComponents-NIO c {b1:bbb} 0 Thanks Indika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Issue-with-ESB-4-8-and-SoupUI-tp90206.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev