Mined Opinions For API: open-esb

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • Only the first key-value pair will be considered.. details
  • The value of the first key-value pair must not be an array.. details
  • In my experience, the JSON parser for WSO2 ESB (based on Axis2-json) supports only a subset of JSON: 1.. details
  • This is because JSON is mapped to XML-like datastructure, and XML must have a root, so the first key-value pair is considered as root.. details
  • This because the converter has to know which XML tag should be used for each value: e.g.. details
  • But when I try to do the same using a simple pass through service I get only : CODESNIPPET_JAVA2 .. details
  • well actually i modified the source for the message builder and it solved the problem atleast for now... details
  • well actually i modified the source for the message builder and it solved the problem atleast for now... details
  • Sorry for the late reply..let me see if Message Relay solves my problem... details
  • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder/formatter for application/json in place of default axis2 builder/formatter pair.Have a look at [this]( URL_http://docs.wso2.org/display/ESB403/Message+Relay) .. details
  • so does this mean as of now we dont have any other solution to this problem...?. details
  • Similarly CODETERM1 method can be used to set arbitrary JSON objects.. details
  • I have the same problem here and want to find a fix for this.. details
  • { "**root**" : ... } ) to fake the parser.. details
  • I mean is their any way I can manipulate the json data before the esb converts it into json data.. details
  • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format.. details
Summaries the opinions about open-esb using topic modeling.
  • 0. pair key root experience subset pas simple axis2 tag datastructure: 6
    • The value of the first key-value pair must not be an array.. details
    • This because the converter has to know which XML tag should be used for each value: e.g.. details
    • Only the first key-value pair will be considered.. details
    • This is because JSON is mapped to XML-like datastructure, and XML must have a root, so the first key-value pair is considered as root.. details
    • In my experience, the JSON parser for WSO2 ESB (based on Axis2-json) supports only a subset of JSON: 1.. details
    • But when I try to do the same using a simple pass through service I get only : CODESNIPPET .. details
  • 0. message builder formatter solve relay explanation resolve format find receive: 9
    • well actually i modified the source for the message builder and it solved the problem atleast for now... details
    • Sorry for the late reply..let me see if Message Relay solves my problem... details
    • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder/formatter for application/json in place of default axis2 builder/formatter pair.Have a look at [this]( .. details
    • so does this mean as of now we dont have any other solution to this problem...?. details
    • Similarly mc.setJSON() method can be used to set arbitrary JSON objects.. details
    • I have the same problem here and want to find a fix for this.. details
    • { "**root**" : ... } ) to fake the parser.. details
    • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format.. details
    • I mean is their any way I can manipulate the json data before the esb converts it into json data.. details
