Re: [Dev] [DEV][ESB] Appending the file name dynamically in WSO2 file connector

Thanks Shafreen and Keerthika, This approach works fine. Cheers, Pubudu. Pubudu D.P Senior Software Engineer - QA Team | WSO2 inc. Mobile : +94775464547 Linkedin: https://uk.linkedin.com/in/pubududp Medium: https://medium.com/@pubududp On Thu, Nov 24, 2016 at 1:54 PM, Shafreen Anfar

Re: [Dev] [DEV][ESB] Appending the file name dynamically in WSO2 file connector

Hi Pubudu, What you can do is have the below part of the uri in some property. And then have another property to append the file name to the end. Something like blew. Then in the connector try something as below, *{$ctx:completeLocation}*

Re: [Dev] [DEV][ESB][DSS] Sending batch request to DSS

Hi, Removing 'blocking = true' worked. Thank you Rajith, Malaka for the help. Regards Chanuka. On Wed, Aug 31, 2016 at 8:28 PM, Rajith Vitharana wrote: > Hi Chanuka, > > Try with call mediator blocking=false. > > Thanks, > > On 31 August 2016 at 19:53, Malaka Silva

Re: [Dev] [DEV][ESB][DSS] Sending batch request to DSS

Hi Chanuka, Try with call mediator blocking=false. Thanks, On 31 August 2016 at 19:53, Malaka Silva wrote: > Hi Chanuka, > > Shall we try to find the payload in messagecontext before iterator > mediator. > > You can use log mediator or mediation debugger to do that. > > On

Re: [Dev] [DEV][ESB][DSS] Sending batch request to DSS

Hi Chanuka, Shall we try to find the payload in messagecontext before iterator mediator. You can use log mediator or mediation debugger to do that. On Wed, Aug 31, 2016 at 4:50 PM, Chanuka Dissanayake wrote: > Hi, > > I'm trying to do the $subject using ESB 5.0, DSS 3.5.0

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

Hi Nuwan Awesome. Thank You Best Regards Erandi On Mon, Jul 25, 2016 at 5:05 PM, Nuwan Pallewela wrote: > Hi Chathurika, > > Yes. We have discussed it and going to do it[1]. We will provide a > editable drop down with the configuration need to provide to select the > input

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

Hi Chathurika, Yes. We have discussed it and going to do it[1]. We will provide a editable drop down with the configuration need to provide to select the input and operator description in the configure dialog about it. [1] https://wso2.org/jira/browse/DEVTOOLESB-655 Thanks, Nuwan On Mon, Jul

Re: [Dev] [DEV][ESB Tooling] Improvement on constant operator

Hi Viraj Thank you for your reply. Agree with you on a proper graphical representation for a global constant as it will increase usability. Best Regards Erandi On Fri, Jul 22, 2016 at 5:47 PM, Viraj Rajaguru wrote: > Hi Chaturika, > > We got your point and we will consider

Re: [Dev] [DEV][ESB Tooling] Improvement on constant operator

Hi Chaturika, We got your point and we will consider this improvement for a next release with a proper graphical representation. BTW, we are encouraging users to write self contained custom functions as much as possible to reduce the complexity. So that its better to define constants within the

Re: [Dev] [DEV][ESB Tooling] Data mapper interprets multiplication of negative integers by zero results in signed zero

Hi Chanaka, On Fri, Jul 22, 2016 at 12:47 PM, Chanaka Fernando wrote: > Hi Chathurika, > > We understand your point. But this is not a functional blocker. We will > reduce the priority of this issue and as NuwanP mentioned in the ticket, > this needs to be fixed from the JS

Re: [Dev] [DEV][ESB Tooling] Data mapper interprets multiplication of negative integers by zero results in signed zero

Hi Chathurika, We understand your point. But this is not a functional blocker. We will reduce the priority of this issue and as NuwanP mentioned in the ticket, this needs to be fixed from the JS engine level. If we are going to deal with that, it will reduce the performance of the entire data

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

Hi Chathurika, We highly appreciate your suggestions to improve the data mapper. As you said what we should provide as the data mapper is an enhanced mechanism for data conversion which would be easy for user to do whatever s/he wants. So I think we should provide those capabilities without

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

