Re: [Dev] Please review and merge

[Kathees Rajendram]

Hi Ishara/Hasanthi,

The PR is merged.

Thanks,
Kathees



On Fri, May 5, 2017 at 1:00 PM, Ishara Karunarathna <isha...@wso2.com>
wrote:

> Hi connector team,
>
> Can we get this merged ?
>
> -Ishara
>
> On Fri, May 5, 2017 at 10:11 AM, Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi Kathees
>>
>> Fixed the comments.
>>
>> Thanks,
>>
>> Hasanthi Dissanayake
>>
>> Software Engineer | WSO2
>>
>> E: hasan...@wso2.com
>> M :0718407133| http://wso2.com <http://wso2.com/>
>>
>> On Fri, May 5, 2017 at 9:45 AM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Thanks Hasanthi for your fix.
>>>
>>> Please fix those comments in the PR.
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Thu, May 4, 2017 at 3:16 PM, Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
>>>> Hi connector team,
>>>> Please review and merge [1] which fixes [2].
>>>> [1]https://github.com/wso2-extensions/identity-oauth2-grant-jwt/pull/14
>>>> [2]https://wso2.org/jira/browse/IDENTITY-5888
>>>>
>>>> Thanks,
>>>>
>>>> Hasanthi Dissanayake
>>>>
>>>> Software Engineer | WSO2
>>>>
>>>> E: hasan...@wso2.com
>>>> M :0718407133| http://wso2.com <http://wso2.com/>
>>>>
>>>
>>>
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173 <+94%2077%20259%206173>
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Kathees Rajendram]

Thanks Hasanthi for your fix.

Please fix those comments in the PR.

Thanks,
Kathees

On Thu, May 4, 2017 at 3:16 PM, Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi connector team,
> Please review and merge [1] which fixes [2].
> [1]https://github.com/wso2-extensions/identity-oauth2-grant-jwt/pull/14
> [2]https://wso2.org/jira/browse/IDENTITY-5888
>
> Thanks,
>
> Hasanthi Dissanayake
>
> Software Engineer | WSO2
>
> E: hasan...@wso2.com
> M :0718407133| http://wso2.com 
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when configuring EmailOTP with Email API

[Kathees Rajendram]

Hi Vishanth,

Are you using email OTP authenticator with SMTP transport or Email APIs?

Thanks,
Kathees

On Mon, Jan 30, 2017 at 11:40 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> Hi,
>
> I followed the steps mentioned in the docs [1]. I am not sure what exactly
> I need to set for the following configurations
>
>- SendgridFormData
>- SendgridURLParams
>
>
> I am getting the following error when I tried to do the 2 step
> authentication via Email OTP.
>
> [2017-01-30 11:30:35,087] ERROR {org.wso2.carbon.identity.
> authenticator.emailotp.EmailOTPAuthenticator} -  Unable to send the code
>
> org.wso2.carbon.identity.application.authentication.framework.exception.AuthenticationFailedException:
> Unable to send the code
>
> at org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.
> initiateAuthenticationRequest(EmailOTPAuthenticator.java:186)
>
> at org.wso2.carbon.identity.application.authentication.framework.
> AbstractApplicationAuthenticator.process(AbstractApplicationAuthenticat
> or.java:64)
>
> at org.wso2.carbon.identity.application.authentication.
> framework.handler.step.impl.DefaultStepHandler.doAuthentication(
> DefaultStepHandler.java:466)
> .
> .
> .
> Caused by: org.wso2.carbon.identity.application.authentication.
> framework.exception.AuthenticationFailedException: Unable to send the code
>
> at org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.
> initiateAuthenticationRequest(EmailOTPAuthenticator.java:186)
>
> ... 62 more
>
> [1] - https://docs.wso2.com/display/ISCONNECTORS/
> Configuring+EmailOTP+With+Email+APIs
>
>
> Regards,
> Vishanth
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth *
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Supporting MongoDB as a Secondary Userstore : an Extension for WSO2 Platform

[Kathees Rajendram]

Hi Tharindu,

Yes. We can add this MongoDB user store as an extension to WSO2 Store.

Thanks,
Kathees

On Mon, Jan 9, 2017 at 5:33 PM, Tharindu Edirisinghe 
wrote:

