wso2ei

问题 i am using WSO2 Enterprise Integrator 6.5.0 (lastest) I need to enable HTTP Basic Authentication through a Proxy Service (SOAP, REST) I have tried below resource - WSO2 EI and WSO2 Developer - Setup an ESB Proxy with http basic authentication <?xml version="1.0" encoding="UTF-8"?> <proxy name="ProxyWithBasicAuth" startOnLoad="true" trace="disable" transports="https" xmlns="http://ws.apache.org/ns/synapse"> <target> <endpoint name="endpoint_urn_uuid_xxxxxxxx-yyyy-zzzz-1111-234567892345">

问题 I am using angular client to call a rest api in wso2 which is exposed from a data service not directly built as an api and also tried many solutions provided in stack overflow and also wso2 documentation , nothing helps. 回答1: With regard to OPTIONS requests in the preflight, the WSO2 Enterprise Integrator (EI) behaves as follows depending on the implementation of the API. If we have defined OPTIONS as a resource method, then EI sends the request to the backend service to collect the

问题 I am trying to create Campaigns by using Sendgrid V3 API. if i use Try it out tool it shows like Error message like "authorization required" even though Authorization Bearer value(API KEY) given, if i hit the same in Postman it gives error response like "access forbidden". Is this Sendgrid API Issue or am i missing anything? and one more question here is shall we try campaign related operations by using trial account? Note : Same API key is working fine for some other operations like List

问题 I am using WSO2 EI 6.3.0 version. I am creating data service within the application which reads data from CSV. I am running into very unusual case where I have created two data services. One with sample Product.csv which is shipped with WSO2 EI. When calling Sample (Product.CSV) I am able to get the json response message. but when I am trying to invoke another API which other data service it is giving me below error: [2018-10-10 17:57:31,916] [EI-Core] ERROR - JsonStreamFormatter Error

问题 how can I achieve this with xpath in wso2? Example: <TEMP> <NAME>GEORGE</NAME> <COGNOME>MENDEZ</COGNOME> <BUSINESSNAME/> <CHANNEL>X091</CHANNEL> </TEMP> Result: <NAME>GEORGE</NAME> <COGNOME>MENDEZ</COGNOME> <BUSINESSNAME/> <CHANNEL>X091</CHANNEL> Thanks 回答1: The XML generated needs to have a root element. Therefore you will not be able to create the following payload, which does not have a root element. <NAME>GEORGE</NAME> <COGNOME>MENDEZ</COGNOME> <BUSINESSNAME/> <CHANNEL>X091</CHANNEL>

来源： https://stackoverflow.com/questions/64347153/attachment-handling-through-wso2-ei-6-1-1-in-api

来源： https://stackoverflow.com/questions/64347153/attachment-handling-through-wso2-ei-6-1-1-in-api

问题 I am implementing Iterate mediator inside Iterate mediator. After that, I have an Aggregate mediator in out-sequence. <inSequence> <iterate attachPath="json-eval($.Entity.names)" expression="json-eval($.Entity.names)" id="iterate-over-names" preservePayload="true"> <target> <payloadFactory media-type="json"> <format>[{"value" : 1},{"value" : 2},{"value" : 3},{"value" : 4},{"value" : 5},{"value" : 6},{"value" : 7},{"value" : 8},{"value" : 9}]</format> <args/> </payloadFactory> <iterate

问题 I have a payload factory like below: <payloadFactory media-type="json"> <format>[{"value" : 1},{"value" : 2},{"value" : 3}]</format> <args/> </payloadFactory> <iterate expression="json-eval($)" id="iterate-over-nameAddress"> <call> <endpoint> <http method="get" uri-template="https://backend.com/names/value+{uri.var.value}/address"/> </endpoint> </call> </iterate> In the above code, in backend call, I want the path-parameter " value+{uri.var.value} " to change dynamically according to the

问题 I want to implement a simple " for loop " in WSO2 Integration Studio. For example: I am implementing a bus-route API. Every bus has 10 different stops. I want to fetch the 10 stops from the back-end service. A normal for-loop for this would be: for(i=0;i<10;i++) { //back-end call <call> <endpoint> <http method="get" uri-template="https://backend.com/city+i"/> </endpoint> </call> } NOTE: In the above for loop, the back-end call has path parameter like city which should be iterated as city1,