Hi All, On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando wrote: > Hi Erandi, > > Appreciate your feedback on improving the DM. The existing compare > operator checks for the equality (==) of the values passed into the > operator. If you passed in 2 String values, it will

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

Hi Chanaka Thank you for your reply and I am sorry if my earlier mail was confusing. Currently the compare operator consists of greater than and less than functions. Usually these operators are used for numeric comparisons. But when two Strings are given for greater than or less than function,

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

Hi Erandi, Appreciate your feedback on improving the DM. The existing compare operator checks for the equality (==) of the values passed into the operator. If you passed in 2 String values, it will check the equality of strings. If it is integer values, it will check for the equality of integer

Re: [Dev] [DEV] [ESB] [SMPP Transport] Unable to send message

Hi Biruntha, AFAIK your correct. Your testing Sending SMS Alerts for failures. In blog[1] Step 6 you stop the service so it will produce error according to blog it's need to send as sms. [1] http://mytecheye.blogspot.com/2013/01/wso2-esb-sending-sms-alerts-for-failures.html On Wed, Jun 1, 2016

Re: [Dev] [DEV] [ESB] [SMPP Transport] Unable to send message

Hi Malaka, I will try to debug. but i already tried with some information from [1] and [2]. but the same error is coming. [1] http://stackoverflow.com/questions/18721246/smpp-using-wso2 [2] http://mytecheye.blogspot.com/2013/01/wso2-esb-sending-sms-alerts-for-failures.html Biruntha Associate

Re: [Dev] [DEV] [ESB] [SMPP Transport] Unable to send message

Hi Biruntha, Try debugging [1] and you may also find some info in [2] [1] http://svn.apache.org/repos/asf/axis/axis2/java/transports/branches/transport/1.0.0/modules/sms/ [2] http://mytecheye.blogspot.com/2013/01/wso2-esb-sending-sms-alerts-for-failures.html On Tue, May 31, 2016 at 7:18 PM,

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Malaka, LDAP Connector is released and published in store [1]. [1] https://store.wso2.com/store/assets/esbconnector/6e86496f-431e-43e2-bded-caedd10c4cb9 *Thank youVivekananthan Sivanayagam* *Associate Software Engineer | WSO2* *E:vivekanant...@wso2.com *

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Noted. *Thank youVivekananthan Sivanayagam* *Associate Software Engineer | WSO2* *E:vivekanant...@wso2.com * *M:+94752786138* On Wed, May 25, 2016 at 5:37 AM, Malaka Silva wrote: > Please proceed and release. > > On Tue, May 24, 2016 at 6:21

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Please proceed and release. On Tue, May 24, 2016 at 6:21 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > Yes, We can release after fixed. > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Malaka, Yes, We can release after fixed. *Thank youVivekananthan Sivanayagam* *Associate Software Engineer | WSO2* *E:vivekanant...@wso2.com * *M:+94752786138* On Tue, May 24, 2016 at 3:44 PM, Malaka Silva wrote: > Can we fix those and

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Can we fix those and release please? On Tue, May 24, 2016 at 2:32 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > I have tested LDAP Connector with those changes, It is working fine , but > there is a problem when run the test cases because all the test case >

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Malaka, I have tested LDAP Connector with those changes, It is working fine , but there is a problem when run the test cases because all the test case methods are skipped but it gets build success. Error is "Caused by: java.io.FileNotFoundException:

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi willian Antunes, Thank you for more details, I am looking on that. *Thank youVivekananthan Sivanayagam* *Associate Software Engineer | WSO2* *E:vivekanant...@wso2.com * *M:+94752786138* On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