> Thanks for sharing the thread Vinod.
>
> In our project we would focus only on the user management.
>
> However later we can integrate the analytics as well together to build a
> complete usecase.
>
>
>
>
> On Mon, Jan 9, 2017 at 5:20 PM, Vinod Kavinda  wrote:
>
>> Hi All,
>> FYI, there is another attempt for using MongoDB with WSO2 Analytics. See
>> the Dev mail thread [1].
>>
>> [1] - "[Dev] [MongoDB] MongoDB support for analytics"
>>
>> On Mon, Jan 9, 2017 at 12:30 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I am willing to contribute and January (30, 31) is ok for me for a
>>> meeting
>>>
>>> thanks,
>>> Asantha
>>>
>>> On Sun, Jan 8, 2017 at 10:20 PM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Devs,

 Along with Google Summer of Code 2016, we initiated this project [1]
 for supporting MongoDB as a secondary userstore for WSO2 products.

 Asantha (CC'ed) here successfully completed the project where it
 supported IS 5.1.0. (for IS 5.2.0 we need to do some minor modification to
 get it to working and for IS 5.3.0 which is about to be released.. we'll
 have to do some more changes because the claim management API is changed).

 We cannot ship this with a WSO2 product, because it is not scalable.
 The end user might use a different version of MongoDB database or JDBC
 driver, releasing patches would be difficult if any bug is found etc.

 Therefore the best way is to develop it as a connector (extension) and
 publicly release to WSO2 store.

 For that, I am initiating this email where we can discuss on how to
 proceed with this.

 @Kathees - I hope you can take the ownership of this. We can get
 Asantha's help as well whenever necessary.

 My idea is to have a meeting for this during the last week of January
 (30,31) and come up with a plan.

 [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+201
 6#ProjectProposalsfor2016-Proposal21:[IS]DocumentBasedNoSQLS
 upportforWSO2IdentityServerDatabase

 Thanks,
 TharinduE

 --

 Tharindu Edirisinghe
 Senior Software Engineer | WSO2 Inc
 Platform Security Team
 Blog : tharindue.blogspot.com
 mobile : +94 775181586 <+94%2077%20518%201586>

>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>> [image: http://wso2.com/signature]
>> 
>>
>>
>
>
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CAS is not working when the application is a SaaS app

[Kathees Rajendram]

Hi Hasintha,

The authenticator is released with the fix [1]. Please find the
authenticator [2] in the store.

[1] - https://wso2.org/jira/browse/ISCONNECT-40
[2] -
https://store.wso2.com/store/assets/isconnector/details/f17abed7-ee3d-4832-b95c-7285310125f0
<https://wso2.org/jira/browse/ISCONNECT-40>
Thanks,
Kathees

On Fri, Nov 18, 2016 at 2:32 PM, Kathees Rajendram <kath...@wso2.com> wrote:

> Yes, we will release the version of authenticator with this fix. Can you
> please create a public jira to track this issue?
>
> Thanks,
> Kathees
>
> On Fri, Nov 18, 2016 at 2:11 PM, Hasintha Indrajee <hasin...@wso2.com>
> wrote:
>
>> Hi Kathees,
>>
>> As per offline discussion with you the issue is there and need to be
>> fixed. Apart from that I couldn't change the subject claim using "Subject
>> Claim URI:". Can we get this fixed please ?
>>
>> On Wed, Nov 16, 2016 at 5:19 PM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 16, 2016 at 5:03 PM, Hasintha Indrajee <hasin...@wso2.com>
>>> wrote:
>>>
>>>> This is with a custom claim mapping right ?. I couldn't get requested
>>>> claim without a custom claim mapping. Is there anything I am overlooking ?
>>>>
>>>
>>> Yes. I checked SAML2 service provider claim mapping and it works same.
>>> Please correct me if it is wrong.
>>>
>>>>
>>>>
>>>> On Wed, Nov 16, 2016 at 5:01 PM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Hasintha
>>>>>
>>>>> On Wed, Nov 16, 2016 at 12:54 PM, Hasintha Indrajee <hasin...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 16, 2016 at 12:25 PM, Hasintha Indrajee <
>>>>>> hasin...@wso2.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee <
>>>>>>> hasin...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Please find the below fix for this issue. This includes an API
>>>>>>>> change. Please review and merge this fix.
>>>>>>>>
>>>>>>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>>>>>>> -cas/pull/10
>>>>>>>>
>>>>>>>
>>>>>>> This fix only returns subject. I think we need to improve it to
>>>>>>> return attributes as well.
>>>>>>>
>>>>>>
>>>>>> Sorry. Not getting attributes is a general behaviour I have observed
>>>>>> for super tenant users as well. I configured requested claims and still
>>>>>> couldn't get user claims. There seems to be an issue.
>>>>>>
>>>>>
>>>>> I was able to get the attributes with your fix by enabling "Requested
>>>>> Claim" check box in service provider. Please check and confirm.
>>>>>
>>>>> ​
>>>>>
>>>>>>
>>>>>>>> On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva <mal...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Kanapriya can you have a quick look and update with findings
>>>>>>>>> please?
>>>>>>>>>
>>>>>>>>> On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee <
>>>>>>>>> hasin...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi All,
>>>>>>>>>>
>>>>>>>>>> CAS is not working when we register a SaaS application and when I
>>>>>>>>>> am trying to login from a different tenant user. This should be 
>>>>>>>>>> supported
>>>>>>>>>> by CAS authentication as it is a basic requirement.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Hasintha Indrajee
>>>>>>>>>> WSO2, Inc.
>>>>>>>>>> Mobile:+94 771892453
>>>>>>>>>>
>>>>>>>>>>
>>>>&

Re: [Dev] File read with enabling streaming

[Kathees Rajendram]

If the datasource from your operation is not instance of
StreamingOnRequestDataSource and you can directly write. In this case, you
don't need to cast.

On Fri, Nov 25, 2016 at 10:20 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Malaka,
>
> I am getting the casting exception in the following methods in the
> carbon-mediation[1].
>
> private void findAndWrite2OutputStream(MessageContext messageContext,
>OutputStream out,
>boolean preserve) throws
> AxisFault {
> try {
> SOAPEnvelope envelope = messageContext.getEnvelope();
>   OMElement contentEle = envelope.getBody().getFirstElement();
> if (contentEle != null) {
> OMNode node = contentEle.getFirstOMChild();
> if (!(node instanceof OMText)) {
> String msg = "Wrong Input for the Validator, " +
> "the content of the first child element of the
> Body " +
> "should have the zip file";
> log.error(msg);
> throw new AxisFault(msg);
> }
> OMText binaryDataNode = (OMText) node;
> DataHandler dh = (DataHandler)
> binaryDataNode.getDataHandler();
>
> DataSource dataSource = dh.getDataSource();
> if (((StreamingOnRequestDataSource)
> dataSource).isConsumed()) {
> Object httpMethodObj = messageContext.getProperty(
> Constants.Configuration.HTTP_METHOD);
> if ((httpMethodObj instanceof String) &&
> "POST".equals(httpMethodObj)) {
> log.warn("Attempting to send an already
> consumed request [" +
>  messageContext.getTo().getAddress()
> + " POST/Empty Message Body]");
> }
> }
>
> //Ask the data source to stream, if it has not already
> cached the request
> if (!preserve && dataSource instanceof
> StreamingOnRequestDataSource) {
> ((StreamingOnRequestDataSource)
> dataSource).setLastUse(true);
> }
>
> dh.writeTo(out);
> }
> } catch (OMException e) {
> log.error(e);
> throw AxisFault.makeFault(e);
> } catch (IOException e) {
> log.error(e);
> throw AxisFault.makeFault(e);
> }
> }
>
>
> [1] https://github.com/wso2/carbon-mediation/blob/master/
> components/mediation-monitor/message-relay/org.wso2.carbon.
> relay/src/main/java/org/wso2/carbon/relay/ExpandingMessageFormatter.
> java#L185
>
> Vivekananthan Sivanayagam
> Associate Software Engineer | WSO2
> E:vivekanant...@wso2.com
> M:+94752786138
>
> On Thu, Nov 24, 2016 at 4:30 PM, Malaka Silva  wrote:
>
>>
>>
>> On Thu, Nov 24, 2016 at 4:25 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> When I enable builders as I mentioned in the previous mail, It is
>>> working always for the false statement[1] of streaming even enabling the
>>> streaming. We have to use ">> class="org.apache.axis2.format.BinaryBuilder"/>", If I use this one, I
>>> am getting
>>> "PassThroughHttpSender Failed to submit the response" error.
>>>
>> ​We have to dig into this and find the root cause.​
>>
>>
>>>
>>> We were able to write the file content into the message context but
>>> could not get this as a response, and I checked the test case and found the
>>> reason why it worked, there streaming is set as true and content type is
>>> as "text/plain", in this case also consider as an else statement, that is
>>> why test cases are passed.
>>>
>> ​Currently latest connector read does not work. So ideally the test case
>> should fail.​
>>
>>
>>>
>>> [1]
>>>
>>> ​
>>> ​
>>> InputStream in;
>>>
>>> if (builder instanceof DataSourceMessageBuilder && 
>>> "true".equals(streaming)) {
>>> in = null;
>>> dataSource = ManagedDataSourceFactory.create(new 
>>> FileObjectDataSource(file, contentType));
>>> } else {
>>> in = new AutoCloseInputStream(file.getContent().getInputStream());
>>> dataSource = null;
>>> }
>>>
>>>
>>> Vivekananthan Sivanayagam
>>> Associate Software Engineer | WSO2
>>> E:vivekanant...@wso2.com
>>> M:+94752786138
>>>
>>> On Thu, Nov 24, 2016 at 10:23 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
 Hi Malaka,

 When I use ">>> class="org.wso2.carbon.relay.BinaryRelayBuilder"/>" instead of
 ">>> class="org.apache.axis2.format.BinaryBuilder"/>", it is working fine.

 Vivekananthan Sivanayagam
 Associate Software Engineer | WSO2
 E:vivekanant...@wso2.com
 M:+94752786138

 On Wed, Nov 23, 2016 at 3:26 PM, Vivekananthan Sivanayagam <
 vivekanant...@wso2.com> wrote:

> Hi Makala,

Re: [Dev] CAS is not working when the application is a SaaS app

[Kathees Rajendram]

Yes, we will release the version of authenticator with this fix. Can you
please create a public jira to track this issue?

Thanks,
Kathees

On Fri, Nov 18, 2016 at 2:11 PM, Hasintha Indrajee <hasin...@wso2.com>
wrote:

> Hi Kathees,
>
> As per offline discussion with you the issue is there and need to be
> fixed. Apart from that I couldn't change the subject claim using "Subject
> Claim URI:". Can we get this fixed please ?
>
> On Wed, Nov 16, 2016 at 5:19 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>>
>>
>> On Wed, Nov 16, 2016 at 5:03 PM, Hasintha Indrajee <hasin...@wso2.com>
>> wrote:
>>
>>> This is with a custom claim mapping right ?. I couldn't get requested
>>> claim without a custom claim mapping. Is there anything I am overlooking ?
>>>
>>
>> Yes. I checked SAML2 service provider claim mapping and it works same.
>> Please correct me if it is wrong.
>>
>>>
>>>
>>> On Wed, Nov 16, 2016 at 5:01 PM, Kathees Rajendram <kath...@wso2.com>
>>> wrote:
>>>
>>>> Hi Hasintha
>>>>
>>>> On Wed, Nov 16, 2016 at 12:54 PM, Hasintha Indrajee <hasin...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Nov 16, 2016 at 12:25 PM, Hasintha Indrajee <hasin...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee <hasin...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Please find the below fix for this issue. This includes an API
>>>>>>> change. Please review and merge this fix.
>>>>>>>
>>>>>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>>>>>> -cas/pull/10
>>>>>>>
>>>>>>
>>>>>> This fix only returns subject. I think we need to improve it to
>>>>>> return attributes as well.
>>>>>>
>>>>>
>>>>> Sorry. Not getting attributes is a general behaviour I have observed
>>>>> for super tenant users as well. I configured requested claims and still
>>>>> couldn't get user claims. There seems to be an issue.
>>>>>
>>>>
>>>> I was able to get the attributes with your fix by enabling "Requested
>>>> Claim" check box in service provider. Please check and confirm.
>>>>
>>>> ​
>>>>
>>>>>
>>>>>>> On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva <mal...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Kanapriya can you have a quick look and update with findings please?
>>>>>>>>
>>>>>>>> On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee <
>>>>>>>> hasin...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> CAS is not working when we register a SaaS application and when I
>>>>>>>>> am trying to login from a different tenant user. This should be 
>>>>>>>>> supported
>>>>>>>>> by CAS authentication as it is a basic requirement.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Hasintha Indrajee
>>>>>>>>> WSO2, Inc.
>>>>>>>>> Mobile:+94 771892453
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>>
>>>>>>>> Malaka Silva
>>>>>>>> Senior Technical Lead
>>>>>>>> M: +94 777 219 791
>>>>>>>> Tel : 94 11 214 5345
>>>>>>>> Fax :94 11 2145300
>>>>>>>> Skype : malaka.sampath.silva
>>>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>>>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>>>>>
>>>>>>>> WSO2, Inc.
>>>>>>>> lean . enterprise . middleware
>>>>>>>> https://wso2.com/signature
>>>>>>>> http://www.wso2.com/about/team/malaka-silva/
>>>>>>>> <http://wso2.com/about/team/malaka-silva/>
>>>>>>>> https://store.wso2.com/store/
>>>>>>>>
>>>>>>>> Don't make Trees rare, we should keep them with care
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Hasintha Indrajee
>>>>>>> WSO2, Inc.
>>>>>>> Mobile:+94 771892453
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Hasintha Indrajee
>>>>>> WSO2, Inc.
>>>>>> Mobile:+94 771892453
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Hasintha Indrajee
>>>>> WSO2, Inc.
>>>>> Mobile:+94 771892453
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Kathees
>>>> Software Engineer,
>>>> email: kath...@wso2.com
>>>> mobile: +94772596173
>>>>
>>>
>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CAS is not working when the application is a SaaS app

[Kathees Rajendram]

On Wed, Nov 16, 2016 at 5:03 PM, Hasintha Indrajee <hasin...@wso2.com>
wrote:

> This is with a custom claim mapping right ?. I couldn't get requested
> claim without a custom claim mapping. Is there anything I am overlooking ?
>

Yes. I checked SAML2 service provider claim mapping and it works same.
Please correct me if it is wrong.

>
>
> On Wed, Nov 16, 2016 at 5:01 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi Hasintha
>>
>> On Wed, Nov 16, 2016 at 12:54 PM, Hasintha Indrajee <hasin...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 16, 2016 at 12:25 PM, Hasintha Indrajee <hasin...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee <hasin...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Please find the below fix for this issue. This includes an API change.
>>>>> Please review and merge this fix.
>>>>>
>>>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>>>> -cas/pull/10
>>>>>
>>>>
>>>> This fix only returns subject. I think we need to improve it to return
>>>> attributes as well.
>>>>
>>>
>>> Sorry. Not getting attributes is a general behaviour I have observed for
>>> super tenant users as well. I configured requested claims and still
>>> couldn't get user claims. There seems to be an issue.
>>>
>>
>> I was able to get the attributes with your fix by enabling "Requested
>> Claim" check box in service provider. Please check and confirm.
>>
>> ​
>>
>>>
>>>>> On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>>>
>>>>>> Kanapriya can you have a quick look and update with findings please?
>>>>>>
>>>>>> On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee <
>>>>>> hasin...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> CAS is not working when we register a SaaS application and when I am
>>>>>>> trying to login from a different tenant user. This should be supported 
>>>>>>> by
>>>>>>> CAS authentication as it is a basic requirement.
>>>>>>>
>>>>>>> --
>>>>>>> Hasintha Indrajee
>>>>>>> WSO2, Inc.
>>>>>>> Mobile:+94 771892453
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Malaka Silva
>>>>>> Senior Technical Lead
>>>>>> M: +94 777 219 791
>>>>>> Tel : 94 11 214 5345
>>>>>> Fax :94 11 2145300
>>>>>> Skype : malaka.sampath.silva
>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>>>
>>>>>> WSO2, Inc.
>>>>>> lean . enterprise . middleware
>>>>>> https://wso2.com/signature
>>>>>> http://www.wso2.com/about/team/malaka-silva/
>>>>>> <http://wso2.com/about/team/malaka-silva/>
>>>>>> https://store.wso2.com/store/
>>>>>>
>>>>>> Don't make Trees rare, we should keep them with care
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Hasintha Indrajee
>>>>> WSO2, Inc.
>>>>> Mobile:+94 771892453
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Hasintha Indrajee
>>>> WSO2, Inc.
>>>> Mobile:+94 771892453
>>>>
>>>>
>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CAS is not working when the application is a SaaS app

[Kathees Rajendram]

Hi Hasintha

On Wed, Nov 16, 2016 at 12:54 PM, Hasintha Indrajee 
wrote:

>
>
> On Wed, Nov 16, 2016 at 12:25 PM, Hasintha Indrajee 
> wrote:
>
>>
>>
>> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please find the below fix for this issue. This includes an API change.
>>> Please review and merge this fix.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/10
>>>
>>
>> This fix only returns subject. I think we need to improve it to return
>> attributes as well.
>>
>
> Sorry. Not getting attributes is a general behaviour I have observed for
> super tenant users as well. I configured requested claims and still
> couldn't get user claims. There seems to be an issue.
>

I was able to get the attributes with your fix by enabling "Requested
Claim" check box in service provider. Please check and confirm.

​

>
>>> On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva  wrote:
>>>
 Kanapriya can you have a quick look and update with findings please?

 On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee 
 wrote:

> Hi All,
>
> CAS is not working when we register a SaaS application and when I am
> trying to login from a different tenant user. This should be supported by
> CAS authentication as it is a basic requirement.
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>


 --

 Best Regards,

 Malaka Silva
 Senior Technical Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 https://wso2.com/signature
 http://www.wso2.com/about/team/malaka-silva/
 
 https://store.wso2.com/store/

 Don't make Trees rare, we should keep them with care

>>>
>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CAS is not working when the application is a SaaS app

[Kathees Rajendram]

Yes. Will release a version of CAS inbound with this fix.


Thanks,
Kathees

On Wed, Nov 16, 2016 at 8:22 AM, Malaka Silva  wrote:

> Hi Kathees,
>
> Can you check this and release the fix to store please?
>
> On Tue, Nov 15, 2016 at 10:36 PM, Kanapriya Kuleswararajan <
> kanapr...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> I have tested existing cas-inbound-authenticator by enable the SaaS
>> application in super tenant domain and try to login from different tenant
>> domain. But I couldn't login with different tenant domain.
>>
>> I checked with above fix also, It works fine when the application is a
>> SaaS app.
>>
>> Thanks
>>
>> Kanapriya Kuleswararajan
>> Associate Software Engineer
>> Mobile : - 0774894438
>> Mail : - kanapr...@wso2.com
>>
>> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please find the below fix for this issue. This includes an API change.
>>> Please review and merge this fix.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/10
>>>
>>> On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva  wrote:
>>>
 Kanapriya can you have a quick look and update with findings please?

 On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee 
 wrote:

> Hi All,
>
> CAS is not working when we register a SaaS application and when I am
> trying to login from a different tenant user. This should be supported by
> CAS authentication as it is a basic requirement.
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>


 --

 Best Regards,

 Malaka Silva
 Senior Technical Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 https://wso2.com/signature
 http://www.wso2.com/about/team/malaka-silva/
 
 https://store.wso2.com/store/

 Don't make Trees rare, we should keep them with care

>>>
>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CAS connector doesnt work with federated authenticators.

[Kathees Rajendram]

SAML-Protocol support is another feature in CAS. Please find few more
resources for other protocols (OpenID,OAuth and SAML) supports as
extensions in CAS protocol.

https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.html
https://apereo.github.io/cas/4.2.x/protocol/SAML-Protocol.html

Thanks,
Kathees

On Tue, Nov 1, 2016 at 9:33 PM, Hasintha Indrajee  wrote:

> If this is the case then we should fix this in the sample cas client
> webapp.
>
> On Tue, Nov 1, 2016 at 9:28 PM, Harsha Thirimanna 
> wrote:
>
>> So in your case, I feel like there should be missing the relyingParty
>> value to pick the correct service provider to get the configured
>> authentication options.
>>
>> *Harsha Thirimanna*
>> Associate Tech Lead | WSO2
>>
>> Email: hars...@wso2.com
>> Mob: +94715186770
>> Blog: http://harshathirimanna.blogspot.com/
>> Twitter: http://twitter.com/harshathirimann
>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>> rsha-thirimanna/10/ab8/122
>> 
>>
>> On Tue, Nov 1, 2016 at 9:15 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi Harsha,
>>>
>>> Following are the resources you can get information about CAS (Provided
>>> by Kanapriya)
>>>
>>> https://docs.wso2.com/display/ISCONNECTORS/CAS+Inbound+Authenticator
>>> https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/2
>>> https://github.com/apereo/cas/blob/master/docs/cas-server-do
>>> cumentation/protocol/CAS-Protocol-Specification.md
>>> https://github.com/UniconLabs/cas-sample-java-webapp
>>> https://wiki.jasig.org/display/CASC/Configuring+the+Jasig+CA
>>> S+Client+for+Java+in+the+web.xml
>>>
>>> On Tue, Nov 1, 2016 at 7:56 PM, Harsha Thirimanna 
>>> wrote:
>>>
 Hi Hasintha,

 Did you get any documentation for this to know the request and
 configuration details with CAS ?

 *Harsha Thirimanna*
 Associate Tech Lead | WSO2

 Email: hars...@wso2.com
 Mob: +94715186770
 Blog: http://harshathirimanna.blogspot.com/
 Twitter: http://twitter.com/harshathirimann
 Linked-In: linked-in: http://www.linkedin.com/pub/ha
 rsha-thirimanna/10/ab8/122
 

 On Tue, Nov 1, 2016 at 5:52 PM, Hasintha Indrajee 
 wrote:

> Hi,
>
> I was trying to login through CAS as inbound protocol and I used
> facebook as a federated authenticator. This scenario didn't work, It 
> always
> prompt me Identity Server's basic auth login page. Aren't we supporting
> this case ? Ideally we should support this right ?. Or am I missing
> something here ?
>
> Also Do we have any idea to implement "samlValidate" in CAS near
> future ?
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.2.0- RC1

[Kathees Rajendram]

Hi,

Tested the following authenticators.

   - SMS OTP
   - Email OTP

No blocking issue found.

[+] Stable - go ahead and release

Thanks,
Kathees

On Thu, Sep 15, 2016 at 12:13 PM, Darshana Gunawardana 
wrote:

> Hi Devs,
>
> Tested,
>
>- SAML SSO
>- Federation
>- JIT Provisioning
>- Google Provisioning
>
> Did not find any blocking issue.
>
> So here's my vote,
>
> [+] Stable - go ahead and release
>
> Thanks,
>
> On Wed, Sep 14, 2016 at 2:59 AM, Hasintha Indrajee 
> wrote:
>
>> Tested IS Analytics including
>>
>>
>>1. Enabling and disabling analytics (publishers),
>>2. Data publishing through publishers.
>>3. Analytics Dashboard functionalities.
>>4. Session Analytics
>>5. Login Analytics
>>
>>
>>-  Variation over time
>>-  Drilling down from different attributes
>>-  Content of data table
>>
>> No blocking issues found.
>> [+] Stable - go ahead and release
>>
>>
>> On Sat, Sep 10, 2016 at 7:48 AM, Kasun Bandara  wrote:
>>
>>> Hi All,
>>>
>>> This is the 1st Release Candidate of WSO2 Identity Server 5.2.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=13329
>>>
>>> Source and distribution
>>>
>>> Run-time   : https://github.com/wso2/produc
>>> t-is/releases/tag/v5.2.0-rc1
>>> Analytics   : https://github.com/wso2/analyt
>>> ics-is/releases/tag/v5.2.0-rc1
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 Identity Server Team -
>>>
>>> --
>>> Kasun Bandara
>>> *Software Engineer*
>>> Mobile : +94 (0) 718 338 360
>>> <%2B94%20%280%29%20773%20451194>
>>> kas...@wso2.com 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding JIRA connector.

[Kathees Rajendram]

Hi Bhashinee,

Now we have the jira connector code in the location [1]. All connectors
from esb-connectors repo [2] are moved to wso2-extensions location [3].

[1] - https://github.com/wso2-extensions/esb-connector-jira
[2] - https://github.com/wso2-attic/esb-connectors 
[3] - https://github.com/wso2-extensions

Thanks,
Kathees

On Mon, Jun 27, 2016 at 6:10 PM, Bhashinee Nirmali 
wrote:

> Hi All,
>
> There is a mismatch between the create issue in JIRA connector
> documentation[1] and the createIssue.xml in github[2]. There is no such
> parameter named "issueFields" in createIssue.xml. Kindly someone point me
> to the latest code?
>
> [1]
> https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Issues+in+JIRA#WorkingwithIssuesinJIRA-createIssue
>
> [2]
> https://github.com/wso2-attic/esb-connectors/blob/master/jira/jira-connector/jira-connector-2.0.0/org.wso2.carbon.connector/src/main/resources/jira_issue/createIssue.xml
>
>
> Thanks
> --
> *Bhashinee Nirmali*
> Software Engineering Intern
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 712150003 <%2B94%20%280%29%20716%20590818>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PET] Getting error when calling the endpoint template within call mediator blocking true

[Kathees Rajendram]

Hi Malaka,

The TemplatEndpoint fix should be with isLeafEndpoint checking. Since this
was blocker, I gave quick fix. Will arrange the code review with IsuruU
tomorrow.

Thanks,
Kathees

On Mon, Jun 20, 2016 at 10:58 AM, Kalyani Yogeswaranathan <kaly...@wso2.com>
wrote:

> Hi Kathees,
>
> I have tested salesforce connector with the provided patch. Its working
> fine for calling the endpoint template within call mediator blocking true.
>
> Thanks
>
> On Mon, Jun 20, 2016 at 8:41 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Kathees,
>>
>> Thank you for taking the initiative of checking this :)
>>
>> However removing the isLeafEndpoint check can cause some other issues.
>>
>> Best we review the fix with ESB team.
>>
>> Can you arrange a code review this week and invite IsuruU please.
>>
>> On Sun, Jun 19, 2016 at 3:33 PM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have added the improvement[1] to support templateEndpoint in
>>> callMediator blocking mode in ESB 5.0.0.
>>>
>>> @Kalyani
>>> You can continue the connector implementation with the patch [2]. The
>>> improvement will be included in ESB 5.0.0.
>>>
>>> [1] - https://wso2.org/jira/browse/ESBJAVA-4687
>>> [2] -
>>> https://drive.google.com/file/d/0B-oWbuBPpKK9WGRYNlY3ZFBhZEk/view?usp=sharing
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Thu, Jun 16, 2016 at 7:19 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> AFAIK we cannot use templates with call mediator in blocking mode.
>>>>
>>>> @ESB Team please confirm if this is still the case with ESB 5.0.0
>>>>
>>>>
>>>> On Thu, Jun 16, 2016 at 2:16 PM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Kalyani,
>>>>>
>>>>> You can get the parameter value from init method (
>>>>> {$ctx:salesforce.timeout}) in the template. Instead of adding
>>>>> endpoints in different template, you can add the endpoint in the template
>>>>> for blocking calls. The endpoint timeout can be different between API
>>>>> methods and we need to adjust the timeout value for some api methods. So 
>>>>> we
>>>>> can include the endpoint configuration inside the template rather than
>>>>> adding in common template.
>>>>>
>>>>> http://ws.apache.org/ns/synapse;>
>>>>> 
>>>>> >>>>description="Progress factor for timeout of the API
>>>>> request."/>
>>>>> >>>>description="Maximum duration for timeout of the API
>>>>> request."/>
>>>>> 
>>>>> >>>>description="It is used to specify the action to
>>>>> perform once an endpoint has timed out."/>
>>>>> 
>>>>>
>>>>>  
>>>>> 
>>>>> 
>>>>> 
>>>>> -1
>>>>> 
>>>>> 
>>>>> -1
>>>>> 2000
>>>>> 1.0
>>>>> 3000
>>>>> 
>>>>> 
>>>>> {$ctx:salesforce.timeout}
>>>>> fault
>>>>> 
>>>>> 
>>>>>   
>>>>>  
>>>>> 
>>>>>
>>>>> Thanks,
>>>>> Kathees
>>>>>
>>>>> On Thu, Jun 16, 2016 at 1:58 PM, Kalyani Yogeswaranathan <
>>>>> kaly...@wso2.com> wrote:
>>>>>
>>>>>> Hi Al,
>>>>>>
>>>>>> I am working on salesforce connector to add dynamic endpoint. For
>>>>>> that I've wrote a separate template as [1] and calling this template 
>>>>>> within
>>>>>> call mediator,
>>>>>>
>>>>>> It's working fine for blocking false when i call endpoint template,
>>>>>> but it's not working for blocking true[2].
>>>>>>
>>>>>> [2]
>>>>>>
>>>>>> 
>>>>>>   

Re: [Dev] [PET] Getting error when calling the endpoint template within call mediator blocking true

[Kathees Rajendram]

Hi,

I have added the improvement[1] to support templateEndpoint in callMediator
blocking mode in ESB 5.0.0.

@Kalyani
You can continue the connector implementation with the patch [2]. The
improvement will be included in ESB 5.0.0.

[1] - https://wso2.org/jira/browse/ESBJAVA-4687
[2] -
https://drive.google.com/file/d/0B-oWbuBPpKK9WGRYNlY3ZFBhZEk/view?usp=sharing

Thanks,
Kathees

On Thu, Jun 16, 2016 at 7:19 PM, Malaka Silva <mal...@wso2.com> wrote:

> AFAIK we cannot use templates with call mediator in blocking mode.
>
> @ESB Team please confirm if this is still the case with ESB 5.0.0
>
>
> On Thu, Jun 16, 2016 at 2:16 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi Kalyani,
>>
>> You can get the parameter value from init method (
>> {$ctx:salesforce.timeout}) in the template. Instead of adding endpoints
>> in different template, you can add the endpoint in the template for
>> blocking calls. The endpoint timeout can be different between API methods
>> and we need to adjust the timeout value for some api methods. So we can
>> include the endpoint configuration inside the template rather than adding
>> in common template.
>>
>> http://ws.apache.org/ns/synapse;>
>> 
>> >description="Progress factor for timeout of the API
>> request."/>
>> >description="Maximum duration for timeout of the API
>> request."/>
>> 
>> >description="It is used to specify the action to perform
>> once an endpoint has timed out."/>
>> 
>>
>>  
>> 
>> 
>> 
>> -1
>> 
>> 
>> -1
>> 2000
>> 1.0
>> 3000
>> 
>> 
>> {$ctx:salesforce.timeout}
>> fault
>> 
>> 
>>   
>>  
>> 
>>
>> Thanks,
>> Kathees
>>
>> On Thu, Jun 16, 2016 at 1:58 PM, Kalyani Yogeswaranathan <
>> kaly...@wso2.com> wrote:
>>
>>> Hi Al,
>>>
>>> I am working on salesforce connector to add dynamic endpoint. For that
>>> I've wrote a separate template as [1] and calling this template within call
>>> mediator,
>>>
>>> It's working fine for blocking false when i call endpoint template, but
>>> it's not working for blocking true[2].
>>>
>>> [2]
>>>
>>> 
>>> >>   
>>> template="org.wso2.carbon.connector.salesforce.salesforceEndPoint">
>>> 
>>> 
>>> 
>>>
>>> but if I add the whole endpoint[3], rather than calling endpoint template 
>>> it's working fine.
>>>
>>> [3]
>>> 
>>> 
>>> 
>>> 
>>> -1
>>> 
>>> 
>>> -1
>>> 2000
>>> 1.0
>>> 3000
>>> 
>>> 
>>> {$ctx:salesforce.timeout}
>>> fault
>>> 
>>> 
>>> 
>>> 
>>>
>>> Is there any other way to call endpoint template within call mediator
>>> with blocking true?
>>>
>>>
>>> [1]
>>>
>>> http://ws.apache.org/ns/synapse;>
>>> 
>>> >>description="Progress factor for timeout of the API 
>>> request."/>
>>> >>description="Maximum duration for timeout of the API 
>>> request."/>
>>> 
>>> >>description="It is used to specify the action to perform 
>>> once an endpoint has timed out."/>
>>> 
>>> 
>>> 
>>> 
>>> -1
>>> 
>>> 
>>> -1
>>> 2000
>>> 1.0
>>> 3000
>>> 
>>> 
>>> {$ctx:salesforce.timeout}
>>> fault
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>>
>>> *Kalyani Yogeswaranathan*
>>>
>>> *Associate software engineer*
>>> *WSO2 Inc.*
>>>
>>> *Mobile: 0776390284 <0776390284>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Socket connection closed while trying ESB connector operation.

[Kathees Rajendram]

Hi Shakila,

Since you are using PUT operation without body, Can you try the following
property to remove the entry body from HTTP request.




Thanks,
Kathees

On Thu, Jun 16, 2016 at 4:41 PM, Shakila Sivagnanarajah 
wrote:

> Hi,
>
> I sent the request without setting the payload entity using a proxy
> service [1], It works fine. But in my template, I remove the previous
> payload using 'FORCE_POST_PUT_NOBODY'. It seems the problem is the payload.
>
> [1]
> 
> 
> 
> 
>  value="256"/>
>  value="xx"/>
>  scope="transport" value="bytes=0-9"/>
>  value="application/xml; charset=UTF-8"/>
> 
>  value="/bucketName/testFile.jpg"/>
>  value="256"/>
> 
> 
> http://1466064852454testconbkt2.s3-us-west-2.amazonaws.com/testFile1.txt?partNumber=2uploadId=wdU0iM8SaNaGzHyFiUEHEk4WTqkL2jC_LHTeLZ3EjTLjsB8WVELvbH.XHcCrToRQQRtDAjr_kWv0JPk_7vacLVevdCjje11_pYuEjes2Ev1erXifpt.gdKmgtXU0VLP1
> "/>
> 
> 
> 
> 
> 
> 
>
> Thanks
>
> On Thu, Jun 16, 2016 at 9:46 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi Shakila,
>>
>> Can you compare the request sending from ESB(using wirelog) and sending
>> directly.
>>
>> Regards
>> Senduran
>>
>> On Wed, Jun 15, 2016 at 6:56 PM, Shakila Sivagnanarajah > > wrote:
>>
>>> Hi all,
>>>
>>> I am experiencing socket connection closed exception while trying
>>> 'upload part operation' [1] of Amazon s3 connector. In direct call, the
>>> response comes within 5 seconds. I increased the the timeout values as
>>> below.
>>>
>>> synapse.global_timeout_interval - 180 seconds in synapse.properties
>>> http.socket.timeout - 180 seconds in passthru-http.properties
>>> http.socket.timeout.receiver - 180 seconds in nhttp.properties
>>>
>>> After this tuning also, no improvement. It waits for nearly 21 seconds.
>>> But not receiving the response from API. [2] is the message I get.
>>>
>>> Finally I set the endpoint timeout [3] also. But the result is same.
>>>
>>> [1]
>>> http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html
>>>
>>>
>>> 
>>> [2]
>>> 
>>> RequestTimeout
>>> Your socket connection to the server was not read from or
>>> written to within the timeout period. Idle connections will be
>>> closed.
>>> 7223E45B22E88E80
>>>
>>> cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c
>>> 
>>>
>>> [3]
>>> 
>>> 
>>> >> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}">
>>> 
>>> 18
>>> fault
>>> 
>>> 
>>> 
>>> 
>>>
>>> [4] Template:
>>>
>>> http://ws.apache.org/ns/synapse;>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> expression="$func:objectName"/>
>>> 
>>> >> expression="$func:partNumber"/>
>>> 
>>> >> scope="axis2"/>
>>> >> scope="axis2"/>
>>> 
>>> 
>>> >>
>>> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}"/>
>>> 
>>> 
>>> 
>>> 
>>> >> action="remove"/>
>>> 
>>> >> action="remove"/>
>>> 
>>> 
>>>
>>>
>>> Thank you
>>> --
>>> Shakila Sivagnanarajah
>>> Software Engineer
>>> Mobile :+94 (0) 768 856837
>>> shak...@wso2.com
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>>
>>
>>
>>
>> --
>> *Senduran *
>> Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548
>>
>
>
>
> --
> Shakila Sivagnanarajah
> Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PET] Getting error when calling the endpoint template within call mediator blocking true

[Kathees Rajendram]

Hi Kalyani,

You can get the parameter value from init method ({$ctx:salesforce.timeout})
in the template. Instead of adding endpoints in different template, you can
add the endpoint in the template for blocking calls. The endpoint timeout
can be different between API methods and we need to adjust the timeout
value for some api methods. So we can include the endpoint configuration
inside the template rather than adding in common template.

http://ws.apache.org/ns/synapse;>







 



-1


-1
2000
1.0
3000


{$ctx:salesforce.timeout}
fault


  
 


Thanks,
Kathees

On Thu, Jun 16, 2016 at 1:58 PM, Kalyani Yogeswaranathan 
wrote:

> Hi Al,
>
> I am working on salesforce connector to add dynamic endpoint. For that
> I've wrote a separate template as [1] and calling this template within call
> mediator,
>
> It's working fine for blocking false when i call endpoint template, but
> it's not working for blocking true[2].
>
> [2]
>
> 
>
> template="org.wso2.carbon.connector.salesforce.salesforceEndPoint">
> 
> 
> 
>
> but if I add the whole endpoint[3], rather than calling endpoint template 
> it's working fine.
>
> [3]
> 
> 
> 
> 
> -1
> 
> 
> -1
> 2000
> 1.0
> 3000
> 
> 
> {$ctx:salesforce.timeout}
> fault
> 
> 
> 
> 
>
> Is there any other way to call endpoint template within call mediator with
> blocking true?
>
>
> [1]
>
> http://ws.apache.org/ns/synapse;>
> 
> description="Progress factor for timeout of the API request."/>
> description="Maximum duration for timeout of the API 
> request."/>
> 
> description="It is used to specify the action to perform once 
> an endpoint has timed out."/>
> 
> 
> 
> 
> -1
> 
> 
> -1
> 2000
> 1.0
> 3000
> 
> 
> {$ctx:salesforce.timeout}
> fault
> 
> 
> 
> 
>
>
> --
> Best Regards,
>
>
> *Kalyani Yogeswaranathan*
>
> *Associate software engineer*
> *WSO2 Inc.*
>
> *Mobile: 0776390284*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Blocking call mediator

[Kathees Rajendram]

Hi Godwin,

Call mediator blocking mode supportes indirect URL with key as you
mensioned above. Can you define the key expression in the endpoint.





@Isuru
Yes, call mediator with the combination of blocking=true and key-expression
in endpoint is not supported directly. We can use above approach.