Summaries of the opinions about open-esb using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • Only the first key value pair will be considered .
  • But when I try to do the same using a simple pass through service I get only : CODESNIPPET JAVA2 .
  • In my experience, the JSON parser for WSO2 ESB (based on Axis2 json) supports only a subset of JSON: 1 .
  • This is because JSON is mapped to XML like datastructure, and XML must have a root, so the first key value pair is considered as root .
  • The value of the first key value pair must not be an array .
  • This because the converter has to know which XML tag should be used for each value: e g .
  • Only the first key value pair will be considered .
  • But when I try to do the same using a simple pass through service I get only : CODESNIPPET JAVA2 .
  • In my experience, the JSON parser for WSO2 ESB (based on Axis2 json) supports only a subset of JSON: 1 .
  • This is because JSON is mapped to XML like datastructure, and XML must have a root, so the first key value pair is considered as root .
  • The value of the first key value pair must not be an array .
  • This because the converter has to know which XML tag should be used for each value: e g .
  • Only the first key value pair will be considered .
  • But when I try to do the same using a simple pass through service I get only : CODESNIPPET JAVA2 .
  • In my experience, the JSON parser for WSO2 ESB (based on Axis2 json) supports only a subset of JSON: 1 .
  • This is because JSON is mapped to XML like datastructure, and XML must have a root, so the first key value pair is considered as root .
  • The value of the first key value pair must not be an array .
  • This because the converter has to know which XML tag should be used for each value: e g .
  • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format .
  • I mean is their any way I can manipulate the json data before the esb converts it into json data .
  • I have the same problem here and want to find a fix for this .
  • { "**root**" : } ) to fake the parser .
  • Similarly mc.setJSON() method can be used to set arbitrary JSON objects .
  • so does this mean as of now we dont have any other solution to this problem ?.
  • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder formatter for application json in place of default axis2 builder formatter pair Have a look at this]( .
  • Sorry for the late reply let me see if Message Relay solves my problem .
  • well actually i modified the source for the message builder and it solved the problem atleast for now .
  • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format .
  • I mean is their any way I can manipulate the json data before the esb converts it into json data .
  • I have the same problem here and want to find a fix for this .
  • { "**root**" : } ) to fake the parser .
  • Similarly mc.setJSON() method can be used to set arbitrary JSON objects .
  • so does this mean as of now we dont have any other solution to this problem ?.
  • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder formatter for application json in place of default axis2 builder formatter pair Have a look at this]( .
  • Sorry for the late reply let me see if Message Relay solves my problem .
  • well actually i modified the source for the message builder and it solved the problem atleast for now .
  • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format .
  • I mean is their any way I can manipulate the json data before the esb converts it into json data .
  • I have the same problem here and want to find a fix for this .
  • { "**root**" : } ) to fake the parser .
  • Similarly mc.setJSON() method can be used to set arbitrary JSON objects .
  • so does this mean as of now we dont have any other solution to this problem ?.
  • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder formatter for application json in place of default axis2 builder formatter pair Have a look at this]( .
  • Sorry for the late reply let me see if Message Relay solves my problem .
  • well actually i modified the source for the message builder and it solved the problem atleast for now .
Summaries of the opinions about open-esb using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about open-esb using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Usability:
  • In my experience, the JSON parser for WSO2 ESB (based on Axis2-json) supports only a subset of JSON: 1.
  • well actually i modified the source for the message builder and it solved the problem atleast for now..
Features:
  • Only the first key-value pair will be considered.
  • { "**root**" : ... } ) to fake the parser.
Bug:
  • N/A
  • well actually i modified the source for the message builder and it solved the problem atleast for now..
  • Features: 2
    1. general: 2
      • Only the first key-value pair will be considered.. details
      • The value of the first key-value pair must not be an array.. details
  • Usability: 4
    1. general: 4
      • In my experience, the JSON parser for WSO2 ESB (based on Axis2-json) supports only a subset of JSON: 1.. details
      • This is because JSON is mapped to XML-like datastructure, and XML must have a root, so the first key-value pair is considered as root.. details
      • This because the converter has to know which XML tag should be used for each value: e.g.. details
      • But when I try to do the same using a simple pass through service I get only : CODESNIPPET_JAVA2 .. details
  • Features: 2
    1. general: 2
      • { "**root**" : ... } ) to fake the parser.. details
      • I mean is their any way I can manipulate the json data before the esb converts it into json data.. details
  • Bug: 4
    1. general: 4
      • well actually i modified the source for the message builder and it solved the problem atleast for now... details
      • Sorry for the late reply..let me see if Message Relay solves my problem... details
      • I have the same problem here and want to find a fix for this.. details
      • I read on the wso2esb site that they had a bug and the explanation given to resolve the bug was that json data received was not in the proper format.. details
  • Usability: 4
    1. general: 4
      • well actually i modified the source for the message builder and it solved the problem atleast for now... details
      • If you don't wish to build or manipulate the message within the ESB, you can use message relay message builder/formatter for application/json in place of default axis2 builder/formatter pair.Have a look at [this]( URL_http://docs.wso2.org/display/ESB403/Message+Relay) .. details
      • so does this mean as of now we dont have any other solution to this problem...?. details
      • Similarly CODETERM1 method can be used to set arbitrary JSON objects.. details