By the way I believe we could talk directly from the LDAP Connector JIRA issue instead from here or use the pull request that I requested from GitHub , so we can keep the history of it from

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Vivekananthan, Did you see what happened during the communication process? If didn't try to install an sniffer like Wireshark to understand which error the LDAP server sent to you. There are two scenarios which you can use to test: 1 - Set *secureConnection* and *disableSSLCertificateChecking

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Malaka, I am working on that and still I have a problem in configure LDAP with SSL connection. Without SSL connection, the connector is working and according to the his changes, the SearchEntry method is working with onlyOneReference parameter. I need to check in SSL connection part. I

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Vivekananthan, Please update the progress please? Shakila went through some of the methods in this connector. The description for parameters are not added in all templates. This is not the standard that we followed so far. On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Willian, Sorry for the missing headers. I edited the files from Developer Studio, it > erases the XML file to a new one every time you open it. So even when a > comment is inserted, the file will be erased again in the design view. > I will look on that and update. -- Thank you Best

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Noted Malaka, I will update the status on Monday. On Sat, May 7, 2016 at 2:19 PM, Malaka Silva wrote: > Thank you Willian. Great if you could create a pull request for [1] > > @Rajjaz - Can we check this improvement and add to our code base on Monday? > > [1]

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Thank you Willian. Great if you could create a pull request for [1] @Rajjaz - Can we check this improvement and add to our code base on Monday? [1] https://github.com/wso2-extensions/esb-connector-ldap On Fri, May 6, 2016 at 11:29 PM, Willian Antunes < willian.lima.antu...@gmail.com> wrote: >

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

It's done. Sorry for the missing headers. I edited the files from Developer Studio, it erases the XML file to a new one every time you open it. So even when a comment is inserted, the file will be erased again in the design view. Thanks! On Fri, May 6, 2016 at 2:16 PM, Malaka Silva

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Willian, Thank you for the fix and your contribution. I went through the fix. Added few comments. Please send the pr. We will review again and merge. Fix will be available via store afterwards. On Fri, May 6, 2016 at 5:19 PM, Willian Antunes < willian.lima.antu...@gmail.com> wrote: >

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

It's created: https://wso2.org/jira/browse/ESBCONNECT-92 Thank you! On Thu, Apr 28, 2016 at 12:52 AM, Malaka Silva wrote: > Hi Willian, > > Please report the issue in [1]. Our team will follow it. > > [1] https://wso2.org/jira/browse/ESBCONNECT > > On Thu, Apr 28, 2016 at

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

Hi Willian, Please report the issue in [1]. Our team will follow it. [1] https://wso2.org/jira/browse/ESBCONNECT On Thu, Apr 28, 2016 at 12:44 AM, Willian Antunes < willian.lima.antu...@gmail.com> wrote: > Hello community, > > I can connect smoothly using port 389 through LDAP Connector. There

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

I got it. As I was used to work with Apache Camel, I could you use something like below to change the data format: *from("file:wso2").marshal().xmljson().to("file:edglobo");* Thank you again! On Wed, Apr 27, 2016 at 7:54 AM, Malaka Silva wrote: > Hi Willian, > > ​ > No in

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

Hi Willian, ​ No in this case​ since response from service (connector) is soap. Only when the m ​e​ ssage format is application/json throughout the flow json will be used internally. On Tue, Apr 26, 2016 at 7:57 PM, Willian Antunes < willian.lima.antu...@gmail.com> wrote: > Guys, > > Internally

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

@Nuwan and @Malaka, I'm using LDAP Connector not a endpoint mediator itself. I tried with messageType but it didn't work. Thus I tried with the following as well without success: Does it apply to Connectors? In my case wouldn't be

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

Hi Willian, Do you want to change the message structure? If you don't need to change the message structure, you can change the axis2 messageType property to "json/application" and esb formatters will convert it to JSON. Eg: If you want to change the message structure you can use FastXSLT

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

Hi Willian, You could try setting the messageType property after getting the soap response. Find details in ESB docs with [1] [1] https://docs.wso2.com/display/ESB490/JSON+Support#JSONSupport-ConvertingapayloadbetweenXMLandJSON On Tue, Apr 26, 2016 at 2:47 AM, Willian Antunes <

Re: [Dev] [DEV] [ESB]

Hi Willian, You could try setting the messageType property after getting the soap response. Find details in ESB docs with [1] [1] https://docs.wso2.com/display/ESB490/JSON+Support#JSONSupport-ConvertingapayloadbetweenXMLandJSON On Tue, Apr 26, 2016 at 2:46 AM, Willian Antunes <

Re: [Dev] [DEV][ESB][Connector] Issue with empty response

Hi Carbon Team, I guess we are taking about the same issues mentioned in [1] Seems like the fix mentioned is in [2]. However in latest code found the fix [3] AFAIK the original fix is correct. [1] https://wso2.org/jira/browse/ESBJAVA-2575 [2] + if(in.available() != 0) { -in =

Re: [Dev] [DEV][ESB][Connector] Issue with empty response

Hi, Can you please share the wire logs. On Thu, Oct 8, 2015 at 1:00 PM, Jay wrote: > Hi All, > > When i developing ESB connector for Microsoft PowerBI there is a method > which returning empty response with the Content-Type: > application/octet-stream. And it is

Re: [Dev] [DEV][ESB][Connector] Issue with empty response

Hi, can you upload your axis.xml file also becasue its seems to be like a problem in message builder/formatter. On Thu, Oct 8, 2015 at 2:18 PM, Malaka Silva wrote: > Hi, > > Can you please share the wire logs. > > On Thu, Oct 8, 2015 at 1:00 PM, Jay

Re: [Dev] [DEV][ESB][Connector] Issue with empty response

Hi, I have attached both axis configuration and wire log here with. axis2.xml log.txt Thanks, Janaka -- View this message in context:

Re: [Dev] [DEV][ESB] Use of REST_URL_POSTFIX

For outbound RESTful invocations, it is recommended to use HTTP endpoint[1]. With that you can completely eliminate REST_URL_POSTFIX. [1] http://wso2.com/library/articles/2013/12/restful-integration-with-wso2-esb/ On Sat, Jun 13, 2015 at 3:25 PM, Malaka Silva mal...@wso2.com wrote: According

Re: [Dev] [DEV][ESB] Use of REST_URL_POSTFIX

According to the current logic it only worked for rest format. On Fri, Jun 12, 2015 at 8:45 PM, Chamila De Alwis chami...@wso2.com wrote: Hi Malaka, Thanks for response! Does this property only work for REST endpoints? I know it's named REST_URL_POSTFIX, however if I want to append some

Re: [Dev] [DEV][ESB] Use of REST_URL_POSTFIX

Hi Malaka, Thanks for response! Does this property only work for REST endpoints? I know it's named REST_URL_POSTFIX, however if I want to append some params to a SOAP endpoint do I have another option? Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2

Re: [Dev] [DEV][ESB] Use of REST_URL_POSTFIX

Ping! :) Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Jun 8, 2015 at 4:14 PM, Chamila De Alwis chami...@wso2.com wrote: Update: I created a simple API and used the Call mediator to call

Re: [Dev] [DEV][ESB] Use of REST_URL_POSTFIX

Can you try adding following to the endpoint and check format=rest eg:- send endpoint address uri= http://localhost:9000/services/SimpleStockQuoteService; format=rest/ address /endpoint /send On Thu, Jun 11, 2015 at 1:18

Re: [Dev] [DEV] ESB Elements are removed from Proxy Services UI

Hi Carbon Team, Any update? On Wed, Apr 22, 2015 at 9:58 PM, Malaka Silva mal...@wso2.com wrote: Jira added https://wso2.org/jira/browse/CARBON-15233 On Wed, Apr 22, 2015 at 2:25 PM, Malaka Silva mal...@wso2.com wrote: Hi Carbon Team, Some elements are missing in proxy details view.

Re: [Dev] [DEV] ESB Elements are removed from Proxy Services UI

Hi Malaka, Can you check if QoS features are added correctly ?. https://github.com/wso2/carbon-qos thanks, On Fri, Apr 24, 2015 at 9:35 AM, Malaka Silva mal...@wso2.com wrote: Hi Carbon Team, Any update? On Wed, Apr 22, 2015 at 9:58 PM, Malaka Silva mal...@wso2.com wrote: Jira added

Re: [Dev] [DEV] ESB Elements are removed from Proxy Services UI

Hi Supun, carbon-qos is a abandoned repo. We are no longer using it. What we are saying is while removing qos related options from service management ui, other important ui options has been removed. Thanks. On Fri, Apr 24, 2015 at 9:50 AM, Supun Malinga sup...@wso2.com wrote: Hi Malaka, Can

Re: [Dev] [DEV] ESB Elements are removed from Proxy Services UI

Jira added https://wso2.org/jira/browse/CARBON-15233 On Wed, Apr 22, 2015 at 2:25 PM, Malaka Silva mal...@wso2.com wrote: Hi Carbon Team, Some elements are missing in proxy details view. I guess this was result when removing QOS from service_info.jsp page. Options like active/inactive,

Re: [Dev] [DEV] [ESB] test case for using RequestHashGenerator in cache mediator

Merged. Thanks, Ishan. On Tue, Mar 31, 2015 at 6:53 PM, Gayan Dhanushka gay...@wso2.com wrote: Hi Ishan, Please merge pull request [1] done for [2]. [1] https://github.com/wso2/product-esb/pull/112 [2] https://wso2.org/jira/browse/APIMANAGER-1838 Regards Gayan -- Gayan Dhanuska

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

Hi Jagath, As discussed, there seems Value class has been changed to contain a SynapsePath instead of SynapseXPath [1]. So all variables that get assigned with value.getExpression() now needs to be changed to SynapseXPath, if they are still using SynapsePath. This will have to be fixed. [1]

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

Correction : All variables that get assigned with value.getExpression() now needs to be changed to SynapsePath, if they are still declared as SynapseXPath or they need to be casted to SynapseXPath. Thanks, Maheeka Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Mon, Mar 23, 2015

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

Hi Maheeka, Thanks for the support and I will do required changes and check. On Mon, Mar 23, 2015 at 6:42 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Correction : All variables that get assigned with value.getExpression() now needs to be changed to SynapsePath, if they are still declared

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

Seems to be so Jagath. What's the mediator that you have used? On Thursday, March 19, 2015, Jagath Sisirakumara Ariyarathne jaga...@wso2.com wrote: Hi, When I built and run wso2esb-4.9.0-M8-SNAPSHOT pack, it gives below type conversion error while opening validate mediator design view and

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

Hi Maheeka, I created a sequence and tried to add validate mediator. But cannot save it and gives the error. [image: Inline image 4] Thanks. On Sun, Mar 22, 2015 at 8:21 AM, Maheeka Jayasuriya mahe...@wso2.com wrote: Seems to be so Jagath. What's the mediator that you have used? On

Re: [Dev] [DEV][ESB] SynapseException when running the sample 57 of the ESB 4.8.1.

Hi Thusitha, If you use ESB 4.7.0, the sample runs successfully. Follow same procedure to configure and run as in latest documentation. But I also could not find a solution to run it with ESB 4.8.1 (latest version). On Wed, Jan 28, 2015 at 9:26 AM, Thusitha Thilina Dayaratne

Re: [Dev] [DEV][ESB] SynapseException when running the sample 57 of the ESB 4.8.1.

Hi Jagath, Thanks for the response. I will try to run using the ESB version 4.7.0 Regards On Wed, Jan 28, 2015 at 10:14 AM, Jagath Sisirakumara Ariyarathne jaga...@wso2.com wrote: Hi Thusitha, If you use ESB 4.7.0, the sample runs successfully. Follow same procedure to configure and run as

Re: [Dev] [DEV][ESB] SynapseException when running the sample 57 of the ESB 4.8.1.

Hi, This issue was previously discussed in dev. mailing list. It's because of mismatching of GroupManagementAgent. Pls find the relevant resource from following: http://mail.wso2.org/mailarchive/dev/2013-December/026247.html Thank you! On Wed, Jan 28, 2015 at 10:17 AM, Thusitha Thilina

Re: [Dev] [DEV][ESB] SynapseException when running the sample 57 of the ESB 4.8.1.

Hi Buddhima, Thanks for the response. I was able to run the sample using ESB version 4.7.0. Regards On Wed, Jan 28, 2015 at 10:21 AM, Buddhima Wijeweera buddh...@wso2.com wrote: Hi, This issue was previously discussed in dev. mailing list. It's because of mismatching of

Re: [Dev] [DEV] [ESB] Please Merge the Pull Request

Hi, Please ignore the previous pull request. I have created a new pull request [3] [3] https://github.com/wso2-dev/wso2-synapse/pull/182 Thanks Senduran On Mon, Nov 17, 2014 at 3:23 PM, Senduran Balasubramaniyam sendu...@wso2.com wrote: Hi, Please merge the pull request [1] to fix [2]

Re: [Dev] [DEV] [ESB] POST_TO_URI does not work in MT mode

Hi Guys, We can't think any reason to not doing that. I guess we can try this now? If something goes wrong we will see this in ESB 4.9.0 test fails? On Sun, Jun 22, 2014 at 9:36 AM, Malaka Silva mal...@wso2.com wrote: As advised by Miyuru added the property to [1] and it seems to be working.

Re: [Dev] [DEV] [ESB] POST_TO_URI does not work in MT mode

Hi, We can't think any reason to not doing that. I guess we can try this now? If something goes wrong we will see this in ESB 4.9.0 testing? Best Regards, Malaka On Sun, Jun 22, 2014 at 9:36 AM, Malaka Silva mal...@wso2.com wrote: As advised by Miyuru added the property to [1] and it seems

Re: [Dev] [DEV] [ESB] POST_TO_URI does not work in MT mode

Probably this property is not getting copied from Tenant MC to ST MC in tenant transport sender. On Sun, Jun 22, 2014 at 5:44 PM, Malaka Silva mal...@wso2.com wrote: Hi Guys, When I debugged the code it goes in this flow. Server Worker (m1) -- MultitenantMessageReceiver(m1 -- m2) --

Re: [Dev] [DEV] [ESB] POST_TO_URI does not work in MT mode

As advised by Miyuru added the property to [1] and it seems to be working. However can we loop all properties and add all at once instead of one by one? Any reason for not doing this? [1]

Re: [Dev] [DEV] [ESB] Can we increase height size of source view

Hi Please create a public jira, we will consider this but IMO this not a showstopper, as most of the time user experience relying on the DevS Cheers, Dushan On Fri, Jun 13, 2014 at 10:39 AM, Seshika Fernando sesh...@wso2.com wrote: Hi, Can we increase the height of the source view to

Re: [Dev] [DEV] [ESB]

Better to start the server with osgi console and cross check whether all the dependencies are got resolved or not. On Mon, May 5, 2014 at 10:36 PM, Malaka Silva mal...@wso2.com wrote: Hi, I build the pack from GIT. Following was found while starting the server. Any idea? Does this has

Re: [Dev] [DEV][ESB] Inbound EP File/vfs - Memory Leak

Hi Malaka, I doubt that's 'injectAsync' is the culprit, because this is tested with Iterate or clone mediators. Rather it could be due to the logic in inbound file endpoint . What heap dump shows us.. do we have many instances of mediation workers created and is that over the max limit of the

Re: [Dev] [DEV] [ESB] Problem running EIP Guide Publish-Subscribe scenario

OK, this is the second bug we are finding running the samples. This time it is EIP, but that too falls under try them out samples. We really got to get the integration tests going. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 12, 2013

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

Can you try with kernel patch0002? I added the fix for this. On Wed, Nov 6, 2013 at 11:53 AM, Dushan Abeyruwan dus...@wso2.com wrote: Done ! https://wso2.org/jira/browse/ESBJAVA-2624 On Wed, Nov 6, 2013 at 11:50 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Can you create a jira

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

To handle this particular scenario, we had to delay the CAppDeployer initialization (common to all servers). It was done by moving the initialization part to server start-up finalization component. Then once tenantServiceBus gets initialized, we could retrieve the related deployer using

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

Hi Kishanthan, We removed this due to [1] which was a blocker on chunk-01 release. The reason for this ConcurrentModificationException was adding the cApp deployer separately at runtime. As I can remember during this fix this deployer adding part from the StartupFinalizerComponent was also

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

Ok..whats the final verdict ? this blocks 480 release ... On Tue, Nov 5, 2013 at 11:05 PM, Manoj Kumara ma...@wso2.com wrote: Hi Kishanthan, We removed this due to [1] which was a blocker on chunk-01 release. The reason for this ConcurrentModificationException was adding the cApp deployer

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

Can you create a jira for this please? I'll look into it. On Wed, Nov 6, 2013 at 10:02 AM, Dushan Abeyruwan dus...@wso2.com wrote: Ok..whats the final verdict ? this blocks 480 release ... On Tue, Nov 5, 2013 at 11:05 PM, Manoj Kumara ma...@wso2.com wrote: Hi Kishanthan, We removed

Re: [Dev] [DEV] ESB 4.8.0 Deploying CAR artifacts broken [totally] for tenants due to deployment changers

Done ! https://wso2.org/jira/browse/ESBJAVA-2624 On Wed, Nov 6, 2013 at 11:50 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Can you create a jira for this please? I'll look into it. On Wed, Nov 6, 2013 at 10:02 AM, Dushan Abeyruwan dus...@wso2.com wrote: Ok..whats the final