Thanks,
Kathees

On Wed, Jun 8, 2016 at 6:27 AM, Isuru Udana  wrote:

> Hi Godwin,
>
> I think key-expressions are not supported in blocking mode.
> @Kathees,
> Can you please confirm ?
>
> Thanks.
>
> On Wed, Jun 8, 2016 at 3:08 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> When I use call mediator in my sequence as below it gives error [1].
>>
>> 
>>
>> 
>>
>> 
>> If I change the code as any of below, its works fine.
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> Do we have a problem in Call mediator with the combination of *blocking=true
>> *and *key-expression *in endpoint ?
>>
>>
>> [1] org.apache.synapse.SynapseException: Error while performing the call
>> operation
>> at
>> org.apache.synapse.mediators.builtin.CallMediator.handleFault(CallMediator.java:306)
>> at
>> org.apache.synapse.mediators.builtin.CallMediator.handleBlockingCall(CallMediator.java:119)
>> at
>> org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:85)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>> at
>> org.apache.synapse.message.processor.impl.sampler.SamplingService$1.run(SamplingService.java:211)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.synapse.message.senders.blocking.BlockingMsgSender.send(BlockingMsgSender.java:114)
>> at
>> org.apache.synapse.mediators.builtin.CallMediator.handleBlockingCall(CallMediator.java:113)
>>
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>>
>
>
>
> --
> *Isuru Udana*
> Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Pass dynamic values to class mediator

[Kathees Rajendram]

Hi Godwin/Isuru,

This may not be a good approach. You can define a static property. In
static property you can dynamically assign dynamic properties and values as
key value pairs with the patterns (dynamicProperty1: value1,
dynamicProperty2: value2, etc.).

dynamicProperty1: value1, dynamicProperty2:
value2

In the class mediator, you can read the static property and you need to
write a login to get each values of the dynamic properties.
Thanks,
Kathees

On Thu, Jun 2, 2016 at 10:46 AM, Isuru Udana  wrote:

> Hi Rajjaz,
>
> Godwin is asking about class mediators not connectors.
>
>
>
> On Thu, Jun 2, 2016 at 10:38 AM, Rajjaz Mohammed  wrote:
>
>> Hi Godwin,
>> You can receive dynamic values in class level without set in the property
>> configuration.
>>
>> for example:
>> 
>> raj
>> > >com.sun.enterprise.naming.SerialInitContextFactory> raj.java.naming.factory.initial>
>> localhost> raj.org.omg.CORBA.ORBInitialHost>
>> 3700> raj.org.omg.CORBA.ORBInitialPort>
>> 
>>
>> these values are dynamic values so we can receive these values in code
>> level without set property[1].
>>
>> [1]
>> https://github.com/wso2-extensions/esb-connector-ejb2.0/blob/master/src/main/java/org/wso2/carbon/custom/connector/EJBUtil.java#L131
>>
>>
>>
>> On Thu, Jun 2, 2016 at 9:09 AM, Godwin Shrimal  wrote:
>>
>>> Hi Isuru,
>>>
>>> Thanks for quick response, I'll proceed with by setting property.
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>>
>>>
>>> On Wed, Jun 1, 2016 at 10:32 PM, Isuru Udana  wrote:
>>>
 Hi Godwin,

 It is not possible to pass dynamic values using the property
 configuration element. It only support static values.

 The only option is to set some property using the property mediator and
 within the class mediator code read that property using
 synCtx.getProperty('prop_name_here')

 Thanks.

 On Thu, Jun 2, 2016 at 8:54 AM, Godwin Shrimal  wrote:

> Hi All,
>
> How can we pass dynamic values to class mediator ?, if we try to do as
> below it give a error *A Class mediator property must specify name
> and value attributes, or a name and a child XML fragment*
>
> 
> 
> 
>
> How can we achieve this ?
>
> Thanks
> Godwin
>
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
>



 --
 *Isuru Udana*
 Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> Platform Extension Team
>> WSO2 Inc. 
>> lean | enterprise | middleware
>> Mobile | +94752833834|+94777226874
>> Email   | raj...@wso2.com
>> LinkedIn  | Blogger
>>  | WSO2 Profile
>> 
>>
>
>
>
> --
> *Isuru Udana*
> Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Twitter Connector and Inbound

[Kathees Rajendram]

Hi Anoukh,

Before sending the stream data to CEP, you can filter the stream data in
ESB. In twitter inbound endpoint, use the track operation. From the output,
you can filter the stream for the particular ID using Xpath expression.

Thanks,
Kathees

On Wed, Jun 1, 2016 at 12:37 PM, Anoukh Jayawardena <ano...@wso2.com> wrote:

> Hi Kathees,
>
> Yes, since twitter API doesn't have AND operation what we can do is a
> "filter" process. As you said, we are using the track operation only and
> from this stream we read the user ID and filter the ones we need. We do
> this manual filtering in CEP currently. If we pass the follower ID to
> another inbound endpoint, wouldn't we get all the tweets that this person
> sent?
>
> Regards,
> Anoukh
>
> On Tue, May 31, 2016 at 6:45 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi Anoukh,
>>
>> The twitter streaming API [1] provides the filter operation with the
>> track follow, and locations fields are combined with an OR operator.
>> Twitter streaming API doesn’t have AND operation.
>>
>> Can you try with two twitter inbound endpoints and twitter connector, In
>> a inbound endpoint, use the track operation to get the public stream with
>> the keyword. In ESB, the streaming output data are injected to a sequence.
>> From the output you can read user or follower ID. If there are
>> no follower ID, use the twitter connector method to retrieve the follower
>> ID. In second twitter Inbound endpoint, pass the follower ID with comma
>> separator to retrieve follower's streaming data.
>>
>> [1] - https://dev.twitter.com/streaming/reference/post/statuses/filter
>>
>> [2] -
>> https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Twitter+Inbound+Operations
>>
>> Thanks,
>> Kathees
>>
>> On Tue, May 31, 2016 at 5:51 PM, Anoukh Jayawardena <ano...@wso2.com>
>> wrote:
>>
>>> Hi
>>>
>>> There is a use case in the US Election analytic app (refer
>>> https://wso2.com/election2016/) to use twitter.track and twitter.follow
>>> parameters together.
>>> This is to pull the tweets of certain accounts (hence the
>>> twitter.follow) that include certain words (hence the twitter.track). So
>>> requirement is twitter.follow AND twitter.track.
>>> These two operations are combined using an "OR" operation from twitter
>>> API itself (refer
>>> https://dev.twitter.com/streaming/reference/post/statuses/filter).
>>> Is there a way we can support "AND" operation within ESB?
>>>
>>> Currently we only do the twitter.follow operation from ESB and filter
>>> the words manually from the stream.
>>>
>>>
>>> Regards
>>> Anoukh Jayawardena
>>> --
>>> Anoukh Jayawardena
>>> *Software Engineer - Intern*
>>> Mobile : +94779928932
>>> ano...@wso2.com
>>>
>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Anoukh Jayawardena
> *Software Engineer - Intern*
> Mobile : +94779928932
> ano...@wso2.com
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Twitter Connector and Inbound

[Kathees Rajendram]

Hi Anoukh,

The twitter streaming API [1] provides the filter operation with the track
follow, and locations fields are combined with an OR operator. Twitter
streaming API doesn’t have AND operation.

Can you try with two twitter inbound endpoints and twitter connector, In a
inbound endpoint, use the track operation to get the public stream with the
keyword. In ESB, the streaming output data are injected to a sequence. From
the output you can read user or follower ID. If there are no follower ID,
use the twitter connector method to retrieve the follower ID. In second
twitter Inbound endpoint, pass the follower ID with comma separator to
retrieve follower's streaming data.

[1] - https://dev.twitter.com/streaming/reference/post/statuses/filter

[2] -
https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Twitter+Inbound+Operations

Thanks,
Kathees

On Tue, May 31, 2016 at 5:51 PM, Anoukh Jayawardena  wrote:

> Hi
>
> There is a use case in the US Election analytic app (refer
> https://wso2.com/election2016/) to use twitter.track and twitter.follow
> parameters together.
> This is to pull the tweets of certain accounts (hence the twitter.follow)
> that include certain words (hence the twitter.track). So requirement is
> twitter.follow AND twitter.track.
> These two operations are combined using an "OR" operation from twitter API
> itself (refer
> https://dev.twitter.com/streaming/reference/post/statuses/filter).
> Is there a way we can support "AND" operation within ESB?
>
> Currently we only do the twitter.follow operation from ESB and filter the
> words manually from the stream.
>
>
> Regards
> Anoukh Jayawardena
> --
> Anoukh Jayawardena
> *Software Engineer - Intern*
> Mobile : +94779928932
> ano...@wso2.com
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: Removing is-connectors and esb-connectors from wso2

[Kathees Rajendram]

Hi Malaka,

Before removing two is-connectors and esb-connectors repos, we need to
check the open PRs [1] [2] and incorporate the changes to new extension
repo if those changes are required.

[1] - https://github.com/wso2/is-connectors/pulls
[2] - https://github.com/wso2/esb-connectors/pulls

Thanks,

On Sat, May 7, 2016 at 3:10 PM, Rajjaz Mohammed  wrote:

> +1,
>
> Having codes in two places may mislead outside contributors.
>
> On Sat, May 7, 2016 at 2:52 PM, Malaka Silva  wrote:
>
>> ​
>> Hi All,
>>
>> We may not need [1] and [2] anymore since all the extensions are already
>> moved to individual repos in [3]. If there are objections let me know?
>>
>> [1] https://github.com/wso2/is-connectors
>> [2] https://github.com/wso2/esb-connectors
>> [3] https://github.com/wso2-extensions
>>
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> Platform Extension Team
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834|+94777226874
> Email   | raj...@wso2.com
> LinkedIn  | Blogger
>  | WSO2 Profile
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB]Blocking option of Call mediator

[Kathees Rajendram]

Hi Dilshani,

Call mediator blocking functionality [1] is similar to the Callout mediator.

When invoked in a asynchronous manner, the Call mediator performs a
blocking external service invocation during mediation. So when you send the
call to backend with blocking functionality (blocking=true), It will wait
for the response. When you send the call with non blocking, It will work in
a synchronous manner without waiting for the response.

[1] - https://docs.wso2.com/display/ESB490/Call+Mediator


Thanks,
Kathees

On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
wrote:

> Hi ESB team,
>
> In call mediator, there is a separate option called "Blocking". AFAIK call
> mediator having default functionality of blocking mediation.
>
> What will be the different behavior can have through Enabling Blocking
> rather than in-built blocking feature ? Even though Blocking disabled, it
> may not act as send mediator.
>
> Can someone help to figure out this ?
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set Password Policy per tenant

[Kathees Rajendram]

Hi,

I have written for this [1] during the authentication flow, if the password
is expired, you will be prompted to reset the password. You can find it in
[1].

[1] -
https://github.com/wso2-extensions/identity-outbound-auth-passwordPolicy/pull/1

Thanks,
Kathees

On Tue, Mar 15, 2016 at 4:17 PM, Gayan Gunawardana  wrote:

>
>
> On Tue, Mar 15, 2016 at 1:47 PM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Gayan,
>>
>> I have written a sample to get the same requirement done. You can find it
>> in [1].
>>
>> In the code, I have added some sample policy patterns for different
>> tenants. You can add the per tenant policies in identity-mgt.properties as
>> well and then retrieve the policy patterns in the init method of this
>> sample.
>>
>> Note that if you put the regex directly in the code, then it's the same
>> java regex you have to put. If you define the patterns in
>> identity-mgt.properties file, then you may have to put some escaping like
>> \\.
>>
>> [1]
>> https://github.com/thariyarox/WSO2PasswordPatternPolicySamples/tree/master/TenantSpecificPasswordPatterns/password-policy-extension/src/main/java/com/wso2/password/policy
>>
>
> Thanks Tharindu. I guess for this use case no use of
> CustomPasswordPatternDataHolder and realm service.
>
>>
>> Regards,
>> TharinduE
>>
>> On Tue, Mar 15, 2016 at 9:48 AM, Gayan Gunawardana 
>> wrote:
>>
>>>
>>>
>>> On Tue, Mar 15, 2016 at 9:42 AM, Johann Nallathamby 
>>> wrote:
>>>
 Yes. We don't have tenanted password policy validator by default in IS.
 We may have to write one.

>>> Thanks Johann. Will look into custom password validator.
>>>

 On Tue, Mar 15, 2016 at 9:25 AM, Gayan Gunawardana 
 wrote:

> Hi All,
>
> Is there a way to configure password policy per tenant ?
>
>  Do we need to write custom password validator according to [1] ?
>
>
> [1]
> https://docs.wso2.com/display/IS510/Writing+a+Custom+Password+Validator
>
> Thanks,
> Gayan
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



 --
 Thanks & Regards,

 *Johann Dilantha Nallathamby*
 Technical Lead & Product Lead of WSO2 Identity Server
 Governance Technologies Team
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - *+9476950*
 Blog - *http://nallaa.wordpress.com *

>>>
>>>
>>>
>>> --
>>> Gayan Gunawardana
>>> Software Engineer; WSO2 Inc.; http://wso2.com/
>>> Email: ga...@wso2.com
>>> Mobile: +94 (71) 8020933
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Tharindu Edirisinghe
>> Software Engineer | WSO2 Inc
>> Platform Security Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775181586
>>
>
>
>
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Connector] Github connector - get List of commits on a repo.

[Kathees Rajendram]

Merged. will release and add to the store.

On Fri, Mar 4, 2016 at 11:27 AM, Lakmini Chathurika <lakm...@wso2.com>
wrote:

> Hi,
>
> I added the two new  methods to do the followings  in GitHub Connector.
>
> 1.List Organization Repositories.[1].
> 2.List Commits on a repository.[2].
>
> I create JIRA [3]&[4] and add the PR[5].
> Could you please review and merge this.
>
> [1].https://developer.github.com/v3/repos/#list-organization-repositories
> [2].
> https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository
> [3].https://wso2.org/jira/browse/ESBCONNECT-85
> [4].https://wso2.org/jira/browse/ESBCONNECT-84
> [5].https://github.com/wso2-extensions/esb-connector-github/pull/3
>
> Thanks & Reagards.
>
> Lakmini.
>
> On Thu, Mar 3, 2016 at 4:53 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Lakmini,
>>
>> Great if you could contribute. Else put a jira and we will include this
>> in next version of github
>>
>> On Thu, Mar 3, 2016 at 4:12 PM, Lakmini Chathurika <lakm...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I need to get the list of repositories that are accessible to the
>>> authenticated user.
>>> Current connector [1] does not support for this but GitHub API [2] is
>>> supporting it . So need to implement the method  inside the connector.
>>> [1].
>>> https://storepreview.wso2.com/store/assets/esbconnector/cf9c44c0-b637-4587-afae-ea55fe64b632
>>> [2].https://developer.github.com/v3/repos/#list-your-repositories
>>>
>>> Thanks & Regards.
>>> Lakmini
>>>
>>> On Thu, Mar 3, 2016 at 12:39 PM, Kathees Rajendram <kath...@wso2.com>
>>> wrote:
>>>
>>>> Hi Chanuka,
>>>>
>>>> Now we don't have the method[1][2] in github1.0.0 connector.
>>>>
>>>> We will include this in next version of github or you can contribute
>>>> [3] with creating the method.
>>>>
>>>> [1] -
>>>> https://developer.github.com/v3/repos/statistics/#get-the-last-year-of-commit-activity-data
>>>> [2] -
>>>> https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository
>>>> [3] - https://github.com/wso2-extensions/esb-connector-github
>>>>
>>>> Thanks,
>>>> Kathees
>>>>
>>>> On Thu, Mar 3, 2016 at 12:35 PM, Chanuka Dissanayake <chan...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Current connector [1] doesn't support on the $subject.  Github API [2]
>>>>> is supporting it, and need to implement the method inside the connector.
>>>>> As a workaround we can do traverse thorough the pull request (refer
>>>>> [3]) per each repo and retrieve the list.
>>>>>
>>>>>
>>>>> [1]
>>>>> https://storepreview.wso2.com/store/assets/esbconnector/cf9c44c0-b637-4587-afae-ea55fe64b632
>>>>> [2]
>>>>> https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository
>>>>> [3]
>>>>> https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Pull+Requests+in+Github#WorkingwithPullRequestsinGithub-listPullRequestCommits
>>>>>
>>>>> Thanks & Regards,
>>>>> Chanuka.
>>>>> --
>>>>> Chanuka Dissanayake
>>>>> *Software Engineer | **WSO2 Inc.*; http://wso2.com
>>>>>
>>>>> Mobile: +94 71 33 63 596
>>>>> Email: chan...@wso2.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Kathees
>>>> Software Engineer,
>>>> email: kath...@wso2.com
>>>> mobile: +94772596173
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Connector] Github connector - get List of commits on a repo.

[Kathees Rajendram]

Hi Chanuka,

Now we don't have the method[1][2] in github1.0.0 connector.

We will include this in next version of github or you can contribute [3]
with creating the method.

[1] -
https://developer.github.com/v3/repos/statistics/#get-the-last-year-of-commit-activity-data
[2] -
https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository
[3] - https://github.com/wso2-extensions/esb-connector-github

Thanks,
Kathees

On Thu, Mar 3, 2016 at 12:35 PM, Chanuka Dissanayake 
wrote:

> Hi,
>
> Current connector [1] doesn't support on the $subject.  Github API [2] is
> supporting it, and need to implement the method inside the connector.
> As a workaround we can do traverse thorough the pull request (refer [3])
> per each repo and retrieve the list.
>
>
> [1]
> https://storepreview.wso2.com/store/assets/esbconnector/cf9c44c0-b637-4587-afae-ea55fe64b632
> [2]
> https://developer.github.com/v3/repos/commits/#list-commits-on-a-repository
> [3]
> https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Pull+Requests+in+Github#WorkingwithPullRequestsinGithub-listPullRequestCommits
>
> Thanks & Regards,
> Chanuka.
> --
> Chanuka Dissanayake
> *Software Engineer | **WSO2 Inc.*; http://wso2.com
>
> Mobile: +94 71 33 63 596
> Email: chan...@wso2.com
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Announcement] WSO2 Identity Server Connectors Store Released

[Kathees Rajendram]

Hi,

The WSO2 Platform Extensions team is pleased to announce the release of the
WSO2 Store for WSO2 Identity Server Authenticators and Provisioning
Connectors.

Authenticators provide you with a way to authenticate users using a
specific external authentication system through WSO2 Identity Server.

To browse through the WSO2 Identity Server authenticators and to download
the authenticator that you require, go to https://store.wso2.com/store.

For more information on authenticators and how to configure an
authenticator with the WSO2 Identity Server, see
https://docs.wso2.com/display/ISCONNECTORS/Identity+Server+Authenticators+and+Connectors
.

The following authenticators are available in WSO2 Store:

*Authenticators*

Tiqr
MePIN
SMSOTP
Inwebo
Yammer
Foursquare

*How You Can Contribute*

You can create an authenticator and publish it in the WSO2 Store. For more
information, see.
https://docs.wso2.com/display/ISCONNECTORS/Creating+a+Third+Party+Authenticator+or+Connector+and+Publishing+in+WSO2+Store
.

*Support*

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.

-- The WSO2 Platform Extensions Team --
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue while using the special characters in url-template with legacy encoding.

[Kathees Rajendram]

Hi Malaka/Kevin,

The legacy and other encoding didn't support for special characters in HTTP
Endpoint. Temporarily I was able to resolve by replacing the special
character with encoded values.

