wso2 - Message relay for JSON data in wso2ESB -


I am trying to create a simple POC using wso2ESB. I have made a simple pass through Alfaro service with proxy service

The problem is that I can not find the full JSON data I have read that it has something to do with axis2-JSON and this problem Generates when JSONArray is in a root, so I decided to use message relay.

I have edited axis2.xml as described in the document, thus adding the following lines

     

and

  & lt; MessageBuilder contentType = "application / xml" class = "org.apache.axis2.builder.ApplicationXMLBuilder" />   

But when I try to use a proxy server through the Firefox REST plugin, ESB throws the following exception after restarting the server

  [2012 -07-12 10: 02: 29,125] Warning - Client worker received unexpected response. HTTP response co Day: 405 HTTP status: not allowed pattern exceptions: SOAP message must not contain a Documen t type declaration (DTD) [2012-07-12 10: 02: 29,125] error - did not NativeWorkerPool exception java. lang.ClassCastException: Org.apache.axiom.om.impl.llom.OMTextImpl organization can not be cast org.apache.synapse.util.MessageHelper.cloneSOAPFault (MessageHelper.java:441) org.apache.synapse.util.MessageHelper Apache.axiom.om.OMElement on .cloneSOAPEnvelope at (MessageHelper.java:254) org.apache. On synapse.core.axis2.SOAPUtils.convertSOAP11toSOAP12 (SOAPUtils.java:95) org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage (SynapseCallbac kReceiver.java:323) on org.apache.synapse.core.axis2.SynapseCallbackReceiver .receive (SynapseCallbackRecei ver.java:160) org.apache.axis2.engine.AxisEngine.receive (AxisEngine.java:181) on org.apache.synapse.transport.nhttp.ClientWorker.run (ClientWorker.java:275) java.util.concurrent.ThreadPoolExecutor $ Worker.runTask (ThreadPoolExecutor.java:886) on java.util.concurrent: org.apache.axis2.transport.base.threads.NativeWorkerPool $ 1.run (173 NativeWorkerPool.ja VA) On . ThreadPool Aksclotr $ Worker.run (ThreadPoolExecutor.java:908) at java.lang.Thread.run (Thredkjawa: 662)   

What is the reason? What is the problem that ESB still tries to change the JSON object instead of trying to relay it?

Is there any other workaround in parsing these JSON objects (i.e. add artificial root to JSON object?)

On the builders you must set the application / json to use org.wso2.carbon.relay.BinaryRelayBuilder.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -