Re: [Dev] Related to Configuring WSO2 ESB JMS transport

What is the error that you see? Did you check any of the use-cases mentioned[1] in the document for your reference? [1] https://docs.wso2.com/display/ESB490/JMS+Usecases On Fri, Jan 29, 2016 at 11:48 PM, Indrajith Udayakumara wrote: > Hi I am following the esb 4.9

Re: [Dev] Jenkins connector apiUrl is in diffent format

Hi Vanji, We reverted that PR. We also think about that issue and now I have changed port as optional. Now we didn't remove the previous implementation but we added simple if condition within the init method to check the port. User can give the port as optional. Now it will work for both giving

Re: [Dev] Related to Configuring WSO2 ESB JMS transport

Please share your axis2.xml [1] configuration [1]/repository/conf/axis2/axis2.xml On Sat, Jan 30, 2016 at 12:44 AM, Indrajith Udayakumara wrote: > This is the proxy service to be added. And I added it as a custom proxy in > the mgmt console. >

Re: [Dev] Jenkins connector apiUrl is in diffent format

@kalyani and @Malaka, rather than removing the previous implementation, you could have facilitated url only scenario with simple if condition. So that if some one is using this connector with host port combination will not get affected! Best Regards, Vanji

[Dev] WSO2 Committers += Malintha Amarasinghe

Hi, It is with great pleasure we welcome Malintha Amarasinghe as a WSO2 Committer. @Malintha, congratulations and keep up the good work! Thanks, NuwanD. -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729

Re: [Dev] Dev] [VOTE] Release WSO2 Business Process Server 3.5.1 RC2

​I have verified Pack contents and tested followings, - Tested Main BPEL functionalists in clustered environment ( LB : Nginx , DB : MySQL ) - Tested BPEL and Human Task Integration in clustered environment. - Tested Human Task Coordination in Super tenant and tenant mode. - Tested

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

congratz malintha... On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe wrote: > Congratzz Malintha :) > > On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias wrote: > >> Hi, >> >> It is with great pleasure we welcome Malintha Amarasinghe as a >> WSO2 Committer.

[Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

Hi, I have worked on writing Jaggery test for Jaggery-Product.I can observe when we tried to log the object it always gives us empty JSON ({}).Currently the implementation goes this way when we try to log java object. So I was trying to get rid of this observed behavior of Jaggery.I have gone

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

Congratzz Malintha :) On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias wrote: > Hi, > > It is with great pleasure we welcome Malintha Amarasinghe as a > WSO2 Committer. @Malintha, congratulations and keep up the good work! > > Thanks, > NuwanD. > > -- > Nuwan Dias > > Technical Lead

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

Congratulations ! On Sat, Jan 30, 2016 at 8:34 PM, Hasunie Adikari wrote: > Congratz Malintha > > On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga > wrote: > >> congratz malintha... >> >> On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe

Re: [Dev] WSO2 Committers += Malintha Amarasinghe

Congratz Malintha On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga wrote: > congratz malintha... > > On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe > wrote: > >> Congratzz Malintha :) >> >> On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

Hi Rajeenthini, AFAIK ability to convert a POJO into JSON object does nor affect the output of a Jaggery Log of that POJO. To get a proper log output for a Java object, you need to implement the "toString" method in that Java class. For example in your case, public class Student { ... public