@@ -246,6 +246,22 @@ public class HTTPEndpoint extends AbstractEndpoint {
 try {
 URI uri = new URI(template.expand());
 evaluatedUri = uri.toString();
+StringBuilder buf = null;
+if (evaluatedUri != null) {
+buf = new StringBuilder(evaluatedUri.length());
+char focus;
+for (int i = 0; i < evaluatedUri.length(); i++) {
+focus = evaluatedUri.charAt(i);
+if (focus == '#') {
+buf.append("%23");
+} else if (focus == '@') {
+buf.append("%40");
+} else {
+buf.append(focus);
+}
+}
+evaluatedUri = buf.toString();
+}

Thanks,
Kathees

On Sat, Dec 19, 2015 at 9:00 PM, Kevin Ratnasekera <ke...@wso2.com> wrote:

> Hi Kathees,
> Is there a specific reason to use the legacy-encoding prefix here in your
> case? Have you tried without the legacy-encoding prefix?
> Can you try the following with legacy prefix,
>
> 
> 
> 
> uri-template="legacy-encoding:{uri.var.apiUrl}/1.1/statuses/update.json?
> status={uri.var.status}"/>
> 
> 
>
> Regards
> Kevin
>
> On Fri, Dec 18, 2015 at 8:56 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Kathees,
>>
>> Can you try debugging [1] and try to figure out the issues?
>>
>> May be the issues it in  'String decodedString =
>> URLDecoder.decode(template.expand(), "UTF-8");'
>>
>> [1]
>> https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/endpoints/HTTPEndpoint.java
>>
>> On Fri, Dec 18, 2015 at 4:59 PM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I created uri.var.status property and used the property in url-template with
>>> legacy encoding. Remaining part of URL is removed with the special
>>> character.
>>>
>>> 
>>> 
>>> >>
>>> uri-template="legacy-encoding:{uri.var.apiUrl}/1.1/statuses/update.json?{uri.var.status}"/>
>>> 
>>> 
>>>
>>> *Request* - sample #test
>>>
>>> *Output*
>>>
>>> [2015-12-18 16:45:47,269] DEBUG - wire << "POST
>>> /1.1/statuses/update.json?status=sample%20 HTTP/1.1[\r][\n]"
>>> [2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
>>> en-US,en;q=0.8[\r][\n]"
>>>
>>> *Expected output*
>>>
>>> [2015-12-18 16:45:47,269] DEBUG - wire << "POST
>>> /1.1/statuses/update.json?status=sample%20%23test HTTP/1.1[\r][\n]"
>>> [2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
>>> en-US,en;q=0.8[\r][\n]"
>>>
>>> What could be the reason?
>>>
>>> Thanks,
>>> Kathees
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue while using the special characters in url-template with legacy encoding.

[Kathees Rajendram]

Hi,

I created uri.var.status property and used the property in url-template with
legacy encoding. Remaining part of URL is removed with the special
character.







*Request* - sample #test

*Output*

[2015-12-18 16:45:47,269] DEBUG - wire << "POST
/1.1/statuses/update.json?status=sample%20 HTTP/1.1[\r][\n]"
[2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
en-US,en;q=0.8[\r][\n]"

*Expected output*

[2015-12-18 16:45:47,269] DEBUG - wire << "POST
/1.1/statuses/update.json?status=sample%20%23test HTTP/1.1[\r][\n]"
[2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
en-US,en;q=0.8[\r][\n]"

What could be the reason?

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Kathees Rajendram]

+1 to deprecate Callout mediator since we have the Callout mediator
functionalities in Call mediator.

On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
wrote:

> I've found DBReport / DBLookup to be quite useful for simple DB operations
> as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
> ability to only being able to return a single row of data, DB Report
> mediator is still quite useful in writing to a database, especially when we
> use a DB as part of the mediation sequences.
>
> I also feel it is worth continuing with POJOCommand, as it is the most
> simplest way of executing some custom code as part of a sequence. Although
> it is possible to do the same with a Class mediator, one doesn't have to
> worry about adding the proper jars, working with MessageContext etc. with
> the POJOCommand. I think we should retain it for the sake of simplicity of
> use.
>
> I'm +1 to deprecate the rest of the mediators.
>
> Thanks,
>
> Vidura
>
>
>
> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Vidura Gamini Abhaya, Ph.D.
> Director of Engineering
> M:+94 77 034 7754
> E: vid...@wso2.com
>
> WSO2 Inc. (http://wso2.com)
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can't create new artifact for the inbound in Developer Studio

[Kathees Rajendram]

Hi,

I tried to create the Kafka inbound configuration from the developer
studio. I got the issue "the interval can't be empty"  What is the cause of
this while creating the inbound configuration in developer studio?

Thanks,
kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to pass pair of values to Message-contest from proxy operation

[Kathees Rajendram]

Hi Malaka,

+1 For your approach.

Thanks,
Kathees

On Tue, Nov 3, 2015 at 4:16 PM, Malaka Silva <mal...@wso2.com> wrote:

> Kathees but with this approach the config will be lengthy and will become
> hard to read.
>
> IMO we should have something like [1] or [2]. We can easily iterate
> properties using [3] WDYT?
>
> [1]
> 
> jboss
> org.jnp.interfaces.
> NamingContextFactory
> org.
> jboss.naming:org.jnp.interfaces naming.factory.url.pkgs>
> jnp://localhost:1099 ejbJNDIKey.jboss.java.naming.provider.url>
> 
> [2]
> 
> org.jnp.interfaces.
> NamingContextFactory
> org.jboss.naming:org.jnp.
> interfaces
> jnp://localhost:1099 jboss.java.naming.provider.url>
> 
>
> [3]
> public static Object lookupTemplateParamater(MessageContext ctxt, int
> index) {
> Stack funcStack = (Stack)
> ctxt.getProperty(SynapseConstants.SYNAPSE__FUNCTION__STACK);
> TemplateContext currentFuncHolder = funcStack.peek();
> Collection paramList = currentFuncHolder.getParameters();
> Iterator it = paramList.iterator();
> int i = 0;
> while (it.hasNext()) {
> String param = (String) it.next();
> if (i == index) {
> return param;
>     }
> i++;
> }
> return null;
> }
>
> On Mon, Nov 2, 2015 at 10:50 PM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In the template,We can use a parameter[1] for the JNDI dynamic properties
>> and input the values with the pattern[2]. The each ejb JNDI properties can
>> be gotten from the parameter and set to the properties[3] using a class
>> mediator.
>>
>> [1]
>> 
>> {$ctx:ejbJNDIProperties}
>> 
>>
>> [2]
>> A:B,C:D,E:F
>>
>> [3]
>> Properties props = new Properties();
>> props.put("A" ,"B");
>> props.setProperty("C","D");
>> props.setProperty("E", "F");
>>
>> Thanks,
>> Kathees
>>
>> On Mon, Nov 2, 2015 at 7:23 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Challenge here is parameters depends on the container rather than the
>>> inbound connector.
>>>
>>> IMO we should follow the same concept followed in ejb mediator. (Except
>>> we need to make it dynamic)
>>>
>>> eg:
>>>
>>> Will have one JNDIID and user can add multiple entries against it.
>>>
>>> inbound.ejb.JNDIID=jboss
>>>
>>> inbound.ejb.JNDIID.jboss.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
>>>
>>> inbound.ejb.JNDIID.jboss.java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
>>> inbound.ejb.JNDIID.jboss.java.naming.provider.url=jnp://localhost:1099
>>>
>>> [1] https://docs.wso2.com/display/ESB490/EJB+Mediator
>>>
>>> On Mon, Nov 2, 2015 at 5:34 PM, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>>
>>>> Hi,
>>>> I'm implementing Connector for EJB 2.x. so in order to create JNDI
>>>> properties i need pair of parameters [1]. and the number of parameters also
>>>> depend on EJB server and Version. How can i write the operation fro
>>>> that?(normally our Init methods will be like [2])
>>>>
>>>>
>>>> [1]
>>>> Properties props = new Properties();
>>>> props.put("A" ,"B");
>>>> props.setProperty("C","D");
>>>> props.setProperty("E", "F");
>>>>
>>>>
>>>> [2]
>>>> 
>>>> {$ctx:a}
>>>> {$ctx:b}
>>>> {$ctx:c}
>>>> {$ctx:d}
>>>> 
>>>>
>>>>
>>>> --
>>>> Thank you
>>>> Best Regards
>>>>
>>>> *Rajjaz HM*
>>>> Associate Software Engineer
>>>> WSO2 Inc. <http://wso2.com/>
>>>> lean | enterprise | middleware
>>>> Mobile | +94752833834
>>>> Email   | raj...@wso2.com
>>>> LinkedIn | Blogger | WSO2 Profile
>>>> <http://wso2.com/about/team/mohammer_rajjaz/>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedI

Re: [Dev] How to pass pair of values to Message-contest from proxy operation

[Kathees Rajendram]

Hi,

In the template,We can use a parameter[1] for the JNDI dynamic properties
and input the values with the pattern[2]. The each ejb JNDI properties can
be gotten from the parameter and set to the properties[3] using a class
mediator.

[1]

{$ctx:ejbJNDIProperties}


[2]
A:B,C:D,E:F

[3]
Properties props = new Properties();
props.put("A" ,"B");
props.setProperty("C","D");
props.setProperty("E", "F");

Thanks,
Kathees

On Mon, Nov 2, 2015 at 7:23 PM, Malaka Silva  wrote:

> Challenge here is parameters depends on the container rather than the
> inbound connector.
>
> IMO we should follow the same concept followed in ejb mediator. (Except we
> need to make it dynamic)
>
> eg:
>
> Will have one JNDIID and user can add multiple entries against it.
>
> inbound.ejb.JNDIID=jboss
>
> inbound.ejb.JNDIID.jboss.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
>
> inbound.ejb.JNDIID.jboss.java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
> inbound.ejb.JNDIID.jboss.java.naming.provider.url=jnp://localhost:1099
>
> [1] https://docs.wso2.com/display/ESB490/EJB+Mediator
>
> On Mon, Nov 2, 2015 at 5:34 PM, Rajjaz Mohammed  wrote:
>
>> Hi,
>> I'm implementing Connector for EJB 2.x. so in order to create JNDI
>> properties i need pair of parameters [1]. and the number of parameters also
>> depend on EJB server and Version. How can i write the operation fro
>> that?(normally our Init methods will be like [2])
>>
>>
>> [1]
>> Properties props = new Properties();
>> props.put("A" ,"B");
>> props.setProperty("C","D");
>> props.setProperty("E", "F");
>>
>>
>> [2]
>> 
>> {$ctx:a}
>> {$ctx:b}
>> {$ctx:c}
>> {$ctx:d}
>> 
>>
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> WSO2 Inc. 
>> lean | enterprise | middleware
>> Mobile | +94752833834
>> Email   | raj...@wso2.com
>> LinkedIn | Blogger | WSO2 Profile
>> 
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Inbound endpoint default values

[Kathees Rajendram]

Hi Susinda,

Please change the parameters(interval and zookeeper.connect) in Kafka
Inbound EP.




*1000localhost:2181*
Other bolded parameters values can be any valid String.

The groupd Id parameter value can be any valid String this is used to
identify the consumer group. If the inbound EPs  have same group, this
works like traditional Queue and If the inbound EPs have different group
ids,this works like Topic.
sampleGroupID

You can use any valid String for topics parameter,And also you can use
comma separated values to consume the messages from more than one topics.
sampleTopic

Thanks,
Kathees

On Fri, Oct 9, 2015 at 1:10 PM, Maheeka Jayasuriya  wrote:

> Hi Susinda,
>
> For Rabbitmq, please change the username and password as below.
>
> *http://rabbitmq.server.user.name>">guest*
>
>
> *guest*
> Other parameters are okay.
>
> Thanks,
> Maheeka
>
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Fri, Oct 9, 2015 at 2:16 AM, Chanaka Fernando 
> wrote:
>
>> Hi Susinda,
>>
>> You can use something like "org.wso2.sample.inbound.customClass" as we
>> have used in the class mediators here [1].
>>
>> [1]
>> https://docs.wso2.com/display/DVS371/Creating+ESB+Artifacts#CreatingESBArtifacts-Creatingamediator
>>
>> On Fri, Oct 9, 2015 at 11:30 AM, Susinda Perera  wrote:
>>
>>> @ chanaka : Like in scheduled tasks do you have a already available
>>> custom class for this, if not what would be the class name which would
>>> likely to have.
>>>
>>>
>>> On Fri, Oct 9, 2015 at 11:26 AM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Kathees/Maheeka,

 Can you comment on kafka and rabbitmq related params?

 @Susinda: For the custom inbound parameter, we can use the same
 approach which we are using for custom class mediators and custom scheduled
 tasks.

 On Fri, Oct 9, 2015 at 11:23 AM, Susinda Perera 
 wrote:

> [+ Dev group]
>
> On Fri, Oct 9, 2015 at 11:21 AM, Susinda Perera 
> wrote:
>
>> ESB team,
>>
>> Could you please suggest the default values for the (bolded
>> parameters) following inbound endpoints. I came up with following values,
>> is this values OK?
>>
>> >   suspend="false" xmlns="http://ws.apache.org/ns/synapse;>
>>   
>> polling
>>   
>> 
>>
>> http://ws.apache.org/ns/synapse;>
>>   
>> *100*
>> true
>> true
>>* > name="zookeeper.connect">zookeeperConnect*
>> *http://group.id>">sampleGroupID*
>> application/xml
>> highlevel
>> *sampleTopic*
>> 0
>> false
>> smallest
>> false
>> > name="partition.assignment.strategy">roundrobin
>> zookeeper
>> false
>>   
>> 
>>
>>
>> > xmlns="http://ws.apache.org/ns/synapse;>
>>   
>> true
>> true
>> *> name="rabbitmq.connection.factory">connection_factory*
>> *http://rabbitmq.server.host.name>">loclahost*
>> *5672*
>> *http://rabbitmq.server.user.name>">admin*
>> *admin*
>> *http://rabbitmq.queue.name>">queue_name*
>> *http://rabbitmq.exchange.name>">excahnge_name*
>>   
>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


 --
 --
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya





>>>
>>>
>>> --
>>> *Susinda Perera*
>>> Software Engineer
>>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>>> Mobile:(+94)716049075
>>> Blog: susinda.blogspot.com
>>> WSO2 Inc. http://wso2.com/
>>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>>
>>>
>>
>>
>> --
>> --
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list

[Dev] [Announcement] WSO2 Enterprise Service Bus Connector Store Released !!

[Kathees Rajendram]

WSO2 Platform Extensions team is pleased to announce the release of WSO2
Connector Store for WSO2 Enterprise Service Bus.


Connectors allow interacting with a third-party product's functionality and
data from WSO2 Enterprise Service Bus message flow, enabling you to connect
to and interact with third-party APIs and standard integration protocols.

WSO2 Enterprise Service Bus can be extended with the many extension points
to plug into. Connectors are build on top of this extensible framework.

To browse through WSO2 Connectors and to download a required connector, go
to https://store.wso2.com/store.

For more information on connectors and how to configure operations for each
connector, see.
https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors+Documentation
.

For information on how to work with connectors, see
https://docs.wso2.com/display/ESB490/Working+with+Connectors.


Following are the connectors available in WSO2 Connector Store:

*Billing and Accounting*

   - Billiving
   - Recurly
   - FreeAgent
   - Xero
   - Stripe
   - Chargebee
   - FreshBooks
   - Paypal
   - Billomat
   - Braintree
   - Ronin
   - QuickBooks

*Communication*

   - Mandrill
   - Nexmo
   - Gmail
   - CallRail
   - Amazon SES
   - Twilio
   - LiveChat

*Customer Relationship Management*

   - Base CRM
   - Zoho CRM
   - Nimble
   - Sirportly
   - Pipedrive
   - Salesforce
   - PipelineDeals
   - FreshDesk
   - Capsule CRM
   - Zendesk
   - Insightly
   - Clevertim CRM
   - SupportBee
   - Sugar CRM

*Developer Tools*

   - LDAP
   - BitBucket
   - Github
   - File
   - Amazon Simple Queue
   - Loggly
   - Amazon Simple DB
   - Amazon S3
   - Google Prediction

*E-commerce*



   - Shopify
   - Magento
   - eBay
   - Netsuite
   - TradeGecko

*Education*

   - Canvas

*Human Resource Management*

   - Zoho People
   - PeopleHR
   - Zoho Recruit
   - Deputy

*IOT*

   - Nest

*Issue Tracking and Project Management*

   - Podio
   - PagerDuty
   - Teamwork
   - Bugherd
   - Activecollab
   - Basecamp
   - Redmine
   - PivotalTracker
   - Prodpad
   - Cashboard
   - Agilezen
   - ProWorkflow
   - Jira

*Productivity Tools*

   - Delicious
   - EverNote
   - Confluence
   - GoToWebinar
   - Google Custom Search
   - SimpleNote
   - Tsheets
   - GoToTraining
   - Google Calendar
   - Formstack
   - Google Spreadsheet
   - Jotform
   - Wunderlist
   - Apple Push Notification
   - Google Tasks

*Sales and Marketing*

   - Eloqua Standard
   - Eloqua
   - Marketo
   - ExactTarget
   - ConstantContact
   - ActiveCampaign
   - SurveyGizmo
   - Campaign Monitor
   - VerticalResponse
   - MailChimp

*Social Media*

   - Wordpress
   - Instagram
   - GooglePlus
   - Foursquare
   - Spotify
   - Yelp
   - Yammer
   - Twitter
   - LinkedIn
   - Flickr

*Storage and Content Management*

   - Slideshare
   - Dropbox
   - Box
   - Google Blogger
   - Disqus

*Other*

   - OpenWeatherMap
   - Planyo
   - Concur
   - Eventbrite
   - Survey Monkey
   - Shippo
   - Clio

*How You Can Contribute*

You can create a connector and publish it in WSO2 store. For more
information, see.
https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Connector+Store
.

*Support*

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.


-- The WSO2 Platform Extensions Team --

---
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing 'blocking' attribute to the Call mediator of DevS ESB Graphical Tool

[Kathees Rajendram]

Hi Rajeevan,

The blocking attribute should be in the call mediator.
In the blocking calls, the attribute' value should be true.


In the non blocking calls,The blocking attribute is not mandatory.


Thanks,
Kathees

On Thu, Sep 10, 2015 at 4:07 PM, Rajeevan Vimalanathan 
wrote:

> Hi,
>
> We found that ESB has introduced a new attribute 'blocking=true/false'
> (Enable Blocking Calls) to the Call mediator from ESB 4.9.0 when testing.
> So we will add the same to Call mediator at ESB Graphical tool [1] of
> Developer Studio.
>
> http://ws.apache.org/ns/synapse"/>
>
> [1] https://wso2.org/jira/browse/TOOLS-3134
>
> Thanks,
> Rajeevan
>
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* 
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Kathees Rajendram]

Hi Malaka.

I will have a look.

Thanks,
Kathees

On Fri, Sep 4, 2015 at 9:36 AM, Malaka Silva  wrote:

> Hi Kathees,
>
> Seems like issue when configuring/starting server.
>
> Can you help on this matter pls?
>
> On Thu, Sep 3, 2015 at 9:48 PM, Nayomi Dayarathne  wrote:
>
>> Hi all,
>>
>> This issue is not related to the jira[1]  i have reported.
>>
>> According to my understanding this is something related to kafka server.
>> Therefore i assumed this issue is not related to kafka inbound endpoint.
>>
>>
>> [1]https://wso2.org/jira/browse/ESBJAVA-4153
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>> On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando 
>> wrote:
>>
>>> Viraj is looking into this.
>>>
>>> On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne 
>>> wrote:
>>>
 Hi ESB team,

 I tested the kafka inbound endpoint in a esb cluster where there is one
 manager and two worker nodes.

 Below are the steps i did when testing the kafka inbound endpoint.

 1. Start the zookeeper
 2.Start the kafka server

 Zookeeper and kafka server started in my local machine.

 3.Create a kafka inbound endpoint in cluster

 it gets deployed in all three nodes.

 4.Then create a topic in kafka broker.


 then, in one of the worker nodes i get the following error,

  ERROR {kafka.producer.SyncProducer} -  Producer connection to
 localhost:9092 unsuccessful {kafka.producer.SyncProducer}
 java.net.ConnectException: Connection refused
 at sun.nio.ch.Net.connect0(Native Method)
 at sun.nio.ch.Net.connect(Net.java:435)
 at sun.nio.ch.Net.connect(Net.java:427)
 at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
 at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
 at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
 at
 kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
 at
 kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
 at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
 at
 kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
 at
 kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
 at
 kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
 at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)



 the above message is throwing continuously by the worker node.

 I assume this issue is related to some configurations of kafka server.

 *Any ideas of solving this issue ?*





 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 <+94+(0)+775246619>

 *nay...@wso2.com *

>>>
>>>
>>>
>>> --
>>> --
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>> Wordpress:http://chanakaudaya.wordpress.com
>>>
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Kathees Rajendram]

Hi Niyomi,

Can you change to the IP address instead of localhost in server.properties
file as you use the IP address in the Kafka inbound.

zookeeper.connect=localhost:2181

Thanks,
Kathees.

On Fri, Sep 4, 2015 at 10:31 AM, Kathees Rajendram <kath...@wso2.com> wrote:

> Hi Malaka.
>
> I will have a look.
>
> Thanks,
> Kathees
>
> On Fri, Sep 4, 2015 at 9:36 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Kathees,
>>
>> Seems like issue when configuring/starting server.
>>
>> Can you help on this matter pls?
>>
>> On Thu, Sep 3, 2015 at 9:48 PM, Nayomi Dayarathne <nay...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> This issue is not related to the jira[1]  i have reported.
>>>
>>> According to my understanding this is something related to kafka server.
>>> Therefore i assumed this issue is not related to kafka inbound endpoint.
>>>
>>>
>>> [1]https://wso2.org/jira/browse/ESBJAVA-4153
>>>
>>> Nayomi Dayarathne
>>>
>>> *Software Engineer-QA*
>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>
>>> *nay...@wso2.com <nay...@wso2.com>*
>>>
>>> On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando <chana...@wso2.com>
>>> wrote:
>>>
>>>> Viraj is looking into this.
>>>>
>>>> On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne <nay...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi ESB team,
>>>>>
>>>>> I tested the kafka inbound endpoint in a esb cluster where there is
>>>>> one manager and two worker nodes.
>>>>>
>>>>> Below are the steps i did when testing the kafka inbound endpoint.
>>>>>
>>>>> 1. Start the zookeeper
>>>>> 2.Start the kafka server
>>>>>
>>>>> Zookeeper and kafka server started in my local machine.
>>>>>
>>>>> 3.Create a kafka inbound endpoint in cluster
>>>>>
>>>>> it gets deployed in all three nodes.
>>>>>
>>>>> 4.Then create a topic in kafka broker.
>>>>>
>>>>>
>>>>> then, in one of the worker nodes i get the following error,
>>>>>
>>>>>  ERROR {kafka.producer.SyncProducer} -  Producer connection to
>>>>> localhost:9092 unsuccessful {kafka.producer.SyncProducer}
>>>>> java.net.ConnectException: Connection refused
>>>>> at sun.nio.ch.Net.connect0(Native Method)
>>>>> at sun.nio.ch.Net.connect(Net.java:435)
>>>>> at sun.nio.ch.Net.connect(Net.java:427)
>>>>> at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
>>>>> at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
>>>>> at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
>>>>> at
>>>>> kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
>>>>> at
>>>>> kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
>>>>> at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
>>>>> at
>>>>> kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
>>>>> at
>>>>> kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
>>>>> at
>>>>> kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
>>>>> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
>>>>>
>>>>>
>>>>>
>>>>> the above message is throwing continuously by the worker node.
>>>>>
>>>>> I assume this issue is related to some configurations of kafka server.
>>>>>
>>>>> *Any ideas of solving this issue ?*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Nayomi Dayarathne
>>>>>
>>>>> *Software Engineer-QA*
>>>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>>>
>>>>> *nay...@wso2.com <nay...@wso2.com>*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Chanaka Fernando
>>>> Senior Technical Lead
>>>> WSO2, Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> mobile: +94 773337238
>>>> Blog : http://soatutorials.blogspot.com
>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>>> Twitter:https://twitter.com/chanakaudaya
>>>> Wordpress:http://chanakaudaya.wordpress.com
>>>>
>>>>
>>>>
>>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

HI Mariangela,

I increased the count and paginationLimit values in
WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag.


var DEFAULT_PAGIN = {
'start': 0,
'count': 1000,
'sortOrder': 'DESC',
'sortBy': 'overview_createdtime',
'paginationLimit':1000
};

Thanks,
Kathees

On Wed, Sep 2, 2015 at 3:49 PM, Mariangela Hills <mariang...@wso2.com>
wrote:

> Hi Kathees,
>
> Can you please let me know the exact changes that you made in the list.jag
> file, so that I can document this in the ES wiki docs.
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Wed, Sep 2, 2015 at 10:25 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Good Job Kathees. :)
>>
>> This became complete blocker for the store release and thx for fixing it
>> quickly.
>>
>> On Wed, Sep 2, 2015 at 10:19 AM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Hi Manuranga/Sameera,
>>>
>>> I  have fixed the issue by changing the value in the following jaggery
>>> file.
>>>
>>> WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Wed, Sep 2, 2015 at 8:05 AM, Sameera Medagammaddegedara <
>>> samee...@wso2.com> wrote:
>>>
>>>> EDIT: My apologies, I did not notice that you were talking about the
>>>> Publisher application.
>>>>
>>>> On Tue, Sep 1, 2015 at 10:21 PM, Sameera Medagammaddegedara <
>>>> samee...@wso2.com> wrote:
>>>>
>>>>> Hi Kathees,
>>>>>
>>>>> If I remember correctly the above code snippet is not invoked from the
>>>>> Store application.The AssetManager is not utilized in the Store 
>>>>> application
>>>>> of the ES pack that  you are using.
>>>>>
>>>>> Thank You,
>>>>> Sameera
>>>>>
>>>>> On Fri, Aug 28, 2015 at 1:02 AM, Kathees Rajendram <kath...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Manuranga,
>>>>>>
>>>>>> The count and paginationLimit values are 1000 but 100 asserts only
>>>>>> are listed. I tried to increase the number. The changes are not picked 
>>>>>> up.
>>>>>>
>>>>>> ../modules/rxt/scripts/asset/asset.js
>>>>>>
>>>>>> function AssetManager(registry, type, rxtManager, renderer) {
>>>>>> this.registry = registry;
>>>>>> this.rxtManager = rxtManager;
>>>>>> this.rxtTemplate = rxtManager.getRxtDefinition(type);
>>>>>> this.type = type;
>>>>>>     this.r = renderer;
>>>>>> this.am = null;
>>>>>> this.defaultPaging = {
>>>>>> 'start': 0,
>>>>>> 'count': 1000,
>>>>>> 'sortOrder': 'desc',
>>>>>> 'sortBy': 'overview_createdtime',
>>>>>> 'paginationLimit': 1000
>>>>>> };
>>>>>> }
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Kathees
>>>>>>
>>>>>> On Thu, Aug 27, 2015 at 10:21 PM, Manuranga Perera <m...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> number 100 is hard-coded in modules dir please grep and fix. can you
>>>>>>> meet me tomorrow?
>>>>>>>
>>>>>>> On Thu, Aug 27, 2015 at 6:40 PM, Kathees Rajendram <kath...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Adding Manuranga,
>>>>>>>>
>>>>>>>> On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram <
>>>>>>>> kath...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> In ESB connector store, we are unable to publish the new
>>>>>>>>> connectors. The ESB connector store publisher is restricted to view 
>>>>>>>>>

Re: [Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

Hi Manuranga/Sameera,

I  have fixed the issue by changing the value in the following jaggery file.
WSO2ES_HOME/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/pages/list.jag

Thanks,
Kathees

On Wed, Sep 2, 2015 at 8:05 AM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> EDIT: My apologies, I did not notice that you were talking about the
> Publisher application.
>
> On Tue, Sep 1, 2015 at 10:21 PM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Hi Kathees,
>>
>> If I remember correctly the above code snippet is not invoked from the
>> Store application.The AssetManager is not utilized in the Store application
>> of the ES pack that  you are using.
>>
>> Thank You,
>> Sameera
>>
>> On Fri, Aug 28, 2015 at 1:02 AM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Hi Manuranga,
>>>
>>> The count and paginationLimit values are 1000 but 100 asserts only are
>>> listed. I tried to increase the number. The changes are not picked up.
>>>
>>> ../modules/rxt/scripts/asset/asset.js
>>>
>>> function AssetManager(registry, type, rxtManager, renderer) {
>>> this.registry = registry;
>>> this.rxtManager = rxtManager;
>>> this.rxtTemplate = rxtManager.getRxtDefinition(type);
>>> this.type = type;
>>> this.r = renderer;
>>> this.am = null;
>>> this.defaultPaging = {
>>> 'start': 0,
>>> 'count': 1000,
>>> 'sortOrder': 'desc',
>>> 'sortBy': 'overview_createdtime',
>>> 'paginationLimit': 1000
>>> };
>>> }
>>>
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Thu, Aug 27, 2015 at 10:21 PM, Manuranga Perera <m...@wso2.com>
>>> wrote:
>>>
>>>> number 100 is hard-coded in modules dir please grep and fix. can you
>>>> meet me tomorrow?
>>>>
>>>> On Thu, Aug 27, 2015 at 6:40 PM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Adding Manuranga,
>>>>>
>>>>> On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram <kath...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> In ESB connector store, we are unable to publish the new connectors.
>>>>>> The ESB connector store publisher is restricted to view only 100
>>>>>> connectors. We are having more than 100 connectors to add to the store. 
>>>>>> Can
>>>>>> you suggest how to increase the limit in the wso2es-1.2.0-SNAPSHOT?
>>>>>>
>>>>>> Thanks,
>>>>>> Kathees
>>>>>> --
>>>>>> Kathees
>>>>>> Software Engineer,
>>>>>> email: kath...@wso2.com
>>>>>> mobile: +94772596173
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kathees
>>>>> Software Engineer,
>>>>> email: kath...@wso2.com
>>>>> mobile: +94772596173
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> With regards,
>>>> *Manu*ranga Perera.
>>>>
>>>> phone : 071 7 70 20 50
>>>> mail : m...@wso2.com
>>>>
>>>
>>>
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>
>>
>>
>> --
>> Sameera Medagammaddegedara
>> Software Engineer
>>
>> Contact:
>> Email: samee...@wso2.com
>> Mobile: + 94 077 255 3005
>>
>
>
>
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: samee...@wso2.com
> Mobile: + 94 077 255 3005
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

I shared the details and the pack link.

On Fri, Aug 28, 2015 at 12:38 PM, Malaka Silva mal...@wso2.com wrote:

 Kathees pls share the details.

 On Fri, Aug 28, 2015 at 11:54 AM, Manuranga Perera m...@wso2.com wrote:

 please send me a link to the pack you are using. or ping me on chat.

 On Fri, Aug 28, 2015 at 10:32 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Manuranga,

 The count and paginationLimit values are 1000 but 100 asserts only are
 listed. I tried to increase the number. The changes are not picked up.

 ../modules/rxt/scripts/asset/asset.js

 function AssetManager(registry, type, rxtManager, renderer) {
 this.registry = registry;
 this.rxtManager = rxtManager;
 this.rxtTemplate = rxtManager.getRxtDefinition(type);
 this.type = type;
 this.r = renderer;
 this.am = null;
 this.defaultPaging = {
 'start': 0,
 'count': 1000,
 'sortOrder': 'desc',
 'sortBy': 'overview_createdtime',
 'paginationLimit': 1000
 };
 }


 Thanks,
 Kathees

 On Thu, Aug 27, 2015 at 10:21 PM, Manuranga Perera m...@wso2.com
 wrote:

 number 100 is hard-coded in modules dir please grep and fix. can you
 meet me tomorrow?

 On Thu, Aug 27, 2015 at 6:40 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Adding Manuranga,

 On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 In ESB connector store, we are unable to publish the new connectors.
 The ESB connector store publisher is restricted to view only 100
 connectors. We are having more than 100 connectors to add to the store. 
 Can
 you suggest how to increase the limit in the wso2es-1.2.0-SNAPSHOT?

 Thanks,
 Kathees
 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com




 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

Hi,

In ESB connector store, we are unable to publish the new connectors. The
ESB connector store publisher is restricted to view only 100 connectors. We
are having more than 100 connectors to add to the store. Can you suggest
how to increase the limit in the wso2es-1.2.0-SNAPSHOT?

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

Adding Manuranga,

On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram kath...@wso2.com wrote:

 Hi,

 In ESB connector store, we are unable to publish the new connectors. The
 ESB connector store publisher is restricted to view only 100 connectors. We
 are having more than 100 connectors to add to the store. Can you suggest
 how to increase the limit in the wso2es-1.2.0-SNAPSHOT?

 Thanks,
 Kathees
 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Can't publish in Enterprise store

[Kathees Rajendram]

Hi Manuranga,

The count and paginationLimit values are 1000 but 100 asserts only are
listed. I tried to increase the number. The changes are not picked up.

../modules/rxt/scripts/asset/asset.js

function AssetManager(registry, type, rxtManager, renderer) {
this.registry = registry;
this.rxtManager = rxtManager;
this.rxtTemplate = rxtManager.getRxtDefinition(type);
this.type = type;
this.r = renderer;
this.am = null;
this.defaultPaging = {
'start': 0,
'count': 1000,
'sortOrder': 'desc',
'sortBy': 'overview_createdtime',
'paginationLimit': 1000
};
}


Thanks,
Kathees

On Thu, Aug 27, 2015 at 10:21 PM, Manuranga Perera m...@wso2.com wrote:

 number 100 is hard-coded in modules dir please grep and fix. can you meet
 me tomorrow?

 On Thu, Aug 27, 2015 at 6:40 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Adding Manuranga,

 On Thu, Aug 27, 2015 at 6:23 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 In ESB connector store, we are unable to publish the new connectors. The
 ESB connector store publisher is restricted to view only 100 connectors. We
 are having more than 100 connectors to add to the store. Can you suggest
 how to increase the limit in the wso2es-1.2.0-SNAPSHOT?

 Thanks,
 Kathees
 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Atom/RSS Inbound endpoint] Test Server for Automation test

[Kathees Rajendram]

Hi Rajjaz,

We need to automate the server startup also if the server startup is
available. We don't need to write the separate connector method for the
server startup. We can include the server startup in the integration test.

We can use the google blogspot to feed.
https://developers.google.com/gdata/docs/auth/oauth

Thanks,
Kathees

On Mon, Aug 24, 2015 at 7:11 PM, Rajjaz Mohammed raj...@wso2.com wrote:

 Hi All,
 I'm Developing Atom Connector and its Feed CRUD Operations are working
 fine for Implemented Testing Server and i need to know how to add the test
 Server to connector and Automation test. i have two options.

 1.write one method as startserver and do the operations follow by
 statrserver.
 2.write the Connector and run the server Separately Before Test the
 Connector.

 please Advice to me which is Best? and Atom/ RSS Connector Currently We
 can't test with 3rd party backend because of the Authentication methods are
 Different to each Backend and  Inbound Working with Atom and RSS and inject
 as Atom into ESB.

 Please Comments on it.

 On Tue, Aug 11, 2015 at 10:23 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi all,

 On Tue, Aug 11, 2015 at 8:59 AM, Malaka Silva mal...@wso2.com wrote:

 Hi Rajjaz,

 If there is a server already provided by automation framework then you
 don't have a blocker for writing the test cases.

 However if that is not the case, write your tests case assuming that
 there is a running server and comment it out. Once it's available we can
 include it to esb tests cases.

 @Automation Team - Do we already have support for this?


 No automation doesn't support for this. Why don't you guys write your own
 way to obtain atom URL and proceed. Its not practical for us to provide all
 test utilities upfront.

 BTW, you guys can use registry atom URLs -
 https://10.100.1.26:9443/registry/atom/_system/config/

 Thanks,
 Krishantha.





 On Tue, Aug 11, 2015 at 1:19 AM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 Hi Vanji,
 This is the way I’m developing. if I’m wrong please correct me.

 On Tue, Aug 11, 2015 at 12:58 AM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 Hi Vanji,
 We are creating a our own rss feed producer but we need to update it
 in 3rd party backend own by Client. that's the Requirement given to me.
 according that I’m Developing the Connector for 3rd party backend rss 
 feeds.

 On Mon, Aug 10, 2015 at 11:37 PM, Vanjikumaran Sivajothy 
 va...@wso2.com wrote:

 Rather than depending on 3rd party backend (like wordpress/
 blogspot.. etc), it is better to create own rss feed producer.

 On Mon, Aug 10, 2015 at 9:55 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Rajjaz,

 To write the automation test for the inbound lister, you can create
 a Java client to produce the feed to the URL. The inbound listener will
 consume the feeds from the URL then you can write the couple of test 
 cases
 to test the inbound listener. Other inbound automation test can be found
 below.


 https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration/tests-transport/src/test/java/org/wso2/carbon/esb

 Thanks,
 Kathees


 On Mon, Aug 10, 2015 at 6:11 PM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 for the Connector Part . Connector will create , update and Delete
 the feeds in given URL. so the URL may be a Blogger or Wordpress or
 something else so Test want to be able to do so.

 On Mon, Aug 10, 2015 at 5:16 PM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 Hi Irham,
 its an polling inbound to listen Atom/RSS feeds update in a given
 URL.

 On Mon, Aug 10, 2015 at 5:01 PM, Irham Iqbal iq...@wso2.com
 wrote:

 Hi Rajjaz,

 Can you elaborate the scenario which you're going to write
 integration tests.

 I mean what are the steps you're following to test this manually?

 Thanks,
 Iqbal

 On Mon, Aug 10, 2015 at 3:45 PM, Rajjaz Mohammed raj...@wso2.com
  wrote:

 *is there any methods available to do the Automation Test to my
 Atom/RSS inbound endpoint?

 On Mon, Aug 10, 2015 at 3:03 PM, Rajjaz Mohammed 
 raj...@wso2.com wrote:

 Hi All,
 I'm Developing Atom/RSS inbount endpoint for ESB so for the
 Automation test i need to test in multiple server like Blogger , 
 Wordpress
 . is the any method to do the Automation test?

 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/




 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Irham Iqbal
 Software Engineer - Test Automation
 WSO2, Inc.: http://wso2.com
 lean

[Dev] Please review and merge the PR.

[Kathees Rajendram]

Hi Malaka,

$subject please.

[1] - https://github.com/wso2/carbon-mediation/pull/377

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Atom/RSS Inbound endpoint] Test Server for Automation test

[Kathees Rajendram]

Hi Rajjaz,

To write the automation test for the inbound lister, you can create a Java
client to produce the feed to the URL. The inbound listener will consume
the feeds from the URL then you can write the couple of test cases to test
the inbound listener. Other inbound automation test can be found below.

https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration/tests-transport/src/test/java/org/wso2/carbon/esb

Thanks,
Kathees


On Mon, Aug 10, 2015 at 6:11 PM, Rajjaz Mohammed raj...@wso2.com wrote:

 for the Connector Part . Connector will create , update and Delete the
 feeds in given URL. so the URL may be a Blogger or Wordpress or something
 else so Test want to be able to do so.

 On Mon, Aug 10, 2015 at 5:16 PM, Rajjaz Mohammed raj...@wso2.com wrote:

 Hi Irham,
 its an polling inbound to listen Atom/RSS feeds update in a given URL.

 On Mon, Aug 10, 2015 at 5:01 PM, Irham Iqbal iq...@wso2.com wrote:

 Hi Rajjaz,

 Can you elaborate the scenario which you're going to write integration
 tests.

 I mean what are the steps you're following to test this manually?

 Thanks,
 Iqbal

 On Mon, Aug 10, 2015 at 3:45 PM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 *is there any methods available to do the Automation Test to my
 Atom/RSS inbound endpoint?

 On Mon, Aug 10, 2015 at 3:03 PM, Rajjaz Mohammed raj...@wso2.com
 wrote:

 Hi All,
 I'm Developing Atom/RSS inbount endpoint for ESB so for the Automation
 test i need to test in multiple server like Blogger , Wordpress . is the
 any method to do the Automation test?

 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/




 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Irham Iqbal
 Software Engineer - Test Automation
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452




 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/




 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94752833834
 Email  :raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 http://wso2.com/about/team/mohammer_rajjaz/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB][IS]Oauth1.0 support in the ESB

[Kathees Rajendram]

Hi IS/ESB Team,

I need to write the connector with the oauth1.0 [1]. Is the Outh1.0 with
the signature generation feature available in the ESB?

[1] -
https://docs.wso2.com/display/IS450/2-legged+OAuth+with+OAuth+1.0+and+2.0

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][IS]Oauth1.0 support in the ESB

[Kathees Rajendram]

Hi Vanji,

Yes, We can create the signature generation but If we have there we can
reuse.

For OAuth1.0 supported connectors. Shall we create a framework  with the
following the parameters in the connector core?
apiUri,consumerKeySecret, accessTokenSecret, httpMethod, URL parameters,
signaure method (HMAC-SHA1, RSA-SHA1, and PLAINTEXT) and encoding (UTF-8).

Thanks,
Kathees

On Mon, Aug 10, 2015 at 11:11 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:

 Hi Kathees,

 did you check the implementation of flickr connector?

 On Mon, Aug 10, 2015 at 10:37 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi IS/ESB Team,

 I need to write the connector with the oauth1.0 [1]. Is the Outh1.0 with
 the signature generation feature available in the ESB?

 [1] -
 https://docs.wso2.com/display/IS450/2-legged+OAuth+with+OAuth+1.0+and+2.0

 Thanks,
 Kathees
 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Vanjikumaran Sivajothy
 *Associate Technical Lead*
 *WSO2 Inc. http://wso2.com http://wso2.com/*
 *USA Mobile **+1-812-361-1286*
 *Srilanka Mobile:+94-777-219-209*
 [image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter]
 https://twitter.com/vanjikumaran [image: LinkedIn]
 http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image:
 Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]
 http://www.slideshare.net/vanjikumaran

 This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may
 have received this communication in error, please reply to the
 sender indicating that fact and delete the copy you received and in
 addition, you should not print, copy, re-transmit, disseminate, or
 otherwise use the information contained in this communication.
 Internet communications cannot be guaranteed to be timely, secure, error
 or virus-free. The sender does not accept liability for any errors
 or omissions




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] kafka UI improvement (ESBJAVA-3915)

[Kathees Rajendram]

Hi Shakila,

You can run the ESB Kafka Inbound sample 904 and make sure other Kafka
functionality is not affected.

Thanks,
Kathees

On Mon, Jul 20, 2015 at 9:51 PM, Shakila Sivagnanarajah shak...@wso2.com
wrote:

 Yes Malaka, I have tested with this change. This does not affect others.

 On Mon, Jul 20, 2015 at 5:47 PM, Malaka Silva mal...@wso2.com wrote:

 Have you tested the other inbound type after the change?

 On Mon, Jul 20, 2015 at 10:50 AM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi Malaka,

 I have modified the code according to your comment. Please find the PR
 [1].
 [1] https://github.com/wso2/carbon-mediation/pull/294

 Thank you

 On Fri, Jul 17, 2015 at 5:21 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Shakila,

 Added some comments.

 Did you check other inbound protocols with this change?

 Don't we need to apply the same for update page as well?

 On Fri, Jul 17, 2015 at 4:55 PM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi Malaka,

 Please review and merge PR[1] for $subject.

 [1] https://github.com/wso2/carbon-mediation/pull/294


 Thank you
 --
 Shakila Sivagnanarajah
 Associate Software Engineer
 Mobile :+94 (0) 770 760240
 shak...@wso2.com




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print
 this email only if it is absolutely necessary.




 --
 Shakila Sivagnanarajah
 Associate Software Engineer
 Mobile :+94 (0) 770 760240
 shak...@wso2.com




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




 --
 Shakila Sivagnanarajah
 Associate Software Engineer
 Mobile :+94 (0) 770 760240
 shak...@wso2.com




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue while creating custom Inbound

[Kathees Rajendram]

Hi Malaka,Senduran,

I was able to resolve As you suggested.

Thanks,
Kathees

On Fri, Jul 17, 2015 at 5:39 PM, Senduran Balasubramaniyam 
sendu...@wso2.com wrote:

 Hi Kathees,

 I think you are not exporting the twitter4j related jars
 Can you please try the following

 Export-Package
 org.wso2.carbon.inbound.custom.poll.*,

 org.twitter4j.*

 /Export-Package


 Regards
 Senduran


 On Fri, Jul 17, 2015 at 12:54 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Lakshani,

 Thank you the reply.
 I added and tried the jars to the component/lib also.I am getting the
 sample error. Am I missing in the pom while bundling?

 packagingbundle/packaging

 dependency
 groupIdorg.twitter4j/groupId
 artifactIdtwitter4j-core/artifactId
 version4.0.4/version
 /dependency
 dependency
 groupIdorg.twitter4j/groupId
 artifactIdtwitter4j-stream/artifactId
 version4.0.4/version
 /dependency

 plugin
 groupIdorg.apache.felix/groupId
 artifactIdmaven-bundle-plugin/artifactId
 version1.4.0/version
 extensionstrue/extensions
 configuration
 instructions
 Bundle-SymbolicName${pom.artifactId}/Bundle-SymbolicName
 Export-Package
 org.wso2.carbon.inbound.custom.poll.*,
 /Export-Package
 Import-Package
 !javax.xml.namespace,
 javax.xml.namespace;
 version=0.0.0,
 *;resolution:=optional,
 /Import-Package
 DynamicImport-Package*/DynamicImport-Package
 /instructions
 /configuration
 /plugin

 Thanks,
 Kathees


 On Fri, Jul 17, 2015 at 9:54 AM, Lakshani Gamage laksh...@wso2.com
 wrote:

 Hi Kathees,

 Seems your class has not been exported properly. Please see the error
 log.
 *Caused by: java.lang.**NoClassDefFoundError: twitter4j/StreamListener*

 May be you haven't created the osgi bundle properly. You can put the jar
 to component/lib directory. It will make the jar osgi and export all
 classes.

 Thank you,
 Lakshani.

 On Fri, Jul 17, 2015 at 8:50 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 While creating a custom inbound Endpoint I am getting the following
 error. In the custom endpoint,i used the twitter4j-stream dependency,
 bundled and added the dropins in the ESB.
 Can you suggest how to solve the issue?


 [2015-07-17 08:32:43,741]  INFO - GenericProcessor Inbound listener
 class for class org.wso2.carbon.inbound.custom.poll.SamplePollingClient
 starting ...
 [2015-07-17 08:30:47,846] ERROR - RPCMessageReceiver
 twitter4j/StreamListener
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at
 org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
 at
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
 at
 org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
 at
 org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 at
 org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
 at
 org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
 at
 org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
 at
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
 at org.apache.jasper.servlet.JspServlet.service

[Dev] Issue while creating custom Inbound

[Kathees Rajendram]

Hi,

While creating a custom inbound Endpoint I am getting the following error.
In the custom endpoint,i used the twitter4j-stream dependency, bundled and
added the dropins in the ESB.
Can you suggest how to solve the issue?


[2015-07-17 08:32:43,741]  INFO - GenericProcessor Inbound listener class
for class org.wso2.carbon.inbound.custom.poll.SamplePollingClient starting
...
[2015-07-17 08:30:47,846] ERROR - RPCMessageReceiver
twitter4j/StreamListener
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
at
org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
at
org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
at
org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at

Re: [Dev] Issue while creating custom Inbound

[Kathees Rajendram]

Hi Lakshani,

Thank you the reply.
I added and tried the jars to the component/lib also.I am getting the
sample error. Am I missing in the pom while bundling?

packagingbundle/packaging

dependency
groupIdorg.twitter4j/groupId
artifactIdtwitter4j-core/artifactId
version4.0.4/version
/dependency
dependency
groupIdorg.twitter4j/groupId
artifactIdtwitter4j-stream/artifactId
version4.0.4/version
/dependency

plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
version1.4.0/version
extensionstrue/extensions
configuration
instructions
Bundle-SymbolicName${pom.artifactId}/Bundle-SymbolicName
Export-Package
org.wso2.carbon.inbound.custom.poll.*,
/Export-Package
Import-Package
!javax.xml.namespace,
javax.xml.namespace;
version=0.0.0,
*;resolution:=optional,
/Import-Package
DynamicImport-Package*/DynamicImport-Package
/instructions
/configuration
/plugin

Thanks,
Kathees


On Fri, Jul 17, 2015 at 9:54 AM, Lakshani Gamage laksh...@wso2.com wrote:

 Hi Kathees,

 Seems your class has not been exported properly. Please see the error log.
 *Caused by: java.lang.**NoClassDefFoundError: twitter4j/StreamListener*

 May be you haven't created the osgi bundle properly. You can put the jar
 to component/lib directory. It will make the jar osgi and export all
 classes.

 Thank you,
 Lakshani.

 On Fri, Jul 17, 2015 at 8:50 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 While creating a custom inbound Endpoint I am getting the following
 error. In the custom endpoint,i used the twitter4j-stream dependency,
 bundled and added the dropins in the ESB.
 Can you suggest how to solve the issue?


 [2015-07-17 08:32:43,741]  INFO - GenericProcessor Inbound listener class
 for class org.wso2.carbon.inbound.custom.poll.SamplePollingClient starting
 ...
 [2015-07-17 08:30:47,846] ERROR - RPCMessageReceiver
 twitter4j/StreamListener
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at
 org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
 at
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
 at
 org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
 at
 org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 at
 org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
 at
 org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
 at
 org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
 at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
 at
 org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61

[Dev] ESB Kafka automation support

[Kathees Rajendram]

Hi All,

Is Kafka test support framework available in integration base? Now in the
integration we manually start the zookeeper and Kafka server.

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

$subject for the HTTP endpoint config changes for redmine connector.
[1] - https://github.com/wso2/esb-connectors/pull/221

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Yes,It worked without config changes. One method (findProducts) uses HTTP
endpoint and that is also not concatenated with any URL parameters.

Thanks,
Kathees

On Sat, Jun 27, 2015 at 8:35 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees.

 Connector is using HTTP Endpoints. Did it work without config changes with
 latest esb?

 On Sat, Jun 27, 2015 at 4:04 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Malaka,

 Please review and merge the PR[1] for the changes in eBay connector.

 [1] - https://github.com/wso2/esb-connectors/pull/210

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

ZendDesk connector's HTTP endpoint configuration changes are included in
the PR[1].

[1] - https://github.com/wso2/esb-connectors/pull/210

Thanks,
Kathees

On Sat, Jun 27, 2015 at 9:49 PM, Kathees Rajendram kath...@wso2.com wrote:

 Hi Malaka,

 Yes,It worked without config changes. One method (findProducts) uses HTTP
 endpoint and that is also not concatenated with any URL parameters.

 Thanks,
 Kathees

 On Sat, Jun 27, 2015 at 8:35 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees.

 Connector is using HTTP Endpoints. Did it work without config changes
 with latest esb?

 On Sat, Jun 27, 2015 at 4:04 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Malaka,

 Please review and merge the PR[1] for the changes in eBay connector.

 [1] - https://github.com/wso2/esb-connectors/pull/210

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for the changes in eBay connector.

[1] - https://github.com/wso2/esb-connectors/pull/210

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Kathees Rajendram]

4 methods are failing and 6 methods are skipped out of 25.

On Fri, Jun 26, 2015 at 6:21 PM, Malaka Silva mal...@wso2.com wrote:

 How many methods are there in the connector and how many are failing?

 On Fri, Jun 26, 2015 at 6:14 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Malaka,

 Please review and merge the PR[1] for Disqus.Some methods are failing
 because of *This method is currently under development* in API [2].

 [1] - https://github.com/wso2/esb-connectors/pull/208
 [2] - https://disqus.com/api/docs/threads/create/

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for Disqus.Some methods are failing
because of *This method is currently under development* in API [2].

[1] - https://github.com/wso2/esb-connectors/pull/208
[2] - https://disqus.com/api/docs/threads/create/

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Please review and merge the PR

[Kathees Rajendram]

Resolved.

On Thu, Jun 25, 2015 at 6:01 PM, Malaka Silva mal...@wso2.com wrote:

 Merged. Please mark the jiras

 On Thu, Jun 25, 2015 at 12:16 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 Please review and merge the PR[1] for ESBJAVA-3712, ESBJAVA-3767 and
 ESBJAVA-3765

 [1] - https://github.com/wso2/carbon-mediation/pull/251

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for the BrainTree connector Automation.

[1] - https://github.com/wso2/esb-connectors/pull/204

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Please review and merge the PR

[Kathees Rajendram]

Hi,

Please review and merge the PR[1] for ESBJAVA-3712, ESBJAVA-3767 and
ESBJAVA-3765

[1] - https://github.com/wso2/carbon-mediation/pull/251

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for Github and BrainTree.

[1] - https://github.com/wso2/esb-connectors/pull/165

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka

Please review and merge the PR [1] for Verticalresponse

[1] - https://github.com/wso2/esb-connectors/pull/159/files

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for Nexmo.

[1] - https://github.com/wso2/esb-connectors/pull/152

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for tradegecko

[1] - https://github.com/wso2/esb-connectors/pull/145

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1] for Dropbox

[1] - https://github.com/wso2/esb-connectors/pull/151

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR[1].

[1] - https://github.com/wso2/product-esb/pull/187


Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge for ESBJAVA-2089

[Kathees Rajendram]

Hi Malaka,

The target is a optional field,can be null.I have fixed.

Thanks,
Kathees

On Tue, Jun 9, 2015 at 11:40 AM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 What happens if the target is null with the new PR?

 On Sat, Jun 6, 2015 at 5:47 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Malaka,

 $subject please.
 PR - https://github.com/wso2/carbon-mediation/pull/200

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Kathees Rajendram]

Hi Malaka,

Please review and merge the PR [1] for ESBJAVA-3752.

[1] - https://github.com/wso2/carbon-mediation/pull/202

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge for ESBJAVA-2089

[Kathees Rajendram]

Hi Malaka,

$subject please.
PR - https://github.com/wso2/carbon-mediation/pull/200

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR[1] for ESBJAVA-3726

[Kathees Rajendram]

Hi Malaka,

$subject please.

[1] - https://github.com/wso2/carbon-mediation/pull/195

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MQTT Axis2 Transport

[Kathees Rajendram]

Hi Sriashalya,

The jira[1] is already created for the issue.I think you need to pass the
content type parameter in axis2.xml.
[1] - https://wso2.org/jira/browse/ESBJAVA-3436

Thanks,
Kathees

On Fri, May 22, 2015 at 12:05 PM, Sriashalya Srivathsan asha...@wso2.com
wrote:

 Hi Chanaka,
 Now I'm testing the broker through ESB with different message format.if we
 set the content type parameter only, we can send different formats of
 messages through ESB to mosquito broker. So how to do this?



 On Tue, May 19, 2015 at 4:08 PM, Sriashalya Srivathsan asha...@wso2.com
 wrote:

 looping to dev

 On Tue, May 19, 2015 at 2:32 PM, Sriashalya Srivathsan asha...@wso2.com
 wrote:

 Hi Chanaka,
 I've configured and setup mqtt axis2 transport through ESB with mosquito
 broker.
  But when I send one message from client, ESB listens bunch of messages
 and send those to broker.I'm looking on that.


 Thank you,

 On Mon, May 18, 2015 at 12:18 PM, Kasun Indrasiri ka...@wso2.com
 wrote:


 Hi Sriashalya,

 Can you try debugging the code and see why it is not working..
 In general, if you encounter any issues with ESB, the best thing is to
 debug and find out why its isn't working as expected. :)



 -- Forwarded message --
 From: Sriashalya Srivathsan asha...@wso2.com
 Date: Mon, May 18, 2015 at 12:12 PM
 Subject: [Dev] MQTT Axis2 Transport
 To: Chanaka Fernando chana...@wso2.com, WSO2 Developers' List 
 dev@wso2.org


 Hi Chanaka,
 I have tried $ subject with Mosquito broker.


- I've started the subscriber by following command

 mosquitto_sub -h 127.0.0.1 -t topic


- have made all the required changes to ESB.
- started the publisher through Java Client

 But I don't get any thing in the ESB console and subscriber console.



 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon-Mediation build failure

[Kathees Rajendram]

Hi Naasheer,

The ESB is in the middle of the release and they are fixing the issue. You
are able to build the inbound module since you are working related with the
inbound.

Thanks,
Kathees

On Fri, May 22, 2015 at 12:21 PM, Naasheer Ali naashe...@wso2.com wrote:

 Hi All,

 I'm building Carbon-Mediation from develop branch. I'm getting the
 following error, how can I solve this?

 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Carbon Mediation - Aggregator Pom . SUCCESS [
  0.697 s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module .. SUCCESS [
  0.272 s]
 [INFO] WSO2 Carbon - HL7 Store Stub ... SUCCESS [
  5.655 s]
 [INFO] WSO2 Carbon - Endpoint Editor Stub . SUCCESS [
  4.753 s]
 [INFO] WSO2 Carbon - localentry Stub .. SUCCESS [
  3.883 s]
 [INFO] WSO2 Carbon - Synapse Artifact Uploader Stub ... SUCCESS [
  2.644 s]
 [INFO] WSO2 Carbon - Synapse Configuration Service Administrator Stub
 SUCCESS [  3.419 s]
 [INFO] WSO2 Carbon - Mediation Library (Synapse) Management Stub SUCCESS [
  5.182 s]
 [INFO] WSO2 Carbon - Mediation Security Stub .. SUCCESS [
  2.805 s]
 [INFO] WSO2 Carbon - Template Editor Service Administrator Stub SUCCESS [
  6.733 s]
 [INFO] WSO2 Carbon - BAM Mediator Configuration Stub .. SUCCESS [
  3.945 s]
 [INFO] WSO2 Carbon - Class Mediator Admin Stub  SUCCESS [
  2.200 s]
 [INFO] WSO2 Carbon - Command Mediator Admin Stub .. SUCCESS [
  2.785 s]
 [INFO] WSO2 Carbon - Event Mediator Admin Stub  SUCCESS [
  3.079 s]
 [INFO] WSO2 Carbon - Message Processor Stub ... SUCCESS [
  4.291 s]
 [INFO] WSO2 Carbon - Message Store Stub ... SUCCESS [
  4.138 s]
 [INFO] WSO2 Carbon - Proxy Services Admin Stub  SUCCESS [
  5.825 s]
 [INFO] WSO2 Carbon - Sequence Editor Stub . SUCCESS [
  6.455 s]
 [INFO] WSO2 Carbon - Task Stub  SUCCESS [
  3.491 s]
 [INFO] WSO2 Carbon - Priority Mediation Stub .. SUCCESS [
  2.757 s]
 [INFO] WSO2 Carbon - Rest API Admin Stub .. SUCCESS [
  5.330 s]
 [INFO] WSO2 Carbon - Inbound Stub . SUCCESS [
  3.415 s]
 [INFO] WSO2 Carbon - ESB NTask Stub ... SUCCESS [
  3.518 s]
 [INFO] WSO2 Carbon - Publish Event Mediator Configuration Stub SUCCESS [
  3.278 s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module .. SUCCESS [
  0.099 s]
 [INFO] WSO2 Carbon - Mediation Statistics Stub  SUCCESS [
  3.567 s]
 [INFO] WSO2 Carbon - Mediation Tracer Stub  SUCCESS [
  3.487 s]
 [INFO] application-mgt-stub ... SUCCESS [
  0.072 s]
 [INFO] WSO2 Carbon - Application Management Synapse Stub .. SUCCESS [
  3.333 s]
 [INFO] WSO2 Carbon - Synapse Registries Aggregator Module . SUCCESS [
  0.019 s]
 [INFO] WSO2 Carbon - Mediation Registries . SUCCESS [
  3.790 s]
 [INFO] WSO2 Carbon - Mediation Initializer Aggregator Module SUCCESS [
  0.265 s]
 [INFO] WSO2 Carbon - Mediator Bridge .. SUCCESS [
  1.079 s]
 [INFO] WSO2 Carbon - Mediators Aggregator Module .. SUCCESS [
  0.015 s]
 [INFO] WSO2 Carbon - Router Mediator Aggregator Module  SUCCESS [
  0.020 s]
 [INFO] WSO2 Carbon - Router mediator .. SUCCESS [
  3.709 s]
 [INFO] WSO2 Carbon - Mediation Dependency Management .. SUCCESS [
  2.058 s]
 [INFO] WSO2 Carbon - Mediation admin- Aggregator Module ... SUCCESS [
  0.064 s]
 [INFO] WSO2 Carbon - Task Services  SUCCESS [
  1.444 s]
 [INFO] WSO2 Carbon - ntask Integration core ... SUCCESS [
  1.827 s]
 [INFO] WSO2 Carbon - Inbound Endpoint Module .. SUCCESS [
  0.597 s]
 [INFO] org.wso2.carbon.inbound.endpoint.persistence ... SUCCESS [
  1.602 s]
 [INFO] org.wso2.carbon.inbound.endpoint.osgi .. SUCCESS [
  1.457 s]
 [INFO] WSO2 Carbon - Clustering Integration ... SUCCESS [
  1.124 s]
 [INFO] org.wso2.carbon.inbound.endpoint ... SUCCESS [
  3.187 s]
 [INFO] WSO2 Carbon - Mediation Initializer  SUCCESS [
  3.989 s]
 [INFO] WSO2 Carbon - Mediation UI Menu Initializer  SUCCESS [
  0.268 s]
 [INFO] WSO2 Carbon Mediation - Transport Handlers . SUCCESS [
  1.311 s]
 [INFO] WSO2 Carbon - Mediation Monitor - Aggregator Module  SUCCESS [
  0.050 s]
 [INFO] WSO2 Carbon - Message Relay Parent . SUCCESS [
  0.019 s]
 [INFO] WSO2 Carbon - Message Relay  SUCCESS [
  0.907 s]
 [INFO] WSO2 Carbon - Message Relay Builder Mediator ... SUCCESS [
  0.972 s]
 [INFO] WSO2 Carbon - Message Relay Module . SUCCESS [
  3.687 s]
 [INFO] WSO2 Carbon - Mediation Statistics Aggregator Module SUCCESS [
  0.019 s]
 [INFO] WSO2 Carbon - Mediation statistics BE .. SUCCESS [
  2.483 s]
 [INFO] WSO2 Carbon - Mediation Statistics UI 

[Dev] [ESB] Please review and merge the PR[1]

[Kathees Rajendram]

Hi,

$subject for the Kafka inbound sample 904

[1] - https://github.com/wso2/product-esb/pull/162

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR[1] for ESBJAVA-3510

[Kathees Rajendram]

Hi,

$subject.

[1] - https://github.com/wso2/carbon-mediation/pull/135

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge the PR[1] for ESBJAVA-3510

[Kathees Rajendram]

Hi Malaka,

Ok,I will fix in the generic way.

Thanks
Kathees

On Mon, May 11, 2015 at 4:20 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 UI is written in a generic way. So fix also needs to be done in that
 manner.

 On Mon, May 11, 2015 at 4:19 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Malaka,

 The HTTP inbound endpoint does not have the advanced parameters but the
 show/hide icon is in UI. This fix is for removing the icon while HTTP
 endpoint.

 Thanks,
 Kathees

 On Mon, May 11, 2015 at 3:54 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 Here the fix checked for inbound http and does not show the advance
 option?

 The correct way should be to check if there are no advance parameters
 don't show that option?

 On Mon, May 11, 2015 at 1:30 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 $subject.

 [1] - https://github.com/wso2/carbon-mediation/pull/135

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print
 this email only if it is absolutely necessary.




 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge the PR[1] for ESBJAVA-3510

[Kathees Rajendram]

Hi Malaka,

The HTTP inbound endpoint does not have the advanced parameters but the
show/hide icon is in UI. This fix is for removing the icon while HTTP
endpoint.

Thanks,
Kathees

On Mon, May 11, 2015 at 3:54 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 Here the fix checked for inbound http and does not show the advance option?

 The correct way should be to check if there are no advance parameters
 don't show that option?

 On Mon, May 11, 2015 at 1:30 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 $subject.

 [1] - https://github.com/wso2/carbon-mediation/pull/135

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please merge the PR for Kafka Inbound

[Kathees Rajendram]

Hi,

$subject for [1].

[1] - https://github.com/wso2/carbon-mediation/pull/133

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] To test the latest carbon mediation code in the ESB

[Kathees Rajendram]

Hi,

I need to test the latest carbon mediation code in the ESB. I am getting
org.wso2.carbon.inbound.endpoint-4.4.1-SNAPSHOT.jar while building the
carbon-mediation from develop branch and org.wso2.carbon.inbound-4.4.0.jar
is in the ESB while building the product-esb from develop branch. How can I
test the carbon mediation in the ESB?


Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] To test the latest carbon mediation code in the ESB

[Kathees Rajendram]

Hi Malaka,

I built the ESB from develop branch of product-esb. there also,the version
and module name are different.

!-- Carbon mediation version --
carbon.mediation.version4.4.0/carbon.mediation.version

Thanks,
Kathees

On Sat, May 9, 2015 at 4:29 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 You need to to build the pack from product esb (develop branch) and use
 it. [1]

 [1] https://github.com/wso2/product-esb

 On Sat, May 9, 2015 at 4:17 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 You need to to build the pack from product esb and use it. [1]

 [1] https://github.com/wso2/product-esb

 On Sat, May 9, 2015 at 4:13 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I need to test the latest carbon mediation code in the ESB. I am getting
 org.wso2.carbon.inbound.endpoint-4.4.1-SNAPSHOT.jar while building the
 carbon-mediation from develop branch and org.wso2.carbon.inbound-4.4.0.jar
 is in the ESB while building the product-esb from develop branch. How can I
 test the carbon mediation in the ESB?


 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Long running test for the inbound transport

[Kathees Rajendram]

Hi,

I need to do long running test for the Kafka inbound transport. How can I
test and monitor the server for the memory issue?. Please advice me how to
test and monitor ,and
if you have any documentation or blog for this please share with me.

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Inbound protocol in ESB

[Kathees Rajendram]

Thank you Malaka.

