wso2esb - WSO2 ESB - JMS response from endpoint with XML payload shows up as Text -

-

Text after "div class =" itemprop = "text">

I am using WSO2 ESB to send a JMS message (XML payload) to the end point and then return a JMS To read the message (on another line) from the same closing point (which sends an XML payload), the problem I am facing is returning JMS messages from the last position, although this is an XML payload, one Comes in the form of text messaging. ?

Here I have sent back the JMP message (with the XML payload) in WSO2 to the endpoint: 

   & Amp; Lt ;? XML version = "1.0" encoding = "UTF-8"? & Gt; & Amp; Lt; Sys1Response xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi: noNamespaceSchemaLocation = "Sys1-acknowledgment-nack.xsd" & amp; Gt; & Amp; Lt; Security & amp; Gt; & Amp; Lt; StatusInfo & amp; Gt; & Amp; Lt; ARMStatus & amp; Gt; ARM_ACK & amp; Lt; / ARMStatus & amp; Gt; & Amp; Lt; Sys1Status & amp; Gt; Sys1_ACK & amp; Lt; / Sys1Status & amp; Gt; & Amp; Lt; FinalStatus & amp; Gt; ACK & amp; Lt; / FinalStatus & amp; Gt; & Amp; Lt; / StatusInfo & amp; Gt; & Amp; Lt; UpstreamIdentifier & amp; Gt; & Amp; Lt; TradeId & amp; Gt; 459609 & amp; Lt; / TradeId & amp; Gt; & Amp; Lt; MessageId & amp; Gt; 12345678 & amp; Lt; / MessageId & amp; Gt; & Amp; Lt; Assetid & amp; Gt; 6M2 & amp; Lt; / Assetid & amp; Gt; & Amp; Amp; Lt; Issue description & amp; Gt; IRS RTP 3.12 May 19, 11 JP & amp; the lift; / Issue description & gt; & Amp; Lt; ProductType & amp; Gt; Swap & amp; Lt; / ProductType & amp; Gt; & Amp; Lt; / UpstreamIdentifier & amp; Gt; & Amp; Lt; / Safety & amp; Gt; & Amp; Lt; / Sys1Response & amp; Gt; & Lt; / Axis2ns2: text & gt; & Lt; / Soapenv: Body & gt; & Lt; / Soapenv: envelope & gt;

This is the WSO2 proxy definition 

 . & Lt ;? Xml version = "1.0" encoding = "UTF-8" & gt; & Lt; Definitions xmlns = "http://ws.apache.org/ns/synapse"> & Lt; Registry Provider = "org.wso2.carbon.mediation.registry.ESBRegistry" & gt; & Lt; Parameter name = "local registry" & gt; / & Lt; / Parameters & gt; & Lt; Parameter name = "cachableDuration" & gt; 15000 & lt; / Parameters & gt; & Lt; / Registry & gt; & Lt; Proxy name = "ToWSO2" transports = "jms" startOnLoad = "true" trace = "disable" & gt; & Lt; Description / & gt; & Lt; Goal & gt; & Lt; InSequence & gt; & Lt; Property name = "transport.jms.ContentTypeProperty" value = "content-type" scope = "axis 2" /> & Lt; Log level = "full" /> & Lt; Phone & gt; & Lt; Endpoint & gt; & Lt; Address uri = "jms: / ToSys1 transport.jms.ConnectionFactoryJNDIName = QueueConnectionFactory & amp; amp; java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory & amp; amp; java.naming.provider.url = TCP: // Local Host: 61616 & amp; transport.jms.DestinationType = Qatar & amp; transport.jms.ReplyDestinationType = Queue & amp; transport.jms.ReplyDestination = FromSys1 & amp; Transport .jms.ContentType = application / xml "/ & gt; & Lt; / Endpoint & gt; & Lt; / Call & gt; & Lt; Log level = "full" /> & Lt; / InSequence & gt; & Lt; OutSequence & gt; & Lt; Log level = "full" /> & Lt; Drop / & gt; & Lt; / OutSequence & gt; & Lt; / Target & gt; & Lt; Parameter name = "transport.jms.ContentType" & gt; & Lt; Rules & gt; & Lt; JmsProperty & gt; ContentType & lt; / JmsProperty & gt; & Lt; Default & gt; Application / xml & lt; / Default & gt; & Lt; / Rules & gt; & Lt; / Parameters & gt; & Lt; Parameter name = "transport.jms.Destination" & gt; ToWSO2 & lt; / Parameters & gt; & Lt; / Proxy & gt; & Lt; Sequence name = "defects" & gt; & Lt; Log level = "full" & gt; & Lt; Property name = "MESSAGE" value = "default execution" wrong "sequence" / & gt; & Lt; Property name = "ERROR_CODE" expression = "get-property ( 'ERROR_CODE')" / & gt; & Lt; Property name = "ERROR_MESSAGE" expression = "received-asset ('ERROR_MESSAGE')" /> & Lt; / Logs & gt; & Lt; Drop / & gt; & Lt; / Sequence & gt; & Lt; Sequence name = "main" & gt; & Lt; In & gt; & Lt; Log level = "Full" / & gt; & Lt; Filter source = "received-asset ('per')" regex = "http: // localhost: 9000. *" "& gt; & Lt; Send / & gt; & Lt; / Filter & gt; & Lt; / In & gt; & Lt; Outside & gt; & Lt; Send / & gt; & Lt; / Out & gt; & Lt; Details & gt; Main sequence for message mediation & lt; / Description & gt; & Lt; / Sequence & gt; & Lt; / Definitions & gt;

Many thanks in advance would appreciate the help in solving it!


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more