On Tue, Apr 21, 2015 at 5:16 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 coordination - true (runs only on one worker node)
 coordination - false (runs on all worker nodes)

 sequential - true (Will mediate the message withing the same thread)
 sequential - false (Will mediate the message using inbound worker pool and
 take the next message) Will process multiple messages parallel.

 On Tue, Apr 21, 2015 at 4:45 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 We are having the common properties interval,coordination and sequence in
 the Inbound protocol. What is the use case of coordination and sequence in
 the inbound protocol? Please advice me how to test these use cases?

 Thanks,
 Kathees
 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Inbound protocol in ESB

[Kathees Rajendram]

Hi,

We are having the common properties interval,coordination and sequence in
the Inbound protocol. What is the use case of coordination and sequence in
the inbound protocol? Please advice me how to test these use cases?

Thanks,
Kathees
-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Testing Kafka Inbound in ESB cluster mode.

[Kathees Rajendram]

Hi Chanaka,Ravindra,

I was able to fix the issue as you suggested to create a new esb cluster
setup.

Thanks,
Kathees

On Tue, Apr 7, 2015 at 10:24 AM, Kathees Rajendram kath...@wso2.com wrote:

 Hi Chanaka,

 No,I created the esb cluster setup without elb and tested on that.I am
 getting same issue.


 Thanks,
 Kathees

 On Tue, Apr 7, 2015 at 9:59 AM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 Have you been able to fix your issue with the given suggestions?

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 4:34 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,

 Ok I will create the cluster setup without ELB.

 @Ravindra,
 I created the cluster with M8 pack which was built from developer
 branch. Ok I will try the cluster with esb M8 pack [1].

 [1] - https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/

 Thanks,
 Kathees

 On Mon, Apr 6, 2015 at 3:03 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Kathees,

 I'm not sure which ESB pack are you using. Anyway the M8 pack [1] was
 working fine for me. Could you please try that out and let us know.


 [1] https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/


 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:53 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 Can you setup a cluster without ELB and check on that?

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 2:50 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,Ravindra,

 I have the setup with a elb,a manager node and a worker node. As
 Chanaka mentioned I changed taskServerCount parameter value to 1 in both
 manager and worker node. Still I am getting the same error in both 
 manager
 and worker node.

 Thanks,
 Kathees

 On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 [Adding Kathees]

 On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Chanaka,

 Yes, I have encountered with this error while I was testing MSMP
 tasks in cluster mode. It was an intermittent issue.

 @Kathees: Could you please restart the manager node again and make
 sure that you have started one or more workers in the meantime as 
 Chanaka
 mentioned. AFAIK, manager node collects them as pending tasks and 
 schedules
 later once workers joined the cluster.



 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando chana...@wso2.com
  wrote:

 Hi Ravindra/Maheeka,

 Have you observed such an issue when you were testing tasks in
 cluster mode?

 Thanks,
 Chanaka

 -- Forwarded message --
 From: Chanaka Fernando chana...@wso2.com
 Date: Mon, Apr 6, 2015 at 1:42 PM
 Subject: Re: Testing Kafka Inbound in ESB cluster mode.
 To: Kathees Rajendram kath...@wso2.com
 Cc: DEV dev@wso2.org, Kasun Indrasiri ka...@wso2.com


 Hi Kathees,

 Have you started the worker nodes? By theory, Tasks are running on
 worker nodes. You need to have at least 1 worker node to start 
 executing
 the tasks. Also there is another configuration file which controls the
 minimum number of instances to start executing the tasks. This can be
 configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml*
 file with the below parameter.

 taskServerCount2/taskServerCount

 The value of 2 means that cluster will wait until 2 worker nodes
 are started for the execution of tasks.

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram 
 kath...@wso2.com wrote:

 Hi,

 I tested Kafka inbound in esb cluster mode. I have added required
 patches and inbound configuration in manager node. When I start the 
 manger
 node I am getting following error.

 Am I missing anything?

 [2015-04-06 12:32:55,977]  INFO - NTaskTaskManager Initialized
 task manager on manager node. Tenant [-1234]
 [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling
 task [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. 
 Error:
 No available task nodes for resolving a task location
 org.wso2.carbon.ntask.common.TaskException: No available task
 nodes for resolving a task location
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
 at
 org.wso2

Re: [Dev] Testing Kafka Inbound in ESB cluster mode.

[Kathees Rajendram]

Hi Chanaka,

No,I created the esb cluster setup without elb and tested on that.I am
getting same issue.


Thanks,
Kathees

On Tue, Apr 7, 2015 at 9:59 AM, Chanaka Fernando chana...@wso2.com wrote:

 Hi Kathees,

 Have you been able to fix your issue with the given suggestions?

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 4:34 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,

 Ok I will create the cluster setup without ELB.

 @Ravindra,
 I created the cluster with M8 pack which was built from developer branch.
 Ok I will try the cluster with esb M8 pack [1].

 [1] - https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/

 Thanks,
 Kathees

 On Mon, Apr 6, 2015 at 3:03 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Kathees,

 I'm not sure which ESB pack are you using. Anyway the M8 pack [1] was
 working fine for me. Could you please try that out and let us know.


 [1] https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/


 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:53 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 Can you setup a cluster without ELB and check on that?

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 2:50 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,Ravindra,

 I have the setup with a elb,a manager node and a worker node. As
 Chanaka mentioned I changed taskServerCount parameter value to 1 in both
 manager and worker node. Still I am getting the same error in both manager
 and worker node.

 Thanks,
 Kathees

 On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 [Adding Kathees]

 On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Chanaka,

 Yes, I have encountered with this error while I was testing MSMP
 tasks in cluster mode. It was an intermittent issue.

 @Kathees: Could you please restart the manager node again and make
 sure that you have started one or more workers in the meantime as 
 Chanaka
 mentioned. AFAIK, manager node collects them as pending tasks and 
 schedules
 later once workers joined the cluster.



 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Ravindra/Maheeka,

 Have you observed such an issue when you were testing tasks in
 cluster mode?

 Thanks,
 Chanaka

 -- Forwarded message --
 From: Chanaka Fernando chana...@wso2.com
 Date: Mon, Apr 6, 2015 at 1:42 PM
 Subject: Re: Testing Kafka Inbound in ESB cluster mode.
 To: Kathees Rajendram kath...@wso2.com
 Cc: DEV dev@wso2.org, Kasun Indrasiri ka...@wso2.com


 Hi Kathees,

 Have you started the worker nodes? By theory, Tasks are running on
 worker nodes. You need to have at least 1 worker node to start 
 executing
 the tasks. Also there is another configuration file which controls the
 minimum number of instances to start executing the tasks. This can be
 configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml*
 file with the below parameter.

 taskServerCount2/taskServerCount

 The value of 2 means that cluster will wait until 2 worker nodes
 are started for the execution of tasks.

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram 
 kath...@wso2.com wrote:

 Hi,

 I tested Kafka inbound in esb cluster mode. I have added required
 patches and inbound configuration in manager node. When I start the 
 manger
 node I am getting following error.

 Am I missing anything?

 [2015-04-06 12:32:55,977]  INFO - NTaskTaskManager Initialized
 task manager on manager node. Tenant [-1234]
 [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task
 [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: 
 No
 available task nodes for resolving a task location
 org.wso2.carbon.ntask.common.TaskException: No available task
 nodes for resolving a task location
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39

Re: [Dev] Testing Kafka Inbound in ESB cluster mode.

[Kathees Rajendram]

Hi Chanaka,

Ok I will create the cluster setup without ELB.

@Ravindra,
I created the cluster with M8 pack which was built from developer branch.
Ok I will try the cluster with esb M8 pack [1].

[1] - https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/

Thanks,
Kathees

On Mon, Apr 6, 2015 at 3:03 PM, Ravindra Ranwala ravin...@wso2.com wrote:

 Hi Kathees,

 I'm not sure which ESB pack are you using. Anyway the M8 pack [1] was
 working fine for me. Could you please try that out and let us know.


 [1] https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/


 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:53 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 Can you setup a cluster without ELB and check on that?

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 2:50 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,Ravindra,

 I have the setup with a elb,a manager node and a worker node. As Chanaka
 mentioned I changed taskServerCount parameter value to 1 in both manager
 and worker node. Still I am getting the same error in both manager and
 worker node.

 Thanks,
 Kathees

 On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 [Adding Kathees]

 On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Chanaka,

 Yes, I have encountered with this error while I was testing MSMP tasks
 in cluster mode. It was an intermittent issue.

 @Kathees: Could you please restart the manager node again and make
 sure that you have started one or more workers in the meantime as Chanaka
 mentioned. AFAIK, manager node collects them as pending tasks and 
 schedules
 later once workers joined the cluster.



 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Ravindra/Maheeka,

 Have you observed such an issue when you were testing tasks in
 cluster mode?

 Thanks,
 Chanaka

 -- Forwarded message --
 From: Chanaka Fernando chana...@wso2.com
 Date: Mon, Apr 6, 2015 at 1:42 PM
 Subject: Re: Testing Kafka Inbound in ESB cluster mode.
 To: Kathees Rajendram kath...@wso2.com
 Cc: DEV dev@wso2.org, Kasun Indrasiri ka...@wso2.com


 Hi Kathees,

 Have you started the worker nodes? By theory, Tasks are running on
 worker nodes. You need to have at least 1 worker node to start executing
 the tasks. Also there is another configuration file which controls the
 minimum number of instances to start executing the tasks. This can be
 configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml*
 file with the below parameter.

 taskServerCount2/taskServerCount

 The value of 2 means that cluster will wait until 2 worker nodes are
 started for the execution of tasks.

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I tested Kafka inbound in esb cluster mode. I have added required
 patches and inbound configuration in manager node. When I start the 
 manger
 node I am getting following error.

 Am I missing anything?

 [2015-04-06 12:32:55,977]  INFO - NTaskTaskManager Initialized task
 manager on manager node. Tenant [-1234]
 [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task
 [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: No
 available task nodes for resolving a task location
 org.wso2.carbon.ntask.common.TaskException: No available task nodes
 for resolving a task location
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432

[Dev] Testing Kafka Inbound in ESB cluster mode.

[Kathees Rajendram]

Hi,

I tested Kafka inbound in esb cluster mode. I have added required patches
and inbound configuration in manager node. When I start the manger node I
am getting following error.

Am I missing anything?

[2015-04-06 12:32:55,977]  INFO - NTaskTaskManager Initialized task manager
on manager node. Tenant [-1234]
[2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task
[[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: No
available task nodes for resolving a task location
org.wso2.carbon.ntask.common.TaskException: No available task nodes for
resolving a task location
at
org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275)
at
org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320)
at
org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
at
org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at

Re: [Dev] Testing Kafka Inbound in ESB cluster mode.

[Kathees Rajendram]

Hi Chanaka,Ravindra,

I have the setup with a elb,a manager node and a worker node. As Chanaka
mentioned I changed taskServerCount parameter value to 1 in both manager
and worker node. Still I am getting the same error in both manager and
worker node.

Thanks,
Kathees

On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando chana...@wso2.com wrote:

 [Adding Kathees]

 On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Hi Chanaka,

 Yes, I have encountered with this error while I was testing MSMP tasks in
 cluster mode. It was an intermittent issue.

 @Kathees: Could you please restart the manager node again and make sure
 that you have started one or more workers in the meantime as Chanaka
 mentioned. AFAIK, manager node collects them as pending tasks and schedules
 later once workers joined the cluster.



 Thanks  Regards,

 On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Ravindra/Maheeka,

 Have you observed such an issue when you were testing tasks in cluster
 mode?

 Thanks,
 Chanaka

 -- Forwarded message --
 From: Chanaka Fernando chana...@wso2.com
 Date: Mon, Apr 6, 2015 at 1:42 PM
 Subject: Re: Testing Kafka Inbound in ESB cluster mode.
 To: Kathees Rajendram kath...@wso2.com
 Cc: DEV dev@wso2.org, Kasun Indrasiri ka...@wso2.com


 Hi Kathees,

 Have you started the worker nodes? By theory, Tasks are running on
 worker nodes. You need to have at least 1 worker node to start executing
 the tasks. Also there is another configuration file which controls the
 minimum number of instances to start executing the tasks. This can be
 configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml* file
 with the below parameter.

 taskServerCount2/taskServerCount

 The value of 2 means that cluster will wait until 2 worker nodes are
 started for the execution of tasks.

 Thanks,
 Chanaka

 On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I tested Kafka inbound in esb cluster mode. I have added required
 patches and inbound configuration in manager node. When I start the manger
 node I am getting following error.

 Am I missing anything?

 [2015-04-06 12:32:55,977]  INFO - NTaskTaskManager Initialized task
 manager on manager node. Tenant [-1234]
 [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task
 [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: No
 available task nodes for resolving a task location
 org.wso2.carbon.ntask.common.TaskException: No available task nodes for
 resolving a task location
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275)
 at
 org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320)
 at
 org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103)
 at
 org.wso2.carbon.mediation.ntask.internal.NtaskService.setConfigurationContextService(NtaskService.java:96)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:432)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
 at
 org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
 at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230

Re: [Dev] Build failure while building the carbon mediation in develop branch

[Kathees Rajendram]

Thanks Chanaka, Vishanth,

I was able to build  carbon mediation in develop branch.


Thanks,
Kathees



On Thu, Mar 26, 2015 at 11:18 PM, Vishanth Balasubramaniam 
vishan...@wso2.com wrote:

 Hi Kathees,

 Did you make any changes in PersistenceUtils.java class? If so, please
 share it.

 Thanks,
 Vishanth

 On Thu, Mar 26, 2015 at 5:07 PM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 I was able to build carbon-mediation develop branch without any issue.
 Have you been able to figure out the issue?

 Thanks,
 Chanaka

 On Thu, Mar 26, 2015 at 12:45 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Chanaka,

 I used java 1.7.0_55. As you recommended I am using java 1.6.0_38.I am
 getting same failure.

 Thanks
 Kathees

 On Thu, Mar 26, 2015 at 11:59 AM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Kathees,

 What is the java version you are using to build the code? If it is 1.7,
 then use 1.6.

 Thanks,
 Chanaka

 On Thu, Mar 26, 2015 at 11:47 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I am getting the following build failure while building the carbon
 mediation from develop branch.
 This failure occurs due to
 org.apache.synapse.transport.passthru.core.ssl.SSLConfiguration is not
 resolved in org.wso2.carbon.inbound.endpoint.persistence module.

 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Carbon Mediation - Aggregator Pom  SUCCESS
 [0.525s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS
 [0.168s]
 [INFO] WSO2 Carbon - HL7 Store Stub .. SUCCESS
 [1:02.619s]
 [INFO] WSO2 Carbon - Endpoint Editor Stub  SUCCESS
 [3.467s]
 [INFO] WSO2 Carbon - localentry Stub . SUCCESS
 [3.057s]
 [INFO] WSO2 Carbon - Synapse Artifact Uploader Stub .. SUCCESS
 [2.160s]
 [INFO] WSO2 Carbon - Synapse Configuration Service Administrator Stub
 SUCCESS [2.936s]
 [INFO] WSO2 Carbon - Mediation Library (Synapse) Management Stub
 SUCCESS [4.056s]
 [INFO] WSO2 Carbon - Mediation Security Stub . SUCCESS
 [1.902s]
 [INFO] WSO2 Carbon - Template Editor Service Administrator Stub
 SUCCESS [4.325s]
 [INFO] WSO2 Carbon - BAM Mediator Configuration Stub . SUCCESS
 [2.582s]
 [INFO] WSO2 Carbon - Class Mediator Admin Stub ... SUCCESS
 [1.752s]
 [INFO] WSO2 Carbon - Command Mediator Admin Stub . SUCCESS
 [1.732s]
 [INFO] WSO2 Carbon - Event Mediator Admin Stub ... SUCCESS
 [2.019s]
 [INFO] WSO2 Carbon - Message Processor Stub .. SUCCESS
 [2.831s]
 [INFO] WSO2 Carbon - Message Store Stub .. SUCCESS
 [2.802s]
 [INFO] WSO2 Carbon - Proxy Services Admin Stub ... SUCCESS
 [3.236s]
 [INFO] WSO2 Carbon - Sequence Editor Stub  SUCCESS
 [3.394s]
 [INFO] WSO2 Carbon - Task Stub ... SUCCESS
 [2.406s]
 [INFO] WSO2 Carbon - Priority Mediation Stub . SUCCESS
 [1.907s]
 [INFO] WSO2 Carbon - Rest API Admin Stub . SUCCESS
 [3.615s]
 [INFO] WSO2 Carbon - Inbound Stub  SUCCESS
 [2.372s]
 [INFO] WSO2 Carbon - ESB NTask Stub .. SUCCESS
 [2.466s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS
 [0.046s]
 [INFO] WSO2 Carbon - Mediation Statistics Stub ... SUCCESS
 [2.829s]
 [INFO] WSO2 Carbon - Mediation Tracer Stub ... SUCCESS
 [2.375s]
 [INFO] application-mgt-stub .. SUCCESS
 [0.016s]
 [INFO] WSO2 Carbon - Application Management Synapse Stub . SUCCESS
 [2.369s]
 [INFO] WSO2 Carbon - Synapse Registries Aggregator Module  SUCCESS
 [0.014s]
 [INFO] WSO2 Carbon - Mediation Registries  SUCCESS
 [45.186s]
 [INFO] WSO2 Carbon - Mediation Initializer Aggregator Module  SUCCESS
 [0.015s]
 [INFO] WSO2 Carbon - Mediator Bridge . SUCCESS
 [0.492s]
 [INFO] WSO2 Carbon - Mediators Aggregator Module . SUCCESS
 [0.013s]
 [INFO] WSO2 Carbon - Router Mediator Aggregator Module ... SUCCESS
 [0.014s]
 [INFO] WSO2 Carbon - Router mediator . SUCCESS
 [1.031s]
 [INFO] WSO2 Carbon - Mediation Dependency Management . SUCCESS
 [10.759s]
 [INFO] WSO2 Carbon - Mediation admin- Aggregator Module .. SUCCESS
 [0.012s]
 [INFO] WSO2 Carbon - Task Services ... SUCCESS
 [0.855s]
 [INFO] WSO2 Carbon - ntask Integration core .. SUCCESS
 [1.282s]
 [INFO] WSO2 Carbon - Inbound Endpoint Module . SUCCESS
 [0.261s]
 [INFO] org.wso2.carbon.inbound.endpoint.persistence .. FAILURE
 [0.645s]
 [INFO] WSO2 Carbon - Clustering Integration .. SKIPPED
 [INFO] org.wso2.carbon.inbound.endpoint .. SKIPPED
 [INFO] WSO2 Carbon - Mediation Initializer ... SKIPPED
 [INFO] WSO2 Carbon - Mediation UI Menu Initializer ... SKIPPED
 [INFO] WSO2 Carbon Mediation - Transport Handlers  SKIPPED
 [INFO] WSO2 Carbon - Mediation Monitor - Aggregator Module  SKIPPED
 [INFO] WSO2 Carbon - Message

[Dev] Build failure while building the carbon mediation in develop branch

[Kathees Rajendram]

Hi,

I am getting the following build failure while building the carbon
mediation from develop branch.
This failure occurs due to
org.apache.synapse.transport.passthru.core.ssl.SSLConfiguration is not
resolved in org.wso2.carbon.inbound.endpoint.persistence module.

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon Mediation - Aggregator Pom  SUCCESS [0.525s]
[INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS [0.168s]
[INFO] WSO2 Carbon - HL7 Store Stub .. SUCCESS
[1:02.619s]
[INFO] WSO2 Carbon - Endpoint Editor Stub  SUCCESS [3.467s]
[INFO] WSO2 Carbon - localentry Stub . SUCCESS [3.057s]
[INFO] WSO2 Carbon - Synapse Artifact Uploader Stub .. SUCCESS [2.160s]
[INFO] WSO2 Carbon - Synapse Configuration Service Administrator Stub
SUCCESS [2.936s]
[INFO] WSO2 Carbon - Mediation Library (Synapse) Management Stub  SUCCESS
[4.056s]
[INFO] WSO2 Carbon - Mediation Security Stub . SUCCESS [1.902s]
[INFO] WSO2 Carbon - Template Editor Service Administrator Stub  SUCCESS
[4.325s]
[INFO] WSO2 Carbon - BAM Mediator Configuration Stub . SUCCESS [2.582s]
[INFO] WSO2 Carbon - Class Mediator Admin Stub ... SUCCESS [1.752s]
[INFO] WSO2 Carbon - Command Mediator Admin Stub . SUCCESS [1.732s]
[INFO] WSO2 Carbon - Event Mediator Admin Stub ... SUCCESS [2.019s]
[INFO] WSO2 Carbon - Message Processor Stub .. SUCCESS [2.831s]
[INFO] WSO2 Carbon - Message Store Stub .. SUCCESS [2.802s]
[INFO] WSO2 Carbon - Proxy Services Admin Stub ... SUCCESS [3.236s]
[INFO] WSO2 Carbon - Sequence Editor Stub  SUCCESS [3.394s]
[INFO] WSO2 Carbon - Task Stub ... SUCCESS [2.406s]
[INFO] WSO2 Carbon - Priority Mediation Stub . SUCCESS [1.907s]
[INFO] WSO2 Carbon - Rest API Admin Stub . SUCCESS [3.615s]
[INFO] WSO2 Carbon - Inbound Stub  SUCCESS [2.372s]
[INFO] WSO2 Carbon - ESB NTask Stub .. SUCCESS [2.466s]
[INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS [0.046s]
[INFO] WSO2 Carbon - Mediation Statistics Stub ... SUCCESS [2.829s]
[INFO] WSO2 Carbon - Mediation Tracer Stub ... SUCCESS [2.375s]
[INFO] application-mgt-stub .. SUCCESS [0.016s]
[INFO] WSO2 Carbon - Application Management Synapse Stub . SUCCESS [2.369s]
[INFO] WSO2 Carbon - Synapse Registries Aggregator Module  SUCCESS [0.014s]
[INFO] WSO2 Carbon - Mediation Registries  SUCCESS [45.186s]
[INFO] WSO2 Carbon - Mediation Initializer Aggregator Module  SUCCESS
[0.015s]
[INFO] WSO2 Carbon - Mediator Bridge . SUCCESS [0.492s]
[INFO] WSO2 Carbon - Mediators Aggregator Module . SUCCESS [0.013s]
[INFO] WSO2 Carbon - Router Mediator Aggregator Module ... SUCCESS [0.014s]
[INFO] WSO2 Carbon - Router mediator . SUCCESS [1.031s]
[INFO] WSO2 Carbon - Mediation Dependency Management . SUCCESS [10.759s]
[INFO] WSO2 Carbon - Mediation admin- Aggregator Module .. SUCCESS [0.012s]
[INFO] WSO2 Carbon - Task Services ... SUCCESS [0.855s]
[INFO] WSO2 Carbon - ntask Integration core .. SUCCESS [1.282s]
[INFO] WSO2 Carbon - Inbound Endpoint Module . SUCCESS [0.261s]
[INFO] org.wso2.carbon.inbound.endpoint.persistence .. FAILURE [0.645s]
[INFO] WSO2 Carbon - Clustering Integration .. SKIPPED
[INFO] org.wso2.carbon.inbound.endpoint .. SKIPPED
[INFO] WSO2 Carbon - Mediation Initializer ... SKIPPED
[INFO] WSO2 Carbon - Mediation UI Menu Initializer ... SKIPPED
[INFO] WSO2 Carbon Mediation - Transport Handlers  SKIPPED
[INFO] WSO2 Carbon - Mediation Monitor - Aggregator Module  SKIPPED
[INFO] WSO2 Carbon - Message Relay Parent  SKIPPED
[INFO] WSO2 Carbon - Message Relay ... SKIPPED
[INFO] WSO2 Carbon - Message Relay Builder Mediator .. SKIPPED
[INFO] WSO2 Carbon - Message Relay Module  SKIPPED
[INFO] WSO2 Carbon - Mediation Statistics Aggregator Module  SKIPPED
[INFO] WSO2 Carbon - Mediation statistics BE . SKIPPED
[INFO] WSO2 Carbon - Mediation Statistics UI . SKIPPED
[INFO] WSO2 Carbon - Mediation Tracer Aggregator Module .. SKIPPED
[INFO] WSO2 Carbon - Mediation Tracer BE . SKIPPED
[INFO] WSO2 Carbon - Mediation Tracer UI . SKIPPED
[INFO] WSO2 Carbon - Proxy Services Admin BE . SKIPPED
[INFO] WSO2 Carbon - Mediator OSGi Service ... SKIPPED
[INFO] WSO2 Carbon - Mediation config admin- Aggregator Module  SKIPPED
[INFO] WSO2 Carbon - Synapse Configuration Service Administrator  SKIPPED
[INFO] WSO2 Carbon - Synapse Configuration Service Administrator UI  SKIPPED
[INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SKIPPED
[INFO] WSO2 Carbon - HL7 Business Messaging 

Re: [Dev] Build failure while building the carbon mediation in develop branch

[Kathees Rajendram]

Hi Chanaka,

I used java 1.7.0_55. As you recommended I am using java 1.6.0_38.I am
getting same failure.

Thanks
Kathees

On Thu, Mar 26, 2015 at 11:59 AM, Chanaka Fernando chana...@wso2.com
wrote:

 Hi Kathees,

 What is the java version you are using to build the code? If it is 1.7,
 then use 1.6.

 Thanks,
 Chanaka

 On Thu, Mar 26, 2015 at 11:47 AM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I am getting the following build failure while building the carbon
 mediation from develop branch.
 This failure occurs due to
 org.apache.synapse.transport.passthru.core.ssl.SSLConfiguration is not
 resolved in org.wso2.carbon.inbound.endpoint.persistence module.

 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Carbon Mediation - Aggregator Pom  SUCCESS
 [0.525s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS
 [0.168s]
 [INFO] WSO2 Carbon - HL7 Store Stub .. SUCCESS
 [1:02.619s]
 [INFO] WSO2 Carbon - Endpoint Editor Stub  SUCCESS
 [3.467s]
 [INFO] WSO2 Carbon - localentry Stub . SUCCESS
 [3.057s]
 [INFO] WSO2 Carbon - Synapse Artifact Uploader Stub .. SUCCESS
 [2.160s]
 [INFO] WSO2 Carbon - Synapse Configuration Service Administrator Stub
 SUCCESS [2.936s]
 [INFO] WSO2 Carbon - Mediation Library (Synapse) Management Stub  SUCCESS
 [4.056s]
 [INFO] WSO2 Carbon - Mediation Security Stub . SUCCESS
 [1.902s]
 [INFO] WSO2 Carbon - Template Editor Service Administrator Stub  SUCCESS
 [4.325s]
 [INFO] WSO2 Carbon - BAM Mediator Configuration Stub . SUCCESS
 [2.582s]
 [INFO] WSO2 Carbon - Class Mediator Admin Stub ... SUCCESS
 [1.752s]
 [INFO] WSO2 Carbon - Command Mediator Admin Stub . SUCCESS
 [1.732s]
 [INFO] WSO2 Carbon - Event Mediator Admin Stub ... SUCCESS
 [2.019s]
 [INFO] WSO2 Carbon - Message Processor Stub .. SUCCESS
 [2.831s]
 [INFO] WSO2 Carbon - Message Store Stub .. SUCCESS
 [2.802s]
 [INFO] WSO2 Carbon - Proxy Services Admin Stub ... SUCCESS
 [3.236s]
 [INFO] WSO2 Carbon - Sequence Editor Stub  SUCCESS
 [3.394s]
 [INFO] WSO2 Carbon - Task Stub ... SUCCESS
 [2.406s]
 [INFO] WSO2 Carbon - Priority Mediation Stub . SUCCESS
 [1.907s]
 [INFO] WSO2 Carbon - Rest API Admin Stub . SUCCESS
 [3.615s]
 [INFO] WSO2 Carbon - Inbound Stub  SUCCESS
 [2.372s]
 [INFO] WSO2 Carbon - ESB NTask Stub .. SUCCESS
 [2.466s]
 [INFO] WSO2 Carbon - Business Adaptors Aggregator Module . SUCCESS
 [0.046s]
 [INFO] WSO2 Carbon - Mediation Statistics Stub ... SUCCESS
 [2.829s]
 [INFO] WSO2 Carbon - Mediation Tracer Stub ... SUCCESS
 [2.375s]
 [INFO] application-mgt-stub .. SUCCESS
 [0.016s]
 [INFO] WSO2 Carbon - Application Management Synapse Stub . SUCCESS
 [2.369s]
 [INFO] WSO2 Carbon - Synapse Registries Aggregator Module  SUCCESS
 [0.014s]
 [INFO] WSO2 Carbon - Mediation Registries  SUCCESS
 [45.186s]
 [INFO] WSO2 Carbon - Mediation Initializer Aggregator Module  SUCCESS
 [0.015s]
 [INFO] WSO2 Carbon - Mediator Bridge . SUCCESS
 [0.492s]
 [INFO] WSO2 Carbon - Mediators Aggregator Module . SUCCESS
 [0.013s]
 [INFO] WSO2 Carbon - Router Mediator Aggregator Module ... SUCCESS
 [0.014s]
 [INFO] WSO2 Carbon - Router mediator . SUCCESS
 [1.031s]
 [INFO] WSO2 Carbon - Mediation Dependency Management . SUCCESS
 [10.759s]
 [INFO] WSO2 Carbon - Mediation admin- Aggregator Module .. SUCCESS
 [0.012s]
 [INFO] WSO2 Carbon - Task Services ... SUCCESS
 [0.855s]
 [INFO] WSO2 Carbon - ntask Integration core .. SUCCESS
 [1.282s]
 [INFO] WSO2 Carbon - Inbound Endpoint Module . SUCCESS
 [0.261s]
 [INFO] org.wso2.carbon.inbound.endpoint.persistence .. FAILURE
 [0.645s]
 [INFO] WSO2 Carbon - Clustering Integration .. SKIPPED
 [INFO] org.wso2.carbon.inbound.endpoint .. SKIPPED
 [INFO] WSO2 Carbon - Mediation Initializer ... SKIPPED
 [INFO] WSO2 Carbon - Mediation UI Menu Initializer ... SKIPPED
 [INFO] WSO2 Carbon Mediation - Transport Handlers  SKIPPED
 [INFO] WSO2 Carbon - Mediation Monitor - Aggregator Module  SKIPPED
 [INFO] WSO2 Carbon - Message Relay Parent  SKIPPED
 [INFO] WSO2 Carbon - Message Relay ... SKIPPED
 [INFO] WSO2 Carbon - Message Relay Builder Mediator .. SKIPPED
 [INFO] WSO2 Carbon - Message Relay Module  SKIPPED
 [INFO] WSO2 Carbon - Mediation Statistics Aggregator Module  SKIPPED
 [INFO] WSO2 Carbon - Mediation statistics BE . SKIPPED
 [INFO] WSO2 Carbon - Mediation Statistics UI . SKIPPED
 [INFO] WSO2 Carbon - Mediation Tracer Aggregator Module .. SKIPPED
 [INFO] WSO2 Carbon - Mediation Tracer BE . SKIPPED
 [INFO] WSO2 Carbon - Mediation Tracer

[Dev] Integration test for blocking calls in call mediator

[Kathees Rajendram]

Hi Isuru,

Please find the PR[1] for $subject.

I tried to add the integration test for the MTOM and out only
request/response. That is not handled. I will fix the functionality and add
the integration test for that.

https://github.com/wso2/product-esb/pull/101

Thanks
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] wso2esb-4.9.0-M8-SNAPSHOT

[Kathees Rajendram]

Hi,

I implemented and tested in wso2 esb-4.9.0-M7-SNAPSHOT. I tried to add the
synapse and carbon mediation jar to the wso2 esb-4.9.0-M8-SNAPSHOT pack.
The changes are not picking in ESB M8.
I built the ESB M8 pack from develop branch.

Any suggestion please?

Thanks
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] wso2esb-4.9.0-M8-SNAPSHOT

[Kathees Rajendram]

Hi Vanji,

The synapse version are same in the M7 and M8 pack.
synapse-core_2.1.3.wso2v2-SNAPSHOT.jar is in M7 pack and
synapse-core_2.1.3.wso2v2.jar is in M8 pack.

Thanks
Kathees

On Fri, Mar 13, 2015 at 12:19 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:

 Is the synapse version same in the M7 and M8??


 On Fri, Mar 13, 2015 at 12:16 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I implemented and tested in wso2 esb-4.9.0-M7-SNAPSHOT. I tried to add
 the synapse and carbon mediation jar to the wso2 esb-4.9.0-M8-SNAPSHOT
 pack. The changes are not picking in ESB M8.
 I built the ESB M8 pack from develop branch.

 Any suggestion please?

 Thanks
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sivajothy Vanjikumaran
 *Senior Software Engineer*
 *Integration Technologies Team*
 *WSO2 Inc. http://wso2.com http://wso2.com/*
 *Mobile:(+94)777219209*
 [image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter]
 https://twitter.com/vanjikumaran [image: LinkedIn]
 http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image:
 Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]
 http://www.slideshare.net/vanjikumaran

 This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may
 have received this communication in error, please reply to the
 sender indicating that fact and delete the copy you received and in
 addition, you should not print, copy, re-transmit, disseminate, or
 otherwise use the information contained in this communication.
 Internet communications cannot be guaranteed to be timely, secure, error
 or virus-free. The sender does not accept liability for any errors
 or omissions




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sample 100 Failed in WSO2 ESB 4.9.0-SNAPSHOT

[Kathees Rajendram]

Thanks Vanji and Thilini.

The issue was in my configuration that the response has the security header
when ESB send back to client. I used the following configuration to remove
the security header Now it is working.

header xmlns:wsse=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd

 name=wsse:Security
 action=remove/

Thanks,
Kathees

On Fri, Mar 6, 2015 at 9:04 AM, Thilini Cooray thili...@wso2.com wrote:

 Hi Kathees,

 Did you store unlimited strength policy files [1] in
 JAVA_HOME/jre/lib/security folder ?

 [1]
 http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

 On Wed, Mar 4, 2015 at 6:43 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Vanji,

 I am getting above exception when I run the esb sample 100. I followed
 the steps as it is in the documentation[1].
 [1] -
 https://docs.wso2.com/display/ESB481/Sample+100%3A+Using+WS-Security+for+Outgoing+Messages

 Thanks,
 Kathees

 On Wed, Mar 4, 2015 at 6:14 PM, Vanjikumaran Sivajothy va...@wso2.com
 wrote:

 Hi Kathees,

 You question is not clear! Can you please elaborate more on what you
 have done?

 On Wed, Mar 4, 2015 at 5:52 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I am getting following exception when I invoke the service.

 [2015-03-04 17:27:00,003] ERROR - AxisEngine Missing wsse:Security
 header in request
 org.apache.axis2.AxisFault: Missing wsse:Security header in request
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:235)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: org.apache.rampart.RampartException: Missing wsse:Security
 header in request
 at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
 ... 9 more
 [2015-03-04 17:27:00,004] ERROR - ClientWorker Fault processing
 response message through Axis2
 org.apache.axis2.AxisFault: Missing wsse:Security header in request
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:235)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: org.apache.rampart.RampartException: Missing wsse:Security
 header in request
 at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
 ... 9 more


 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sivajothy Vanjikumaran
 *Senior Software Engineer*
 *Integration Technologies Team*
 *WSO2 Inc. http://wso2.com http://wso2.com/*
 *Mobile:(+94)777219209*
 [image: Facebook] https://www.facebook.com/vanjikumaran [image:
 Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]
 http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image:
 Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]
 http://www.slideshare.net/vanjikumaran

 This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may
 have received this communication in error, please reply to the
 sender indicating that fact and delete the copy you received and in
 addition, you should not print, copy, re-transmit, disseminate, or
 otherwise use

Re: [Dev] Sample 100 Failed in WSO2 ESB 4.9.0-SNAPSHOT

[Kathees Rajendram]

Hi Vanji,

It is in the doc. I didn't test the esb sample 100 after I got the issue. I
tested the security scenario in new implementation and used the following
configuration It is working.

header name=Action value=urn:getQuote/
 payloadFactory media-type=xml
format
   m0:getQuote xmlns:m0=http://services.samples;
  m0:request
 m0:symbolWSO2/m0:symbol
  /m0:request
   /m0:getQuote
/format
args/
 /payloadFactory
 call blocking=true
endpoint
   address uri=http://localhost:9000/services/SecureStockQuoteService

  enableSec policy=sec_policy/
   /address
/endpoint
 /call
 property name=RESPONSE value=true/
 header name=To action=remove/
 header xmlns:wsse=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd

 name=wsse:Security
 action=remove/
 send/
 drop/


Thanks,
kathees


On Tue, Mar 10, 2015 at 12:43 PM, Vanjikumaran Sivajothy va...@wso2.com
wrote:

 isn't that mentioned in the doc?

 On Tue, Mar 10, 2015 at 12:42 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Thanks Vanji and Thilini.

 The issue was in my configuration that the response has the security
 header when ESB send back to client. I used the following configuration to
 remove the security header Now it is working.

 header xmlns:wsse=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
 
  name=wsse:Security
  action=remove/

 Thanks,
 Kathees

 On Fri, Mar 6, 2015 at 9:04 AM, Thilini Cooray thili...@wso2.com wrote:

 Hi Kathees,

 Did you store unlimited strength policy files [1] in
 JAVA_HOME/jre/lib/security folder ?

 [1]
 http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

 On Wed, Mar 4, 2015 at 6:43 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Vanji,

 I am getting above exception when I run the esb sample 100. I followed
 the steps as it is in the documentation[1].
 [1] -
 https://docs.wso2.com/display/ESB481/Sample+100%3A+Using+WS-Security+for+Outgoing+Messages

 Thanks,
 Kathees

 On Wed, Mar 4, 2015 at 6:14 PM, Vanjikumaran Sivajothy va...@wso2.com
 wrote:

 Hi Kathees,

 You question is not clear! Can you please elaborate more on what you
 have done?

 On Wed, Mar 4, 2015 at 5:52 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 I am getting following exception when I invoke the service.

 [2015-03-04 17:27:00,003] ERROR - AxisEngine Missing wsse:Security
 header in request
 org.apache.axis2.AxisFault: Missing wsse:Security header in request
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:235)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: org.apache.rampart.RampartException: Missing wsse:Security
 header in request
 at
 org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
 ... 9 more
 [2015-03-04 17:27:00,004] ERROR - ClientWorker Fault processing
 response message through Axis2
 org.apache.axis2.AxisFault: Missing wsse:Security header in request
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:235)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: org.apache.rampart.RampartException: Missing wsse:Security
 header in request
 at
 org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
 ... 9 more

Re: [Dev] Supporting blocking calls in Call mediator

[Kathees Rajendram]

Hi,

I have tested the scenarios for security use cases. I am getting the
following issue when test with the blocking and security. Blocking Sender
is not handled the security scenario properly.

[2015-03-05 12:42:36,601] ERROR {org.apache.axis2.engine.AxisEngine} -
Missing wsse:Security header in request
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:277)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: Missing wsse:Security
header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 11 more
[2015-03-05 12:42:36,602] ERROR
{org.apache.synapse.transport.nhttp.ServerWorker} -  Error processing POST
request
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:277)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: Missing wsse:Security
header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 11 more

Thanks,
Kathees

On Wed, Mar 4, 2015 at 9:38 AM, Kathees Rajendram kath...@wso2.com wrote:

 Hi Isuru,

 Ok, I will test the scenarios for security use cases.

 Thanks,
 Kathees

 On Tue, Mar 3, 2015 at 8:57 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Kathees,

 Please include test scenarios for Security use cases as well.

 Thank you.

 On Tue, Mar 3, 2015 at 12:05 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi Isuru,

 I have tested the core functionality of blocking and non blocking.
 Please find the test plan and some test results.



 Test No

 Test

 Configuration

 Expected result

 Observed results

 Status

 Functional Testing





 1

 Direct endpoint without blocking


 call blocking=”false”endpoint name=StockQuoteService

address uri=
 http://localhost:9000/services/SimpleStockQuoteService;
 http://localhost:9000/services/SimpleStockQuoteService/

/endpoint

 call

 Receive response

 Received response

 Passed

 2

 Direct endpoint with blocking

 call blocking=”true”endpoint name=StockQuoteService

address uri=
 http://localhost:9000/services/SimpleStockQuoteService;
 http://localhost:9000/services/SimpleStockQuoteService/

/endpoint

 call

 Receive response

 Received response

 Passed

 3

 Indirect endpoint without blocking

 call blocking=”false” endpoint key=StockQuoteService/

/call

 Receive response

 Received response

 Passed

 4

 Indirect endpoint with blocking

 call blocking=”true” endpoint key=StockQuoteService/

/call

 Receive response

 Received response

 Passed

 5

 Test blocking external service invocation during mediation.



 Pending

 6

 Test non blocking when external service invocates during mediation.



 Pending

 7

 Handle mutual SSL when

Re: [Dev] [Suggestion] A Mediator for the attachment

[Kathees Rajendram]

Hi,

Yes we can add in the connector core. If we have in the ESB it would be
better we can reuse in other components. We can create the new mediator or
use enrich mediator to add this attachment functionality. Now the enrich
mediator is used to clone the OMElement based on the
type(Custom,Envelope,Body,Property and Inline). We can add a additional
option in type for the attachment In this case we can extract the
attachment.

Thanks,
Kathees

On Wed, Mar 4, 2015 at 9:35 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Kathees,

 Good Suggestion. If there are valid use cases for ESB we can add this as a
 mediator. Otherwise more suitable to add to connector core.

 On Wed, Mar 4, 2015 at 6:16 PM, Vanjikumaran Sivajothy va...@wso2.com
 wrote:

 Yes indeed,
 How ever these can be added into connector core  and no need to write a
 separate mediator.


 On Wed, Mar 4, 2015 at 12:59 PM, Kathees Rajendram kath...@wso2.com
 wrote:

 Hi,

 Since most of the connectors are having the attachment method, it would
 be better if we have a mediator in ESB for the attachments. Through that
 mediator we can extract the attachment and encode the values The mediator
 can use the fields such as encoding type,no of attachment,so on. The Users
 can use the configuration rather than coding.

 Thanks,
 Kathees

 --
 Kathees
 Software Engineer,
 email: kath...@wso2.com
 mobile: +94772596173




 --
 Sivajothy Vanjikumaran
 *Senior Software Engineer*
 *Integration Technologies Team*
 *WSO2 Inc. http://wso2.com http://wso2.com/*
 *Mobile:(+94)777219209*
 [image: Facebook] https://www.facebook.com/vanjikumaran [image:
 Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]
 http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image:
 Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]
 http://www.slideshare.net/vanjikumaran

 This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may
 have received this communication in error, please reply to the
 sender indicating that fact and delete the copy you received and in
 addition, you should not print, copy, re-transmit, disseminate, or
 otherwise use the information contained in this communication.
 Internet communications cannot be guaranteed to be timely, secure, error
 or virus-free. The sender does not accept liability for any errors
 or omissions




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev