Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Sriskandarajah Suhothayan]

On Fri, Jul 22, 2016 at 12:00 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi,
>
> Please find the meeting notes in [1].  I have following considerations
> regarding the improvements we have discussed.
>
> (1) Even though we have configured to load the email template from
> EventPublisher(analytics side), the placeholder values has to be sent as
> meta data/correlation data/payload data/arbitrary data, since in analytics
> side, the user claim values are not getting from the user store.
> In order to send the placeholder values from IS side, anyway we have to
> load the email template and retrieve the placeholders. So as I have
> understood, for email notifications, it's not needed to use the email
> template loading part in analytics, since it'll be a redundant task. (Refer
> [2])
>

Here we can set the claim values as arbitrary data, and the notification
specific details as the meta, correlation & payload data.
Then we can use the template loading only at the analytics side.


> (2) The email templates has to be changed as follows.
> i) if the value will be provided in an arbitrary data map, the
> placeholder should be with a prefix "arbitrary_"
> (ex:{{arbitrary_givenname}})
>
ii) if the value will be provided in an meta data map, the placeholder
> should be changed as {{...}} (ex:{{givenname}})
>
> No we should not use "arbitrary_" for any cases, its internal information
and the names should not have "arbitrary_" even if its in arbitrary data
map or otherwise.

(3) Only Text OutputMapping Content can be filled from a value in an
> arbitrary data map using prefix "arbitrary_" .  It's not possible to use a
> value of an arbitrary data map, in a Dynamic adapter properties, only a
> value from a meta data/correlation data/payload data map can be used. I
> think that need to be extended to use even an arbitrary value as a dynamic
> adapter property.(Refer [3])
>

@Gobi can you please fix this if that's the case.


>
> (4) The default stream definitions and publisher definitions has to be
> deployed on super tenant as well as other tenants as well. And when a new
> tenant is added, those streams and publishers has to be deployed for that
> particular tenant as well.
>
> We can have a tenant creation handler to do this copying during that
tenant creation time. WDYT?

Really appreciate your ideas/suggestions regarding the above mentioned
> concerns.
>
> [1] Invitation: [Architecture] [Discussion] Improvement to use Siddhi
> str... @ Wed Jul 20, 2016 4:30pm - 5:30pm (IST) (indu...@wso2.com)
>
> [2]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L108
>
> [3]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/EventPublisher.java#L311
>
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255
>
>
>


-- 

*S. Suhothayan*
Associate Director / Architect & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Roshan Wijesena]

Tested below with DB2 and SQL server 2008.

* Basic APIM functionality.
* Alert subscriptions.
* Log analyzer in a multi-tenant environment.

No issues found

[+] Stable - go ahead and release.



On Fri, Jul 22, 2016 at 11:28 AM, Rukshan Premathunga 
wrote:

> Tested analytics and smoke tested APIM on db2, mssql, mysql, mysql5.7,
> oracle, postgre and h2.
>
> No issues found.
>
> [+] - Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 10:48 AM, Thilini Cooray 
> wrote:
>
>> Tested
>>
>>- API import-export
>>- Store Self Sign-up
>>- Store search
>>- Tested main functionalities with MySQL, PostgreSQL and on Windows
>>
>> No issues found.
>>
>> [+] - Stable - go ahead and release
>>
>> Thanks.
>>
>>
>> On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> *WSO2 API Manager 2.0.0-RC4 Released*
>>>
>>> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC4 :
>>>
>>>  Runtime :
>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>>>  Analytics :
>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Chamalee De Silva]

Tested


   - basic API flow
   - SSO with IS 5.2.0 beta2
   - Reverse Proxy with SSO with IS 5.2.0 beta2


and no issues found.


[x] - Stable - Go ahead and release.




On Fri, Jul 22, 2016 at 11:28 AM, Rukshan Premathunga 
wrote:

> Tested analytics and smoke tested APIM on db2, mssql, mysql, mysql5.7,
> oracle, postgre and h2.
>
> No issues found.
>
> [+] - Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 10:48 AM, Thilini Cooray 
> wrote:
>
>> Tested
>>
>>- API import-export
>>- Store Self Sign-up
>>- Store search
>>- Tested main functionalities with MySQL, PostgreSQL and on Windows
>>
>> No issues found.
>>
>> [+] - Stable - go ahead and release
>>
>> Thanks.
>>
>>
>> On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> *WSO2 API Manager 2.0.0-RC4 Released*
>>>
>>> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC4 :
>>>
>>>  Runtime :
>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>>>  Analytics :
>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Indunil Upeksha Rathnayake]

Hi,

Please find the meeting notes in [1].  I have following considerations
regarding the improvements we have discussed.

(1) Even though we have configured to load the email template from
EventPublisher(analytics side), the placeholder values has to be sent as
meta data/correlation data/payload data/arbitrary data, since in analytics
side, the user claim values are not getting from the user store.
In order to send the placeholder values from IS side, anyway we have to
load the email template and retrieve the placeholders. So as I have
understood, for email notifications, it's not needed to use the email
template loading part in analytics, since it'll be a redundant task. (Refer
[2])

(2) The email templates has to be changed as follows.
i) if the value will be provided in an arbitrary data map, the
placeholder should be with a prefix "arbitrary_"
(ex:{{arbitrary_givenname}})
ii) if the value will be provided in an meta data map, the placeholder
should be changed as {{...}} (ex:{{givenname}})

(3) Only Text OutputMapping Content can be filled from a value in an
arbitrary data map using prefix "arbitrary_" .  It's not possible to use a
value of an arbitrary data map, in a Dynamic adapter properties, only a
value from a meta data/correlation data/payload data map can be used. I
think that need to be extended to use even an arbitrary value as a dynamic
adapter property.(Refer [3])

(4) The default stream definitions and publisher definitions has to be
deployed on super tenant as well as other tenants as well. And when a new
tenant is added, those streams and publishers has to be deployed for that
particular tenant as well.

Really appreciate your ideas/suggestions regarding the above mentioned
concerns.

[1] Invitation: [Architecture] [Discussion] Improvement to use Siddhi
str... @ Wed Jul 20, 2016 4:30pm - 5:30pm (IST) (indu...@wso2.com)

[2]
https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L108

[3]
https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/EventPublisher.java#L311

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
Mobile   0772182255
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Move permission.mgt from device.mgt.core and device.mgt.common in carbon-device-mgt?

[Prabath Abeysekera]

Hi Milan,

I believe, we should ideally review the implementation with IS folks and
see if this can be made part of the identity components, so that others in
the platform too can easily discover and re-use the same. Please do talk to
the IS team and check if this is a possibility.

Cheers,
Prabath

On Fri, Jul 22, 2016 at 11:10 AM, Milan Perera  wrote:

> Hi all,
>
> Shall we $subject? Since permission management is not related directly
> with device management, rather it is used to control the access of webapp
> resources, I think its better we create a separate component to cater the
> requirement.
>
> WDYT?
>
> Regards,
>
> --
> *Milan Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
> 
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Rukshan Premathunga]

Tested analytics and smoke tested APIM on db2, mssql, mysql, mysql5.7,
oracle, postgre and h2.

No issues found.

[+] - Stable - go ahead and release

Thanks.

On Fri, Jul 22, 2016 at 10:48 AM, Thilini Cooray  wrote:

> Tested
>
>- API import-export
>- Store Self Sign-up
>- Store search
>- Tested main functionalities with MySQL, PostgreSQL and on Windows
>
> No issues found.
>
> [+] - Stable - go ahead and release
>
> Thanks.
>
>
> On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
> wrote:
>
>> *WSO2 API Manager 2.0.0-RC4 Released*
>>
>> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC4 :
>>
>>  Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>>  Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Move permission.mgt from device.mgt.core and device.mgt.common in carbon-device-mgt?

[Milan Perera]

Hi Prabath,

Sure, I will check with the IS team.

Regards,

On Fri, Jul 22, 2016 at 11:16 AM, Prabath Abeysekera 
wrote:

> Hi Milan,
>
> I believe, we should ideally review the implementation with IS folks and
> see if this can be made part of the identity components, so that others in
> the platform too can easily discover and re-use the same. Please do talk to
> the IS team and check if this is a possibility.
>
> Cheers,
> Prabath
>
> On Fri, Jul 22, 2016 at 11:10 AM, Milan Perera  wrote:
>
>> Hi all,
>>
>> Shall we $subject? Since permission management is not related directly
>> with device management, rather it is used to control the access of webapp
>> resources, I think its better we create a separate component to cater the
>> requirement.
>>
>> WDYT?
>>
>> Regards,
>>
>> --
>> *Milan Perera *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>> Email: mi...@wso2.com  | Web: www.wso2.com
>> 
>> 
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



-- 
*Milan Perera *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com


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

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

[Prakhash Sivakumar]

Sorry :
s/Sohani/Kavith/g

On Fri, Jul 22, 2016 at 11:14 AM, Prakhash Sivakumar 
wrote:

> Hi Sohani,
>
> We couldn't find the security report for this. Please provide that as
> instructed in "Enforcing Security Scanning Before Product Releases"
>
> Thanks
>
>
> On Fri, Jul 22, 2016 at 10:34 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> I have tested the updater tool functionality including the issue reported
>> at [1].
>>
>> My vote is +1
>>
>> [1] https://wso2.org/jira/browse/TOOLS-3436
>>
>> Thanks,
>> Sohani
>>
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, Jul 20, 2016 at 10:07 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hello Devs,
>>>
>>> Please vote for the second release candidate for WSO2 Developer Studio
>>> Kernel 4.2.0.
>>>
>>> P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0 RC2
>>> is available here
>>> 
>>> .
>>>
>>> Source and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
>>> Eclipse RCP based distribution - further reducing the size.
>>>
>>> We have also introduced a web based dashboard for Developer Studio to
>>> enhance user experience.
>>>
>>> Also the XULRunner is embedded to maintain an unbroken user experience
>>> in WSO2 Developer Studio on windows platform - when using web technologies.
>>>
>>> We have also fixed a few bugs.
>>>
>>>  - https://wso2.org/jira/browse/DEVTOOLESB-441
>>>  - https://wso2.org/jira/browse/TOOLS-3423
>>>
>>> For the second release candidate, we have identified and fixed a major
>>> blocker for automatic updater in kernel.
>>>
>>> - https://wso2.org/jira/browse/TOOLS-3436
>>>
>>> Vote will be open for 72 hours or as needed. Please vote as follows.
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>> Thanks,
>>>
>>> *Kavith Lokuhewage*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +94779145123
>>> Linkedin 
>>> Twitter 
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prakhash Sivakumar
> Software Engineer | WSO2 Inc
> Platform Security Team
> Mobile : +94771510080
> Blog : https://medium.com/@PrakhashS
>



-- 
Prakhash Sivakumar
Software Engineer | WSO2 Inc
Platform Security Team
Mobile : +94771510080
Blog : https://medium.com/@PrakhashS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

[Prakhash Sivakumar]

Hi Sohani,

We couldn't find the security report for this. Please provide that as
instructed in "Enforcing Security Scanning Before Product Releases"

Thanks


On Fri, Jul 22, 2016 at 10:34 AM, Sohani Weerasinghe 
wrote:

> Hi All,
>
> I have tested the updater tool functionality including the issue reported
> at [1].
>
> My vote is +1
>
> [1] https://wso2.org/jira/browse/TOOLS-3436
>
> Thanks,
> Sohani
>
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Jul 20, 2016 at 10:07 PM, Kavith Lokuhewage 
> wrote:
>
>> Hello Devs,
>>
>> Please vote for the second release candidate for WSO2 Developer Studio
>> Kernel 4.2.0.
>>
>> P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0 RC2
>> is available here
>> 
>> .
>>
>> Source and Tag Location to be voted upon is available here
>> 
>> .
>>
>> With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
>> Eclipse RCP based distribution - further reducing the size.
>>
>> We have also introduced a web based dashboard for Developer Studio to
>> enhance user experience.
>>
>> Also the XULRunner is embedded to maintain an unbroken user experience in
>> WSO2 Developer Studio on windows platform - when using web technologies.
>>
>> We have also fixed a few bugs.
>>
>>  - https://wso2.org/jira/browse/DEVTOOLESB-441
>>  - https://wso2.org/jira/browse/TOOLS-3423
>>
>> For the second release candidate, we have identified and fixed a major
>> blocker for automatic updater in kernel.
>>
>> - https://wso2.org/jira/browse/TOOLS-3436
>>
>> Vote will be open for 72 hours or as needed. Please vote as follows.
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Prakhash Sivakumar
Software Engineer | WSO2 Inc
Platform Security Team
Mobile : +94771510080
Blog : https://medium.com/@PrakhashS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Disabling carbon-metrics from UUF

[Rasika Perera]

​Hi Isuru & All,
​


> Why do you want to disable Carbon-Metrics?

In UUF, we are creating a creating a dummy product on top of C5 kernel and
installing our carbon-uuf features. Carbon-Metrics dependency was added
since MSF4J recently added it as a dependency. When the pack is starting up
with carbon-metrics the server startup time goes 4-5 seconds. Apparently
Carbon-Metrics is creating a Hikari-Pool at the server startup which is
consuming more time. Hence we need to disable our carbon-metrics.

However when we disabled the carbon-metrics through metrics.yml it should
honor the configuration property right?

Thank you

On Fri, Jul 22, 2016 at 10:32 AM, Isuru Perera  wrote:

> Why do you want to disable Carbon-Metrics?
>
> On Fri, Jul 22, 2016 at 10:30 AM, Prabushi Samarakoon 
> wrote:
>
>> Hi,
>>
>> We are trying to disable carbon-metrics from the product UUF. Even though
>> we set "enabled: false" at UUF_HOME/conf/metrics.yml, it didn't disable
>> carbon-metrics.
>>
>> Is there another way to disable carbon-metrics?
>>
>> Thanks and Regards,
>>
>> --
>> *Prabushi Samarakoon*
>> Software Engineer
>> Mobile: +94715434580
>> Email: prabus...@wso2.com
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90

[image: wso2-signature-general.png] 

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 MSF4J 2.0.0 RC4

[Dulanja Liyanage]

Hi Thusitha,

We couldn't find the security report for this. Please provide that as
instructed in "Enforcing Security Scanning Before Product Releases"

Thanks,
Dulanja

On Fri, Jul 22, 2016 at 1:09 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Devs,
>
> This is the 4th Release Candidate of the WSO2 MSF4J (Microservices
> Framework for Java) 2.0.0.
>
> Please download, test the framework and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> *​Source and binary distribution files:*
> *https://github.com/wso2/msf4j/releases/tag/v2.0.0-rc4
> *
>
> *Maven staging repository:*
> *https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1005
> *
>
> *The tag to be voted upon:*
> *https://github.com/wso2/msf4j/tree/v2.0.0-rc4
> *
>
>
>
> [ ] Broken - Do not release (explain why)
> [ ] Stable  - Go ahead and release
>
> Thank you,
> WSO2 MSF4J Team
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Dulanja Liyanage
Lead, Platform Security Team
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Disabling carbon-metrics from UUF

[Prabushi Samarakoon]

Hi,

Yes. We are trying to disable carbon-metrics at server start.

On Fri, Jul 22, 2016 at 10:32 AM, Isuru Perera  wrote:

> Why do you want to disable Carbon-Metrics?
>
> On Fri, Jul 22, 2016 at 10:30 AM, Prabushi Samarakoon 
> wrote:
>
>> Hi,
>>
>> We are trying to disable carbon-metrics from the product UUF. Even though
>> we set "enabled: false" at UUF_HOME/conf/metrics.yml, it didn't disable
>> carbon-metrics.
>>
>> Is there another way to disable carbon-metrics?
>>
>> Thanks and Regards,
>>
>> --
>> *Prabushi Samarakoon*
>> Software Engineer
>> Mobile: +94715434580
>> Email: prabus...@wso2.com
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
*Prabushi Samarakoon*
Software Engineer
Mobile: +94715434580
Email: prabus...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Thilini Cooray]

Tested

   - API import-export
   - Store Self Sign-up
   - Store search
   - Tested main functionalities with MySQL, PostgreSQL and on Windows

No issues found.

[+] - Stable - go ahead and release

Thanks.


On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
wrote:

> *WSO2 API Manager 2.0.0-RC4 Released*
>
> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC4 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Nirmal Fernando]

Hi Shavantha,

Analytics pack hasn't required any changes from RC3. So, it's the same as
RC3.

On Fri, Jul 22, 2016 at 10:43 AM, Shavantha Weerasinghe 
wrote:

> Hi Abimaran
>
> Is the analytics pack[1] an RC3 or an RC4
>
> [1] https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
>
>
> regards,
>
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
> On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
> wrote:
>
>> *WSO2 API Manager 2.0.0-RC4 Released*
>>
>> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC4 :
>>
>>  Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>>  Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Shavantha Weerasinghe]

Hi Abimaran

Is the analytics pack[1] an RC3 or an RC4

[1] https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3



regards,

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300


On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan 
wrote:

> *WSO2 API Manager 2.0.0-RC4 Released*
>
> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC4 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

[Sohani Weerasinghe]

Hi All,

I have tested the updater tool functionality including the issue reported
at [1].

My vote is +1

[1] https://wso2.org/jira/browse/TOOLS-3436

Thanks,
Sohani

Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Wed, Jul 20, 2016 at 10:07 PM, Kavith Lokuhewage  wrote:

> Hello Devs,
>
> Please vote for the second release candidate for WSO2 Developer Studio
> Kernel 4.2.0.
>
> P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0 RC2
> is available here
> 
> .
>
> Source and Tag Location to be voted upon is available here
> 
> .
>
> With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
> Eclipse RCP based distribution - further reducing the size.
>
> We have also introduced a web based dashboard for Developer Studio to
> enhance user experience.
>
> Also the XULRunner is embedded to maintain an unbroken user experience in
> WSO2 Developer Studio on windows platform - when using web technologies.
>
> We have also fixed a few bugs.
>
>  - https://wso2.org/jira/browse/DEVTOOLESB-441
>  - https://wso2.org/jira/browse/TOOLS-3423
>
> For the second release candidate, we have identified and fixed a major
> blocker for automatic updater in kernel.
>
> - https://wso2.org/jira/browse/TOOLS-3436
>
> Vote will be open for 72 hours or as needed. Please vote as follows.
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Disabling carbon-metrics from UUF

[Isuru Perera]

Why do you want to disable Carbon-Metrics?

On Fri, Jul 22, 2016 at 10:30 AM, Prabushi Samarakoon 
wrote:

> Hi,
>
> We are trying to disable carbon-metrics from the product UUF. Even though
> we set "enabled: false" at UUF_HOME/conf/metrics.yml, it didn't disable
> carbon-metrics.
>
> Is there another way to disable carbon-metrics?
>
> Thanks and Regards,
>
> --
> *Prabushi Samarakoon*
> Software Engineer
> Mobile: +94715434580
> Email: prabus...@wso2.com
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [UUF] Disabling carbon-metrics from UUF

[Prabushi Samarakoon]

Hi,

We are trying to disable carbon-metrics from the product UUF. Even though
we set "enabled: false" at UUF_HOME/conf/metrics.yml, it didn't disable
carbon-metrics.

Is there another way to disable carbon-metrics?

Thanks and Regards,

-- 
*Prabushi Samarakoon*
Software Engineer
Mobile: +94715434580
Email: prabus...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Nuwan Dias]

Yes, testing includes HA deployment.

On Fri, Jul 22, 2016 at 2:53 AM, Vanjikumaran Sivajothy 
wrote:

> is that testing includes, full scaled HA deployment ?
>
> On Thu, Jul 21, 2016 at 2:12 AM, Harsha Kumara  wrote:
>
>> Tested Throttling Levels of Resource Level, API Level, Subscription
>> Level, Application Level in both tenant and super tenant mode. Tested
>> Blocking conditions in both super tenant and tenant mode. Tested custom
>> rules in super tenant mode. Tested creation of throttling policies in admin
>> dashboard and applicability of them. Tested rate limiting and hard level
>> throttling in super tenant and tenant mode. No issue found.
>>
>> [+] Go ahead and release.
>>
>>
>> On Thu, Jul 21, 2016 at 1:23 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>>
>>> [+] Go ahead and release.
>>>
>>> On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva 
>>> wrote:
>>>
 Tested integrating a Third Party Key Manager, for both Super Tenant and
 Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
 were found.

 [+] Go ahead and release.

 On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan <
 abima...@wso2.com> wrote:

>
> *WSO2 API Manager 2.0.0-RC3 Released*
>
> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC3 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Amila De Silva*

 WSO2 Inc.
 mobile :(+94) 775119302


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Harsha Kumara
>> Software Engineer, WSO2 Inc.
>> Mobile: +94775505618
>> Blog:harshcreationz.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vanjikumaran Sivajothy
> *Associate Technical Lead*
> *WSO2 Inc. http://wso2.com *
>  *+1-925-464-6816*
> [image: Facebook]  [image: Twitter]
>  [image: LinkedIn]
>  [image:
> Blogger]  [image: SlideShare]
> 
>
> 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
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet-Modules] Adding G-Reg 5.2.0 puppet deployment scripts

[Imesh Gunaratne]

Hi Thushara,

Great work on preparing G-Reg 5.2.0 puppet module! Will review it and merge.

Please note that today we are planning to start Puppet Modules v2.1.0-RC1
vote. Therefore we would need to wait until that completes to merge this PR.

Thanks

On Thu, Jul 21, 2016 at 9:29 PM, Thushara Ranawaka 
wrote:

> Hi Puppet Devs,
>
> Kindly review and merge the PR[1]. Please find the related JIRA from
> here[2].
>
> [1] - https://github.com/wso2/puppet-modules/pull/78
> [2] - https://wso2.org/jira/browse/PMODULES-7
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.;  
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com *
>
>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nuwan Pallewela]

Hi Chathurika,

We highly appreciate your suggestions to improve the data mapper. As you
said what we should provide as the data mapper is an enhanced mechanism for
data conversion which would be easy for user to do whatever s/he wants. So
I think we should provide those capabilities without blocking user from
using those provided in JavaScript. I believe your suggestions are mainly
came from the knowledge of JAVA and it's nature. But as we are based on JS
it would be misleading the users if we do not provide those functionalities
available in JS.
I do not think we should build a new standard to our data mapper. The
correct way should be moving with the JS standard as we are moving with JS
underline engine. Otherwise what we would be doing is building a mapping
based on JAVA/WSO2 standard using JavaScript language.

WDYT?

Thanks,
Nuwan

On Fri, Jul 22, 2016 at 9:33 AM, Nuwan Pallewela  wrote:

> Hi All,
>
>
> On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando 
> wrote:
>
>> Hi Erandi,
>>
>> Appreciate your feedback on improving the DM. The existing compare
>> operator checks for the equality (==) of the values passed into the
>> operator. If you passed in 2 String values, it will check the equality of
>> strings. If it is integer values, it will check for the equality of integer
>> values.
>>
> Compare operator have 8 different operations. They are,
>
>- equal value (two inputs are equal or not)
>- equal value type (two inputs are equal in both value and type)
>- not equal value (two inputs are not equal or not)
>- not equal value type (two inputs are not equal in both value and
>type)
>- greater than
>- greater than or equal
>- lower than
>- lower than or equal
>
>
>> Are you talking about adding ">" (greater than) and "<" (less than) as
>> new operators?
>>
>> Basically, you can do this kind of operations with a custom function.
>>
>> Please correct me If I understood your suggestion in a different manner.
>>
>> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> Currently the data mapper compares (compare operator) String values for
>>> > (greater than), < (less than). The native javascript too does the same
>>> which is the underlining engine of data mapper.
>>>
>>> Since we are providing data mapper to the user to enhance conversion and
>>> mapping, rather than a graphical UI for javascript itself, it would be
>>> better if we should add UI (ESB tooling) validations for similar scenarios
>>> as $subject.
>>>
>>
>>> WDYT???
>>>
>>>
>>> Best Regards
>>> Erandi
>>>
>>> --
>>> *Chathurika Erandi*
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> m: +94 773337238
>> https://wso2.com 
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nuwan Pallewela]

Hi All,


On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando  wrote:

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

   - equal value (two inputs are equal or not)
   - equal value type (two inputs are equal in both value and type)
   - not equal value (two inputs are not equal or not)
   - not equal value type (two inputs are not equal in both value and type)
   - greater than
   - greater than or equal
   - lower than
   - lower than or equal


> Are you talking about adding ">" (greater than) and "<" (less than) as new
> operators?
>
> Basically, you can do this kind of operations with a custom function.
>
> Please correct me If I understood your suggestion in a different manner.
>
> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> Currently the data mapper compares (compare operator) String values for >
>> (greater than), < (less than). The native javascript too does the same
>> which is the underlining engine of data mapper.
>>
>> Since we are providing data mapper to the user to enhance conversion and
>> mapping, rather than a graphical UI for javascript itself, it would be
>> better if we should add UI (ESB tooling) validations for similar scenarios
>> as $subject.
>>
>
>> WDYT???
>>
>>
>> Best Regards
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Chathurika De Silva]

Hi Chanaka

Thank you for your reply and I am sorry if my earlier mail was confusing.

Currently the compare operator consists of greater than and less than
functions. Usually these operators are used for numeric comparisons. But
when two Strings are given for greater than or less than function, it is
also compared. In native javascript this kind of comparison is doable which
is the underlining language used for the Data Mapper.

My concern is that even-though such a comparison is doable in javascript,
should we ship the data mapper in the exact same manner?

 Since we are providing an enhanced mechanism for data conversion and
mapping and not a graphical UI for javascript through Data Mapper,
shouldn't we add validations where appropriate in scenarios similar to
above to maintain our own standard for the WSO2 Data Mapper?

Thank You
Erandi



On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando  wrote:

> Hi Erandi,
>
> Appreciate your feedback on improving the DM. The existing compare
> operator checks for the equality (==) of the values passed into the
> operator. If you passed in 2 String values, it will check the equality of
> strings. If it is integer values, it will check for the equality of integer
> values.
>
> Are you talking about adding ">" (greater than) and "<" (less than) as new
> operators?
>
> Basically, you can do this kind of operations with a custom function.
>
> Please correct me If I understood your suggestion in a different manner.
>
> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> Currently the data mapper compares (compare operator) String values for >
>> (greater than), < (less than). The native javascript too does the same
>> which is the underlining engine of data mapper.
>>
>> Since we are providing data mapper to the user to enhance conversion and
>> mapping, rather than a graphical UI for javascript itself, it would be
>> better if we should add UI (ESB tooling) validations for similar scenarios
>> as $subject.
>>
>> WDYT???
>>
>>
>> Best Regards
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dashboard Server] Redirect to last requested URL after login

[Dunith Dhanushka]

Thanks Sinthuja for the prompt response!

On Thu, Jul 21, 2016 at 8:35 PM, Sinthuja Ragendran 
wrote:

> Hi Dunith,
>
> On Thu, Jul 21, 2016 at 6:41 PM, Dunith Dhanushka  wrote:
>
>> Hi DS team,
>>
>> I've noticed following behavior with latest carbon-dashboards.
>>
>> 1. Accessed a dashboard using its direct URL.
>> E.g https://localhost:9443/portal/dashboards/esb-analytics
>>
>> 2. If the user is not logged in before, the user will be redirected to
>> the login page.
>>
>> 3. After logging in, the user will be redirected to dashboard listing
>> page. E.g /portal/dashboards
>>
>
>> In this case, the user has to perform an additional action to view the
>> dashboard. IMO, user should be redirected to the referring URL (
>> https://localhost:9443/portal/dashboards/esb-analytics in this case ) after
>> a successful login.
>>
>> Analytics products like ESB and Security has only one dashboard and it is
>> treated as the default dashboard. In a situation like above, user will have
>> the ability to access the dashboard designer mode which is  restricted for
>> normal users.
>>
>> So is it possible to redirect the user to last requested page after
>> login?
>>
>
> This is fixed with this [1].
>
> Anyhow if you want to restrict the design mode from user, then you need to
> do it from the settings. Redirecting directly to the view of the dashboard
> is not completely prohibiting from accessing the design mode, therefore
> this needs to be configured in dashboard settings. Also since these
> settings will be reflected in dashboard.json therefore when you export it
> and use in the CApp.
>
> [1]
> https://github.com/wso2/carbon-dashboards/commit/4245201d150382738adcceeaca033b1cf4f5391a
>
>
> Thanks,
> Sinthuja.
>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Associate Technical Lead
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - *https://medium.com/@dunithd *
>> Twitter - @dunithd 
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


-- 
Regards,

Dunith Dhanushka,
Associate Technical Lead
WSO2 Inc,

Mobile - +94 71 8615744
Blog - *https://medium.com/@dunithd *
Twitter - @dunithd 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EventPublisherConfigurationException at IS 5.2.0 Snapshot Startup

[Dulanja Liyanage]

Also, Kernel Team, I wonder why the correct Windows version cannot be
identified. Mine is a 10 but identified as 8.1. Could we please check on
that?

TID: [-1234] [] [2016-07-22 07:36:38,101]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Windows 8.1 6.3, amd64
TID: [-1234] [] [2016-07-22 07:36:38,105]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
C:\Program Files\Java\jdk1.7.0_80\jre
TID: [-1234] [] [2016-07-22 07:36:38,108]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.7.0_80
TID: [-1234] [] [2016-07-22 07:36:38,110]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 24.80-b11,Oracle Corporation
TID: [-1234] [] [2016-07-22 07:36:38,114]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
D:\packs\WSO2IS~1.0-S\bin\..
TID: [-1234] [] [2016-07-22 07:36:38,116]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
D:\packs\WSO2IS~1.0-S\bin\..\tmp
TID: [-1234] [] [2016-07-22 07:36:38,119]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
dulanja, en-US, Asia/Colombo
TID: [-1234] [] [2016-07-22 07:36:38,233]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
running OS : Windows 8.1 is not a tested Operating System for running WSO2
Carbon


On Fri, Jul 22, 2016 at 7:55 AM, Dulanja Liyanage  wrote:

> Hi All,
>
> Getting the following error at the server startup:
>
> TID: [-1234] [] [2016-07-22 07:37:16,240] ERROR
>
> {org.wso2.carbon.event.publisher.core.EventPublisherDeployer}
>
> - Error, Event Publisher not deployed and in inactive state, Error while
> deleting the Event Publisher : Illegal char <:> at index 2:
> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
> org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException:
> Error while deleting the Event Publisher : Illegal char <:> at index 2:
> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
> at
> org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
> at
> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
> at
> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
> at
> org.wso2.carbon.core.CarbonAxisConfigurator.deployServices(CarbonAxisConfigurator.java:567)
> at
> org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup(DeploymentServerStartupObserver.java:51)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore(CarbonCoreServiceComponent.java:238)
> at
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:185)
> at
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:288)
> 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.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>

[Dev] EventPublisherConfigurationException at IS 5.2.0 Snapshot Startup

[Dulanja Liyanage]

Hi All,

Getting the following error at the server startup:

TID: [-1234] [] [2016-07-22 07:37:16,240] ERROR

{org.wso2.carbon.event.publisher.core.EventPublisherDeployer}

- Error, Event Publisher not deployed and in inactive state, Error while
deleting the Event Publisher : Illegal char <:> at index 2:
/D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException:
Error while deleting the Event Publisher : Illegal char <:> at index 2:
/D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
at
org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
at
org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
at
org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
at
org.wso2.carbon.core.CarbonAxisConfigurator.deployServices(CarbonAxisConfigurator.java:567)
at
org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup(DeploymentServerStartupObserver.java:51)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore(CarbonCoreServiceComponent.java:238)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:185)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:288)
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.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
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.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: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

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Vanjikumaran Sivajothy]

is that testing includes, full scaled HA deployment ?

On Thu, Jul 21, 2016 at 2:12 AM, Harsha Kumara  wrote:

> Tested Throttling Levels of Resource Level, API Level, Subscription Level,
> Application Level in both tenant and super tenant mode. Tested Blocking
> conditions in both super tenant and tenant mode. Tested custom rules in
> super tenant mode. Tested creation of throttling policies in admin
> dashboard and applicability of them. Tested rate limiting and hard level
> throttling in super tenant and tenant mode. No issue found.
>
> [+] Go ahead and release.
>
>
> On Thu, Jul 21, 2016 at 1:23 PM, Abimaran Kugathasan 
> wrote:
>
>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>
>> [+] Go ahead and release.
>>
>> On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva  wrote:
>>
>>> Tested integrating a Third Party Key Manager, for both Super Tenant and
>>> Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
>>> were found.
>>>
>>> [+] Go ahead and release.
>>>
>>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan >> > wrote:
>>>

 *WSO2 API Manager 2.0.0-RC3 Released*

 This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0

 Source & binary distribution files of API Manager 2.0.0-RC3 :

  Runtime :
 https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
  Analytics :
 https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 Please vote as follows.
 [+] Stable - go ahead and release
 [-]  Broken - do not release (please explain why)

 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


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


>>>
>>>
>>> --
>>> *Amila De Silva*
>>>
>>> WSO2 Inc.
>>> mobile :(+94) 775119302
>>>
>>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vanjikumaran Sivajothy
*Associate Technical Lead*
*WSO2 Inc. http://wso2.com *
 *+1-925-464-6816*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]


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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Abimaran Kugathasan]

*WSO2 API Manager 2.0.0-RC4 Released*

This is the 4th Release Candidate of the WSO2 API Manager 2.0.0

Source & binary distribution files of API Manager 2.0.0-RC4 :

 Runtime :
https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
 Analytics :
https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


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

[Dev] [VOTE] Release WSO2 MSF4J 2.0.0 RC4

[Thusitha Thilina Dayaratne]

Hi Devs,

This is the 4th Release Candidate of the WSO2 MSF4J (Microservices
Framework for Java) 2.0.0.

Please download, test the framework and vote. Vote will be open for 72
hours or as needed.
Refer to github readme for guides.

*​Source and binary distribution files:*
*https://github.com/wso2/msf4j/releases/tag/v2.0.0-rc4
*

*Maven staging repository:*
*https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1005
*

*The tag to be voted upon:*
*https://github.com/wso2/msf4j/tree/v2.0.0-rc4
*



[ ] Broken - Do not release (explain why)
[ ] Stable  - Go ahead and release

Thank you,
WSO2 MSF4J Team

-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

Re: [Dev] EMM 2.1.0 DAS integration and Device Monitoring

[Dilan Udara Ariyaratne]

Hi Chamara,

When it comes to EMM Monitoring Dashboard, we are not retrieving data from
DAS.
Instead, we use the data from our product databases themselves as our
current monitoring use-cases only carry the use of snapshot data and not
historical data.

Regards,
Dilan.

*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Thu, Jul 21, 2016 at 6:10 PM, Chamara Ariyarathne 
wrote:

>
>
> On Thu, Jul 21, 2016 at 6:05 PM, Hasunie Adikari  wrote:
>
>> Hi Chamara,
>>
>> Publishing events[1] and Device Monitoring [2] are not related each other.
>> Since Android agent is capable of sending out critical events to WSO2 DAS
>> server,
>>
>
> What is the usage of this in  a real world scenario?
>
>
>
>> There are some configurations to enable in EMM server to publish events
>> in DAS Server. Here [1] Managing Event publishing
>> provides those configurations.
>> [1]
>> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
>> [2]
>> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>>
>>
>>
>> On Thu, Jul 21, 2016 at 5:25 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
>>> each other?
>>>
>>> Are we using the Stream definitions defined in DAS in [2] in the EMM
>>> dashboard in [1]. If so I cannot see the exact mapping of what goes into
>>> DAS and what is available in EMM Dashboard side.
>>>
>>> [1]
>>> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
>>> [2]
>>> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Associate Technical Lead - QA
>>> WSO2 Inc; http://www.wso2.com/
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94713350904
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Associate Technical Lead - QA
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <%2B94772786766>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Puppet-Modules] Adding G-Reg 5.2.0 puppet deployment scripts

[Thushara Ranawaka]

Hi Puppet Devs,

Kindly review and merge the PR[1]. Please find the related JIRA from
here[2].

[1] - https://github.com/wso2/puppet-modules/pull/78
[2] - https://wso2.org/jira/browse/PMODULES-7

-- 
Thanks,
Thushara Kasun Ranawaka
Software Engineer
WSO2 Inc.;  
lean.enterprise.middleware
Mobile : *+94 (0) 773438949*
*thusha...@wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shipping marathon-lb docker image with mesos artifacts

[Imesh Gunaratne]

Indeed! Great work on resolving the session affinity issue and SSL protocol
problem.

Thanks!

On Thu, Jul 21, 2016 at 6:02 PM, Isuru Haththotuwa  wrote:

> Great work Anurudhdha!
>
> On Thu, Jul 21, 2016 at 5:52 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Akila,
>>
>> I have sent PR [1] to fix a issue with their run script. I was able to
>> provide a custom HAPROXY_HEAD template [2] and remove the dependency with
>> their code except for run script.
>>
>> [1] https://github.com/mesosphere/marathon-lb/pull/273
>> [2]
>> https://github.com/wso2/mesos-artifacts/blob/master/common/marathon-lb/docker/templates/HAPROXY_HEAD
>>
>> On Thu, Jul 21, 2016 at 5:46 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Anuruddha,
>>>
>>> Great work in patching Marathon-lb to work with WSO2 products! Ideally
>>> this should be fixed in the upstream project otherwise maintenance will be
>>> a problem. Shall we create a issue in Marathon-lb project and send a PR?
>>>
>>> Thanks.
>>>
>>> On Thu, Jul 21, 2016 at 5:24 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi All,

 By default marathon-lb blocks  TLS 1.0  protocol [1].

> ssl-default-bind-options no-sslv3 no-tlsv10 no-tls-tickets
>
> Since wso2am uses TLS v1.0.0, users are unable to login to api-manager
 publisher ui when sticky sessions are enabled.

 In order to sticky session to work with wso2am and jdk 1.7.*,  we need
 to enable TLS V1.0.0 in marathon_lb template. Also marathon-lb certificate
 should be added to client-trust-store of wso2server.

 As a solution I have created a customized wso2/marathon-lb docker image
 which has pre loaded with a self signed certificate [2]. This certificate
 is added to client trust-store via puppet [3]. In production this
 certificate can be replaced and configure with a proper certificate.

 I have pushed the customized docker image to docker hub
 (wso2/marathon-lb:v1.3.1) and changed wso2-mesos-artifacts to use
 customized image.


 [1] https://github.com/mesosphere/marathon-lb/blob/master/config.py#L56
 [2]
 https://github.com/wso2/mesos-artifacts/tree/master/common/marathon-lb/docker
 [3]
 https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/manifests/import_cert.pp
 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a nurudd...@wso2.com

>>>
>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Nuwan Dias]

Hi,

We need to drop RC3 due to [1]. We'll call for an RC4 soon.

[1] - https://wso2.org/jira/browse/APIMANAGER-5292

Thanks,
NuwanD.

On Thu, Jul 21, 2016 at 2:42 PM, Harsha Kumara  wrote:

> Tested Throttling Levels of Resource Level, API Level, Subscription Level,
> Application Level in both tenant and super tenant mode. Tested Blocking
> conditions in both super tenant and tenant mode. Tested custom rules in
> super tenant mode. Tested creation of throttling policies in admin
> dashboard and applicability of them. Tested rate limiting and hard level
> throttling in super tenant and tenant mode. No issue found.
>
> [+] Go ahead and release.
>
>
> On Thu, Jul 21, 2016 at 1:23 PM, Abimaran Kugathasan 
> wrote:
>
>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>
>> [+] Go ahead and release.
>>
>> On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva  wrote:
>>
>>> Tested integrating a Third Party Key Manager, for both Super Tenant and
>>> Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
>>> were found.
>>>
>>> [+] Go ahead and release.
>>>
>>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan >> > wrote:
>>>

 *WSO2 API Manager 2.0.0-RC3 Released*

 This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0

 Source & binary distribution files of API Manager 2.0.0-RC3 :

  Runtime :
 https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
  Analytics :
 https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 Please vote as follows.
 [+] Stable - go ahead and release
 [-]  Broken - do not release (please explain why)

 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


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


>>>
>>>
>>> --
>>> *Amila De Silva*
>>>
>>> WSO2 Inc.
>>> mobile :(+94) 775119302
>>>
>>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Chanaka Fernando]

Hi Erandi,

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

Are you talking about adding ">" (greater than) and "<" (less than) as new
operators?

Basically, you can do this kind of operations with a custom function.

Please correct me If I understood your suggestion in a different manner.

On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva 
wrote:

> Hi
>
> Currently the data mapper compares (compare operator) String values for >
> (greater than), < (less than). The native javascript too does the same
> which is the underlining engine of data mapper.
>
> Since we are providing data mapper to the user to enhance conversion and
> mapping, rather than a graphical UI for javascript itself, it would be
> better if we should add UI (ESB tooling) validations for similar scenarios
> as $subject.
>
> WDYT???
>
>
> Best Regards
> Erandi
>
> --
> *Chathurika Erandi*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
m: +94 773337238
https://wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dashboard Server] Redirect to last requested URL after login

[Sinthuja Ragendran]

Hi Dunith,

On Thu, Jul 21, 2016 at 6:41 PM, Dunith Dhanushka  wrote:

> Hi DS team,
>
> I've noticed following behavior with latest carbon-dashboards.
>
> 1. Accessed a dashboard using its direct URL.
> E.g https://localhost:9443/portal/dashboards/esb-analytics
>
> 2. If the user is not logged in before, the user will be redirected to the
> login page.
>
> 3. After logging in, the user will be redirected to dashboard listing
> page. E.g /portal/dashboards
>

> In this case, the user has to perform an additional action to view the
> dashboard. IMO, user should be redirected to the referring URL (
> https://localhost:9443/portal/dashboards/esb-analytics in this case ) after
> a successful login.
>
> Analytics products like ESB and Security has only one dashboard and it is
> treated as the default dashboard. In a situation like above, user will have
> the ability to access the dashboard designer mode which is  restricted for
> normal users.
>
> So is it possible to redirect the user to last requested page after login?
>

This is fixed with this [1].

Anyhow if you want to restrict the design mode from user, then you need to
do it from the settings. Redirecting directly to the view of the dashboard
is not completely prohibiting from accessing the design mode, therefore
this needs to be configured in dashboard settings. Also since these
settings will be reflected in dashboard.json therefore when you export it
and use in the CApp.

[1]
https://github.com/wso2/carbon-dashboards/commit/4245201d150382738adcceeaca033b1cf4f5391a


Thanks,
Sinthuja.

>
> --
> Regards,
>
> Dunith Dhanushka,
> Associate Technical Lead
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - *https://medium.com/@dunithd *
> Twitter - @dunithd 
>



-- 
*Sinthuja Rajendran*
Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Add a default theme for gadgets in DS/DAS

[Sachith Withana]

Hi Jerad,

Please find my comments inline.

Thanks,
Sachith

On Wed, Jul 20, 2016 at 10:47 PM, Jerad Rutnam  wrote:

> Hi Sachith,
>
> This concern was raised and we are trying to figure it out a way to apply
> styling on demand to gadgets, perhaps by using a config. But right now with
> shindig limitations it is not possible.
>
> But IMO this is a feature for advance developers who creates gadgets from
> the scratch. Which is not the primary use case. Developers who create
> custom gadgets from the scratch should apply necessary custom styling to
> the gadgets that they develop. Because Dashboard Server already have a
> feature to keep gadget templates and generate gadgets using them. I think
> that covers the primary use case for the end user.
>

In the DS only scenarios yes, you might not need to use custom gadgets
often.
But in analytics scenarios, it's almost always the case to use custom
gadgets. And it is not a advanced developer scenario IMHO because we do not
create everything from the scratch. What we do is take a generic gadget and
change the internals(queries, pre-processing, handling pubsubs ...etc).

In that case, what I would propose is to have is a generic gadget which
would pull the styling from the styling from the pack itself. Why I bought
this up is, since the current gadgets have their own styling, when we
change the packs, it stands out and IMO it should not be the case.

That generic gadget would be the extension point to all the other custom
gadgets and it would retain backward/forward compatibility since it does
not have to worry about the styling. I feel that it's doable.

Having this would considerably speed up the visualization development of
analytics for sure.

I do agree with you on the point that, if someone creates a gadget from the
scratch, the developer needs to worry about the styling ( not the ideal
case though).



Cheers!

>
> On Fri, Jul 15, 2016 at 7:59 PM, Chamila De Alwis 
> wrote:
>
>>
>> On Fri, Jul 15, 2016 at 9:25 AM, Sachith Withana 
>> wrote:
>>
>>> We do write a lot of custom gadgets in analytics. Is there a way to
>>> incorporate the solution above to those as well? So that devs writing
>>> custom gadgets don't have to worry about their theme not syncing with other
>>> gadgets (generated/precooked).
>>>
>>
>> +1
>>
>> If styling hasn't been drifted too far in the custom gadgets, this should
>> be the case IMO.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> *Jerad Rutnam*
> *Software Engineer*
>
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>
> 
>



-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EMM 2.1.0 DAS integration and Device Monitoring

[Hasunie Adikari]

Hi Chamara,

Publishing events[1] and Device Monitoring [2] are not related each other.
Since Android agent is capable of sending out critical events to WSO2 DAS
server, There are some configurations to enable in EMM server to publish
events in DAS Server. Here [1] Managing Event publishing
provides those configurations.
[1]
https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
[2]
https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard



On Thu, Jul 21, 2016 at 5:25 PM, Chamara Ariyarathne 
wrote:

> Hi all,
>
> How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
> each other?
>
> Are we using the Stream definitions defined in DAS in [2] in the EMM
> dashboard in [1]. If so I cannot see the exact mapping of what goes into
> DAS and what is available in EMM Dashboard side.
>
> [1]
> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
> [2]
> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>
> --
> *Chamara Ariyarathne*
> Associate Technical Lead - QA
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <%2B94772786766>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Hasunie Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
blog http://hasuniea.blogspot.com
Mobile:+94713350904
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Gayan Gunarathne]

On Thu, Jul 21, 2016 at 5:05 PM, Pubudu Gunatilaka  wrote:

> Hi Akila,
>
> What you are saying is correct. We will use apt-get install in SVN docker
> image and get rid of base image. And also I will use the image name as
> wso2/svn:1.0.0 as we can push this to docker hub.
>

Why we use 1.0.0 instead of the SVN version? How we manager SVN different
versions?

>
> Thank you!
>
> On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> True, but this image will not be built regularly right? Once we push to
>> DockerHub users can pull instead of building?
>>
>> Thanks.
>>
>>
>> On Thursday, 21 July 2016, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Akila,

 I used the base image to get rid of running apt-get update again for
 svn docker image. Apt-get update takes time and also sometimes it fails as
 well.

 I have already created Mesos artifacts for svn in [1] and will push
 those changes to Mesos artifact repo. Will work on the Kubernetes 
 artifacts.

>>>
>>> ​May be we can first focus on Mesos artifacts. Will add this to K8S
>>> artifacts later on. Might be better to track it in JIRA.
>>>
>>> Thanks​
>>>
>>>

 [1] -
 https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn

 Thank you!

 On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Pubudu,
>
> Why are we using wso2/wso2base:latest as the base image here? We have
> to run apt-get update and install subversion anyway right?
>
> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
> complete package as well?
>
> Thanks.
>
> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi,
>>
>> At the moment there is no any official docker image for SVN[1]. I
>> have created the dockerfile and other relevant artifacts for SVN [2]. 
>> This
>> is to maintain a separate a docker image for SVN for deployment
>> synchronization. For dep sync in container deployments, there is a mail
>> thread with subject in [3].
>>
>> Basically rsync is an option for dep sync. But when it compares to
>> SVN, the following are the main advantages.
>>
>> - Can handle several manager nodes
>> - SVN Container can accommodate multiple products
>> - We can mount a single volume for SVN server only
>>
>> Please share your thoughts.
>>
>> [1] - https://hub.docker.com/
>> [2] - https://github.com/wso2/dockerfiles/pull/57
>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
>> Kubernetes
>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



 --
 *Pubudu Gunatilaka*
 Committer and PMC Member - Apache Stratos
 Software Engineer
 WSO2, Inc.: http://wso2.com
 mobile : +94774078049 <%2B94772207163>


>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shipping marathon-lb docker image with mesos artifacts

[Anuruddha Liyanarachchi]

Hi Akila,

I have sent PR [1] to fix a issue with their run script. I was able to
provide a custom HAPROXY_HEAD template [2] and remove the dependency with
their code except for run script.

[1] https://github.com/mesosphere/marathon-lb/pull/273
[2]
https://github.com/wso2/mesos-artifacts/blob/master/common/marathon-lb/docker/templates/HAPROXY_HEAD

On Thu, Jul 21, 2016 at 5:46 PM, Akila Ravihansa Perera 
wrote:

> Hi Anuruddha,
>
> Great work in patching Marathon-lb to work with WSO2 products! Ideally
> this should be fixed in the upstream project otherwise maintenance will be
> a problem. Shall we create a issue in Marathon-lb project and send a PR?
>
> Thanks.
>
> On Thu, Jul 21, 2016 at 5:24 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi All,
>>
>> By default marathon-lb blocks  TLS 1.0  protocol [1].
>>
>>> ssl-default-bind-options no-sslv3 no-tlsv10 no-tls-tickets
>>>
>>> Since wso2am uses TLS v1.0.0, users are unable to login to api-manager
>> publisher ui when sticky sessions are enabled.
>>
>> In order to sticky session to work with wso2am and jdk 1.7.*,  we need to
>> enable TLS V1.0.0 in marathon_lb template. Also marathon-lb certificate
>> should be added to client-trust-store of wso2server.
>>
>> As a solution I have created a customized wso2/marathon-lb docker image
>> which has pre loaded with a self signed certificate [2]. This certificate
>> is added to client trust-store via puppet [3]. In production this
>> certificate can be replaced and configure with a proper certificate.
>>
>> I have pushed the customized docker image to docker hub
>> (wso2/marathon-lb:v1.3.1) and changed wso2-mesos-artifacts to use
>> customized image.
>>
>>
>> [1] https://github.com/mesosphere/marathon-lb/blob/master/config.py#L56
>> [2]
>> https://github.com/wso2/mesos-artifacts/tree/master/common/marathon-lb/docker
>> [3]
>> https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/manifests/import_cert.pp
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Dashboard Server] Redirect to last requested URL after login

[Dunith Dhanushka]

Hi DS team,

I've noticed following behavior with latest carbon-dashboards.

1. Accessed a dashboard using its direct URL.
E.g https://localhost:9443/portal/dashboards/esb-analytics

2. If the user is not logged in before, the user will be redirected to the
login page.

3. After logging in, the user will be redirected to dashboard listing page.
E.g /portal/dashboards

In this case, the user has to perform an additional action to view the
dashboard. IMO, user should be redirected to the referring URL (
https://localhost:9443/portal/dashboards/esb-analytics in this case ) after
a successful login.

Analytics products like ESB and Security has only one dashboard and it is
treated as the default dashboard. In a situation like above, user will have
the ability to access the dashboard designer mode which is  restricted for
normal users.

So is it possible to redirect the user to last requested page after login?

-- 
Regards,

Dunith Dhanushka,
Associate Technical Lead
WSO2 Inc,

Mobile - +94 71 8615744
Blog - *https://medium.com/@dunithd *
Twitter - @dunithd 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shipping marathon-lb docker image with mesos artifacts

[Isuru Haththotuwa]

Great work Anurudhdha!

On Thu, Jul 21, 2016 at 5:52 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Akila,
>
> I have sent PR [1] to fix a issue with their run script. I was able to
> provide a custom HAPROXY_HEAD template [2] and remove the dependency with
> their code except for run script.
>
> [1] https://github.com/mesosphere/marathon-lb/pull/273
> [2]
> https://github.com/wso2/mesos-artifacts/blob/master/common/marathon-lb/docker/templates/HAPROXY_HEAD
>
> On Thu, Jul 21, 2016 at 5:46 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Anuruddha,
>>
>> Great work in patching Marathon-lb to work with WSO2 products! Ideally
>> this should be fixed in the upstream project otherwise maintenance will be
>> a problem. Shall we create a issue in Marathon-lb project and send a PR?
>>
>> Thanks.
>>
>> On Thu, Jul 21, 2016 at 5:24 PM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> By default marathon-lb blocks  TLS 1.0  protocol [1].
>>>
 ssl-default-bind-options no-sslv3 no-tlsv10 no-tls-tickets

 Since wso2am uses TLS v1.0.0, users are unable to login to api-manager
>>> publisher ui when sticky sessions are enabled.
>>>
>>> In order to sticky session to work with wso2am and jdk 1.7.*,  we need
>>> to enable TLS V1.0.0 in marathon_lb template. Also marathon-lb certificate
>>> should be added to client-trust-store of wso2server.
>>>
>>> As a solution I have created a customized wso2/marathon-lb docker image
>>> which has pre loaded with a self signed certificate [2]. This certificate
>>> is added to client trust-store via puppet [3]. In production this
>>> certificate can be replaced and configure with a proper certificate.
>>>
>>> I have pushed the customized docker image to docker hub
>>> (wso2/marathon-lb:v1.3.1) and changed wso2-mesos-artifacts to use
>>> customized image.
>>>
>>>
>>> [1] https://github.com/mesosphere/marathon-lb/blob/master/config.py#L56
>>> [2]
>>> https://github.com/wso2/mesos-artifacts/tree/master/common/marathon-lb/docker
>>> [3]
>>> https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/manifests/import_cert.pp
>>> --
>>> *Thanks and Regards,*
>>> Anuruddha Lanka Liyanarachchi
>>> Software Engineer - WSO2
>>> Mobile : +94 (0) 712762611
>>> Tel  : +94 112 145 345
>>> a nurudd...@wso2.com
>>>
>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EMM 2.1.0 DAS integration and Device Monitoring

[Hasunie Adikari]

When managing devices, administrator must be notified of events occurring
on the user's devices that reduce the effectiveness and efficiency of the
tasks performed by a device, so that He can take immediate action and
correct it.
For example, if a cooperate application is utilizing a high CPU or memory
percentage, admin can stop that application from running or un-install and
re-install the application again on the user's device. Like wise those
type of events are published in DAS Server.

On Thu, Jul 21, 2016 at 6:10 PM, Chamara Ariyarathne 
wrote:

>
>
> On Thu, Jul 21, 2016 at 6:05 PM, Hasunie Adikari  wrote:
>
>> Hi Chamara,
>>
>> Publishing events[1] and Device Monitoring [2] are not related each other.
>> Since Android agent is capable of sending out critical events to WSO2 DAS
>> server,
>>
>
> What is the usage of this in  a real world scenario?
>
>
>
>> There are some configurations to enable in EMM server to publish events
>> in DAS Server. Here [1] Managing Event publishing
>> provides those configurations.
>> [1]
>> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
>> [2]
>> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>>
>>
>>
>> On Thu, Jul 21, 2016 at 5:25 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
>>> each other?
>>>
>>> Are we using the Stream definitions defined in DAS in [2] in the EMM
>>> dashboard in [1]. If so I cannot see the exact mapping of what goes into
>>> DAS and what is available in EMM Dashboard side.
>>>
>>> [1]
>>> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
>>> [2]
>>> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Associate Technical Lead - QA
>>> WSO2 Inc; http://www.wso2.com/
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94713350904
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Associate Technical Lead - QA
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <%2B94772786766>*
>



-- 
*Hasunie Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
blog http://hasuniea.blogspot.com
Mobile:+94713350904
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Shipping marathon-lb docker image with mesos artifacts

[Anuruddha Liyanarachchi]

Hi All,

By default marathon-lb blocks  TLS 1.0  protocol [1].

> ssl-default-bind-options no-sslv3 no-tlsv10 no-tls-tickets
>
> Since wso2am uses TLS v1.0.0, users are unable to login to api-manager
publisher ui when sticky sessions are enabled.

In order to sticky session to work with wso2am and jdk 1.7.*,  we need to
enable TLS V1.0.0 in marathon_lb template. Also marathon-lb certificate
should be added to client-trust-store of wso2server.

As a solution I have created a customized wso2/marathon-lb docker image
which has pre loaded with a self signed certificate [2]. This certificate
is added to client trust-store via puppet [3]. In production this
certificate can be replaced and configure with a proper certificate.

I have pushed the customized docker image to docker hub
(wso2/marathon-lb:v1.3.1) and changed wso2-mesos-artifacts to use
customized image.


[1] https://github.com/mesosphere/marathon-lb/blob/master/config.py#L56
[2]
https://github.com/wso2/mesos-artifacts/tree/master/common/marathon-lb/docker
[3]
https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/manifests/import_cert.pp
-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EMM 2.1.0 DAS integration and Device Monitoring

[Chamara Ariyarathne]

On Thu, Jul 21, 2016 at 6:05 PM, Hasunie Adikari  wrote:

> Hi Chamara,
>
> Publishing events[1] and Device Monitoring [2] are not related each other.
> Since Android agent is capable of sending out critical events to WSO2 DAS
> server,
>

What is the usage of this in  a real world scenario?



> There are some configurations to enable in EMM server to publish events in
> DAS Server. Here [1] Managing Event publishing
> provides those configurations.
> [1]
> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
> [2]
> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>
>
>
> On Thu, Jul 21, 2016 at 5:25 PM, Chamara Ariyarathne 
> wrote:
>
>> Hi all,
>>
>> How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
>> each other?
>>
>> Are we using the Stream definitions defined in DAS in [2] in the EMM
>> dashboard in [1]. If so I cannot see the exact mapping of what goes into
>> DAS and what is available in EMM Dashboard side.
>>
>> [1]
>> https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
>> [2]
>> https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard
>>
>> --
>> *Chamara Ariyarathne*
>> Associate Technical Lead - QA
>> WSO2 Inc; http://www.wso2.com/
>> Mobile; *+94772786766 <%2B94772786766>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Hasunie Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> blog http://hasuniea.blogspot.com
> Mobile:+94713350904
>



-- 
*Chamara Ariyarathne*
Associate Technical Lead - QA
WSO2 Inc; http://www.wso2.com/
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Isuru Haththotuwa]

Hi Pubudu,

Good work!

Since we are using apt-get to install svn, there might be some
incompatibility issues when using with deployment synchronizer. AFAIR there
are different svn versions that different Carbon versions support. We might
need to check this and stick to one/few svn version(s) if such issues arise.

On Thu, Jul 21, 2016 at 5:05 PM, Pubudu Gunatilaka  wrote:

> Hi Akila,
>
> What you are saying is correct. We will use apt-get install in SVN docker
> image and get rid of base image. And also I will use the image name as
> wso2/svn:1.0.0 as we can push this to docker hub.
>
> Thank you!
>
> On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> True, but this image will not be built regularly right? Once we push to
>> DockerHub users can pull instead of building?
>>
>> Thanks.
>>
>>
>> On Thursday, 21 July 2016, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Akila,

 I used the base image to get rid of running apt-get update again for
 svn docker image. Apt-get update takes time and also sometimes it fails as
 well.

 I have already created Mesos artifacts for svn in [1] and will push
 those changes to Mesos artifact repo. Will work on the Kubernetes 
 artifacts.

>>>
>>> ​May be we can first focus on Mesos artifacts. Will add this to K8S
>>> artifacts later on. Might be better to track it in JIRA.
>>>
>>> Thanks​
>>>
>>>

 [1] -
 https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn

 Thank you!

 On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Pubudu,
>
> Why are we using wso2/wso2base:latest as the base image here? We have
> to run apt-get update and install subversion anyway right?
>
> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
> complete package as well?
>
> Thanks.
>
> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi,
>>
>> At the moment there is no any official docker image for SVN[1]. I
>> have created the dockerfile and other relevant artifacts for SVN [2]. 
>> This
>> is to maintain a separate a docker image for SVN for deployment
>> synchronization. For dep sync in container deployments, there is a mail
>> thread with subject in [3].
>>
>> Basically rsync is an option for dep sync. But when it compares to
>> SVN, the following are the main advantages.
>>
>> - Can handle several manager nodes
>> - SVN Container can accommodate multiple products
>> - We can mount a single volume for SVN server only
>>
>> Please share your thoughts.
>>
>> [1] - https://hub.docker.com/
>> [2] - https://github.com/wso2/dockerfiles/pull/57
>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
>> Kubernetes
>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



 --
 *Pubudu Gunatilaka*
 Committer and PMC Member - Apache Stratos
 Software Engineer
 WSO2, Inc.: http://wso2.com
 mobile : +94774078049 <%2B94772207163>


>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Pubudu Gunatilaka]

Hi Gayan,

Actually we don't specify any SVN version when installing and we use the
latest in apt-get. When building the docker image, you can specify any
version you want as per [1].

[1] - https://github.com/wso2/dockerfiles/blob/master/svn/README.md

Thank you!

On Thu, Jul 21, 2016 at 5:48 PM, Gayan Gunarathne  wrote:

>
>
> On Thu, Jul 21, 2016 at 5:05 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Akila,
>>
>> What you are saying is correct. We will use apt-get install in SVN docker
>> image and get rid of base image. And also I will use the image name as
>> wso2/svn:1.0.0 as we can push this to docker hub.
>>
>
> Why we use 1.0.0 instead of the SVN version? How we manager SVN different
> versions?
>
>>
>> Thank you!
>>
>> On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> True, but this image will not be built regularly right? Once we push to
>>> DockerHub users can pull instead of building?
>>>
>>> Thanks.
>>>
>>>
>>> On Thursday, 21 July 2016, Imesh Gunaratne  wrote:
>>>


 On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka 
 wrote:

> Hi Akila,
>
> I used the base image to get rid of running apt-get update again for
> svn docker image. Apt-get update takes time and also sometimes it fails as
> well.
>
> I have already created Mesos artifacts for svn in [1] and will push
> those changes to Mesos artifact repo. Will work on the Kubernetes 
> artifacts.
>

 ​May be we can first focus on Mesos artifacts. Will add this to K8S
 artifacts later on. Might be better to track it in JIRA.

 Thanks​


>
> [1] -
> https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn
>
> Thank you!
>
> On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> Why are we using wso2/wso2base:latest as the base image here? We have
>> to run apt-get update and install subversion anyway right?
>>
>> IMHO, we need to add artifacts for deploying this on Mesos,
>> Kubernetes etc. and integrate this with WSO2 DepSync. Shall we work on
>> delivering the complete package as well?
>>
>> Thanks.
>>
>> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka > > wrote:
>>
>>> Hi,
>>>
>>> At the moment there is no any official docker image for SVN[1]. I
>>> have created the dockerfile and other relevant artifacts for SVN [2]. 
>>> This
>>> is to maintain a separate a docker image for SVN for deployment
>>> synchronization. For dep sync in container deployments, there is a mail
>>> thread with subject in [3].
>>>
>>> Basically rsync is an option for dep sync. But when it compares to
>>> SVN, the following are the main advantages.
>>>
>>> - Can handle several manager nodes
>>> - SVN Container can accommodate multiple products
>>> - We can mount a single volume for SVN server only
>>>
>>> Please share your thoughts.
>>>
>>> [1] - https://hub.docker.com/
>>> [2] - https://github.com/wso2/dockerfiles/pull/57
>>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
>>> Kubernetes
>>>
>>> Thank you!
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


 --
 *Imesh Gunaratne*
 Software Architect
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: https://medium.com/@imesh TW: @imesh
 lean. enterprise. middleware


>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>



-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.

Re: [Dev] Shipping marathon-lb docker image with mesos artifacts

[Akila Ravihansa Perera]

Hi Anuruddha,

Great work in patching Marathon-lb to work with WSO2 products! Ideally this
should be fixed in the upstream project otherwise maintenance will be a
problem. Shall we create a issue in Marathon-lb project and send a PR?

Thanks.

On Thu, Jul 21, 2016 at 5:24 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi All,
>
> By default marathon-lb blocks  TLS 1.0  protocol [1].
>
>> ssl-default-bind-options no-sslv3 no-tlsv10 no-tls-tickets
>>
>> Since wso2am uses TLS v1.0.0, users are unable to login to api-manager
> publisher ui when sticky sessions are enabled.
>
> In order to sticky session to work with wso2am and jdk 1.7.*,  we need to
> enable TLS V1.0.0 in marathon_lb template. Also marathon-lb certificate
> should be added to client-trust-store of wso2server.
>
> As a solution I have created a customized wso2/marathon-lb docker image
> which has pre loaded with a self signed certificate [2]. This certificate
> is added to client trust-store via puppet [3]. In production this
> certificate can be replaced and configure with a proper certificate.
>
> I have pushed the customized docker image to docker hub
> (wso2/marathon-lb:v1.3.1) and changed wso2-mesos-artifacts to use
> customized image.
>
>
> [1] https://github.com/mesosphere/marathon-lb/blob/master/config.py#L56
> [2]
> https://github.com/wso2/mesos-artifacts/tree/master/common/marathon-lb/docker
> [3]
> https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/manifests/import_cert.pp
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

That time is fine by me.

thanks,

On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I will try using Puppet.
>> It wasn't a problem with log path/pattern, in fact I used the same log
>> path that I used last time. I believe it was a bug from Azure side, please
>> check the attached screenshots.
>> Shall we please have the meeting on Friday?
>>
> +1. How about 2.00 - 3.0.0 PM on Friday?
>
>>
>> thank you,
>>
>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>>> the current progress of the project? Please let us know your preference.
>>>
>>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and horizontal.
> Vertical scaling, also known as scale up and scale down, means increasing
> or decreasing virtual machine (VM) sizes in response to a workload. As I
> explained in one of my previous emails, vertical auto scaling is achieved
> through monitoring rules. We can set it to trigger an alarm when certain
> conditions are met and also as the action we can set up a runbook to scale
> up or down. I could successfully get VMs to scale up and down using this
> feature.
>

 ​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in, where
> the number of VMs is altered depending on the workload. Horizontal scaling
> is achieved through virtual machine scale sets (VMSS). One important thing
> about VMSS is that the VMs included should be of the same size and have 
> the
> same OS image. All the VMs in the scale set are added to the load 
> balancer,
> as a backend pool. Backend pool is a pool of VMs which share the traffic
> coming via the load balancer. We can add auto scale rules, as to when
> additional VMs should be added and removed, based on the conditions. I
> could test some auto scale rules and observed VMs getting added to the
> backend pool. But one problem is that when these VMs getting added, it’s a
> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
> installed and configured.
>

 ​Yes we would need a VM image with required WSO2 product and
 pre-requisites to test this. At WSO2 we use Puppet​

 ​for automating the installation process [1]. With Puppet we can use
 one base VM image and start a VM for any WSO2 product. Puppet does the WSO2
 product installation at the VM startup.

>
> Note: only a limited horizontal scaling features are supported in the
> azure portal yet so I’m using REST API to create and manage auto scaling
> features.
>
>
> *Centralized logging*
>
>
> I was able to get log to Log Analytics using custom logs. I have
> collected logs generated from 2 wso2 application servers. You only have to
> add respective VMs to the Log analytics and set the path where logs are
> located. This feature was under public preview, which might have been one
> reason why it didn’t work last time when I tried.
>

 ​Was the issue with the log file path/pattern?​ Did it work once you
 remove that?

 [1]
 https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment

 ​Thanks​

>
> Thanks,
>
> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please accept my apologies I have messed up names in my last email.
>> I'm not going to be available today due to an unavoidable circumstance so
>> can we please have the meeting on Wednesday? Extremely sorry if it made 
>> any
>> inconvenience. I will update you with a detailed email today for sure.
>>
>> Thanks in advance,
>>
>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you send a detailed updated on the current status? Shall we have
>>> a meeting on Monday to review the progress.
>>>
>>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 About dynamically adding members to the load balancer, I will cross
 check it with auto-scaling. I couldn't look into that from 
 auto-scaling end
 since I couldn't test it yet.

 about monitoring, yes we can do a POC on that.

 thanks,

 On Tue, Jul 12, 2016 a

[Dev] EMM 2.1.0 DAS integration and Device Monitoring

[Chamara Ariyarathne]

Hi all,

How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
each other?

Are we using the Stream definitions defined in DAS in [2] in the EMM
dashboard in [1]. If so I cannot see the exact mapping of what goes into
DAS and what is available in EMM Dashboard side.

[1]
https://docs.wso2.com/display/EMM210/Managing+Event+Publishing+with+WSO2+Data+Analytics+Server
[2]
https://docs.wso2.com/display/EMM210/Monitoring+Devices+via+the+Dashboard

-- 
*Chamara Ariyarathne*
Associate Technical Lead - QA
WSO2 Inc; http://www.wso2.com/
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Okay sure.

thanks,

On Thu, Jul 21, 2016 at 2:14 PM, Imesh Gunaratne  wrote:

>
>
> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I will try using Puppet.
>>
>
> I think its okay to create a VM image with a specific product,
> configurations and prerequisites. We can utilize that time for adding more
> value to Azure related features.
> ​
>
>
>> It wasn't a problem with log path/pattern, in fact I used the same log
>> path that I used last time. I believe it was a bug from Azure side, please
>> check the attached screenshots.
>> Shall we please have the meeting on Friday?
>>
>> ​Right, got it!
> ​
>
>
>> thank you,
>>
>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>>> the current progress of the project? Please let us know your preference.
>>>
>>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and horizontal.
> Vertical scaling, also known as scale up and scale down, means increasing
> or decreasing virtual machine (VM) sizes in response to a workload. As I
> explained in one of my previous emails, vertical auto scaling is achieved
> through monitoring rules. We can set it to trigger an alarm when certain
> conditions are met and also as the action we can set up a runbook to scale
> up or down. I could successfully get VMs to scale up and down using this
> feature.
>

 ​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in, where
> the number of VMs is altered depending on the workload. Horizontal scaling
> is achieved through virtual machine scale sets (VMSS). One important thing
> about VMSS is that the VMs included should be of the same size and have 
> the
> same OS image. All the VMs in the scale set are added to the load 
> balancer,
> as a backend pool. Backend pool is a pool of VMs which share the traffic
> coming via the load balancer. We can add auto scale rules, as to when
> additional VMs should be added and removed, based on the conditions. I
> could test some auto scale rules and observed VMs getting added to the
> backend pool. But one problem is that when these VMs getting added, it’s a
> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
> installed and configured.
>

 ​Yes we would need a VM image with required WSO2 product and
 pre-requisites to test this. At WSO2 we use Puppet​

 ​for automating the installation process [1]. With Puppet we can use
 one base VM image and start a VM for any WSO2 product. Puppet does the WSO2
 product installation at the VM startup.

>
> Note: only a limited horizontal scaling features are supported in the
> azure portal yet so I’m using REST API to create and manage auto scaling
> features.
>
>
> *Centralized logging*
>
>
> I was able to get log to Log Analytics using custom logs. I have
> collected logs generated from 2 wso2 application servers. You only have to
> add respective VMs to the Log analytics and set the path where logs are
> located. This feature was under public preview, which might have been one
> reason why it didn’t work last time when I tried.
>

 ​Was the issue with the log file path/pattern?​ Did it work once you
 remove that?

 [1]
 https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment

 ​Thanks​

>
> Thanks,
>
> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please accept my apologies I have messed up names in my last email.
>> I'm not going to be available today due to an unavoidable circumstance so
>> can we please have the meeting on Wednesday? Extremely sorry if it made 
>> any
>> inconvenience. I will update you with a detailed email today for sure.
>>
>> Thanks in advance,
>>
>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you send a detailed updated on the current status? Shall we have
>>> a meeting on Monday to review the progress.
>>>
>>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 About dynamically adding members to the load balancer, I will cross
 check it with auto-scaling. I couldn't look into that from 
 auto-scaling end
 since I couldn't t

Re: [Dev] Misleading Aggregate Mediator Description

[Praneesha Chandrasiri]

hi Isuru,

This is a kind reminder on the above.

On Tue, Jul 12, 2016 at 6:30 PM, Praneesha Chandrasiri 
wrote:

> hi Isuru,
>
> Could you please review the above description given by Rajeevan, so that I
> can work on [1] to add it to ESB docs.
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-3539
>
> On Wed, Jun 29, 2016 at 7:46 AM, Vimalanathan Rajeevan  > wrote:
>
>> Thanks Isuru for your response.
>>
>> What about the description below?
>>
>> The *Aggregate mediator* implements the Aggregator enterprise
>> integration pattern
>>  and
>> aggregates the *response messages* for messages that were split by the
>> Clone  or Iterate
>>  mediator.
>>
>> Does this explain the full functionality of Aggregate mediator?
>> Appreciate your response on this.
>>
>> Thanks,
>> Rajeevan
>>
>> On Tue, Jun 28, 2016 at 1:48 AM, Isuru Udana  wrote:
>>
>>> Hi Rajeevan,
>>>
>>> On Tue, Jun 28, 2016 at 10:11 AM, Vimalanathan Rajeevan <
>>> rajeev...@wso2.com> wrote:
>>>
 Hi,

 The description[1] is as below,

 The *Aggregate mediator* implements the Aggregator enterprise
 integration pattern
  and
 aggregates the *response messages* for messages that were split by the
 Clone  or Iterate
  mediator and
 sent using the Send
  mediator.

 Doesn't above paragraph mean that Aggregate mediator will aggregate
 messages and send that using a Send mediator even if we don't explicitly
 call Send mediator?
 Also as I believe there are some places we don't even use a Send
 mediator when there is an Aggregate mediator.
 Appreciate your thoughts on this.

>>> Thanks for pointing this, It seems above statement is confusing. And as
>>> you mentioned there are situations where we are not using the send mediator.
>>>
>>> We need a better description which explains the behaviour.
>>>
>>>
 [1] https://docs.wso2.com/display/ESB490/Aggregate+Mediator

 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
 *

>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>>
>>
>>
>>
>> --
>> 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
>>
>>
>
>
> --
> Thanks & Best Regards,
> *Praneesha Chandrasiri*
> *Technical Writer*
> *WSO2 Inc. *
> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
> *E-mail: pranee...@wso2.com *
>
>


-- 
Thanks & Best Regards,
*Praneesha Chandrasiri*
*Technical Writer*
*WSO2 Inc. *
*Mobile: +(94) 718156888*
*E-mail: pranee...@wso2.com *

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

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Pubudu Gunatilaka]

Hi Akila,

What you are saying is correct. We will use apt-get install in SVN docker
image and get rid of base image. And also I will use the image name as
wso2/svn:1.0.0 as we can push this to docker hub.

Thank you!

On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera  wrote:

> Hi Pubudu,
>
> True, but this image will not be built regularly right? Once we push to
> DockerHub users can pull instead of building?
>
> Thanks.
>
>
> On Thursday, 21 July 2016, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Akila,
>>>
>>> I used the base image to get rid of running apt-get update again for svn
>>> docker image. Apt-get update takes time and also sometimes it fails as
>>> well.
>>>
>>> I have already created Mesos artifacts for svn in [1] and will push
>>> those changes to Mesos artifact repo. Will work on the Kubernetes artifacts.
>>>
>>
>> ​May be we can first focus on Mesos artifacts. Will add this to K8S
>> artifacts later on. Might be better to track it in JIRA.
>>
>> Thanks​
>>
>>
>>>
>>> [1] -
>>> https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn
>>>
>>> Thank you!
>>>
>>> On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Pubudu,

 Why are we using wso2/wso2base:latest as the base image here? We have
 to run apt-get update and install subversion anyway right?

 IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
 etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
 complete package as well?

 Thanks.

 On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
 wrote:

> Hi,
>
> At the moment there is no any official docker image for SVN[1]. I have
> created the dockerfile and other relevant artifacts for SVN [2]. This is 
> to
> maintain a separate a docker image for SVN for deployment synchronization.
> For dep sync in container deployments, there is a mail thread with subject
> in [3].
>
> Basically rsync is an option for dep sync. But when it compares to
> SVN, the following are the main advantages.
>
> - Can handle several manager nodes
> - SVN Container can accommodate multiple products
> - We can mount a single volume for SVN server only
>
> Please share your thoughts.
>
> [1] - https://hub.docker.com/
> [2] - https://github.com/wso2/dockerfiles/pull/57
> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
> Kubernetes
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


 --
 Akila Ravihansa Perera
 WSO2 Inc.;  http://wso2.com/

 Blog: http://ravihansa3000.blogspot.com

>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Chathurika De Silva]

Hi

Currently the data mapper compares (compare operator) String values for >
(greater than), < (less than). The native javascript too does the same
which is the underlining engine of data mapper.

Since we are providing data mapper to the user to enhance conversion and
mapping, rather than a graphical UI for javascript itself, it would be
better if we should add UI (ESB tooling) validations for similar scenarios
as $subject.

WDYT???


Best Regards
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Dinusha Senanayaka]

Hi All,

We are closing this vote. Vote hasn't got any -1 votes. We will proceed
with publishing the maven artifacts to nexus and hosting the GA pack.

Regards,
Dinusha.

On Thu, Jul 21, 2016 at 3:53 AM, Dinusha Senanayaka 
wrote:

> Tested with following scenarios and found no issue.
>
> - Throttling
> - JWT generation for different apps
> - Recent apps loading
> - Deleting apps in multiple states
>
> +1
> Stable - Go ahead and release.
>
> Regards,
> Dinusha.
>
> On Thu, Jul 21, 2016 at 1:01 AM, Lahiru Cooray  wrote:
>
>> Tested following Scenarios:
>>
>>- SSO and SLO
>>- App visibility restrictions
>>- Resource level role based restriction
>>- Favourite apps/page functionality
>>- Sorting and searching
>>
>>
>> +1
>> Stable - Go ahead and release.
>>
>>
>> On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray  wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> The distribution is available to download at [1]
>>>
>>> [1] :
>>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>>>
>>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>>
>>> [2] : https://wso2.org/jira/issues/?filter=13104
>>> [3] : https://wso2.org/jira/issues/?filter=13148
>>> [4] :
>>> https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thanks,
>>> App Manager Team
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I will try using Puppet.
> It wasn't a problem with log path/pattern, in fact I used the same log
> path that I used last time. I believe it was a bug from Azure side, please
> check the attached screenshots.
> Shall we please have the meeting on Friday?
>
+1. How about 2.00 - 3.0.0 PM on Friday?

>
> thank you,
>
> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>> the current progress of the project? Please let us know your preference.
>>
>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 *Auto scaling*


 Azure supports two paradigms of auto scaling, vertical and horizontal.
 Vertical scaling, also known as scale up and scale down, means increasing
 or decreasing virtual machine (VM) sizes in response to a workload. As I
 explained in one of my previous emails, vertical auto scaling is achieved
 through monitoring rules. We can set it to trigger an alarm when certain
 conditions are met and also as the action we can set up a runbook to scale
 up or down. I could successfully get VMs to scale up and down using this
 feature.

>>>
>>> ​We would use horizontal scaling in most scenarios.​
>>>
>>>

 Horizontal scaling, also referred to as scale out and scale in, where
 the number of VMs is altered depending on the workload. Horizontal scaling
 is achieved through virtual machine scale sets (VMSS). One important thing
 about VMSS is that the VMs included should be of the same size and have the
 same OS image. All the VMs in the scale set are added to the load balancer,
 as a backend pool. Backend pool is a pool of VMs which share the traffic
 coming via the load balancer. We can add auto scale rules, as to when
 additional VMs should be added and removed, based on the conditions. I
 could test some auto scale rules and observed VMs getting added to the
 backend pool. But one problem is that when these VMs getting added, it’s a
 whole new VM.  I’m trying to add custom made VMs which has a wso2 product
 installed and configured.

>>>
>>> ​Yes we would need a VM image with required WSO2 product and
>>> pre-requisites to test this. At WSO2 we use Puppet​
>>>
>>> ​for automating the installation process [1]. With Puppet we can use one
>>> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
>>> product installation at the VM startup.
>>>

 Note: only a limited horizontal scaling features are supported in the
 azure portal yet so I’m using REST API to create and manage auto scaling
 features.


 *Centralized logging*


 I was able to get log to Log Analytics using custom logs. I have
 collected logs generated from 2 wso2 application servers. You only have to
 add respective VMs to the Log analytics and set the path where logs are
 located. This feature was under public preview, which might have been one
 reason why it didn’t work last time when I tried.

>>>
>>> ​Was the issue with the log file path/pattern?​ Did it work once you
>>> remove that?
>>>
>>> [1]
>>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>>>
>>> ​Thanks​
>>>

 Thanks,

 On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email.
> I'm not going to be available today due to an unavoidable circumstance so
> can we please have the meeting on Wednesday? Extremely sorry if it made 
> any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have
>> a meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling 
>>> end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Imesh,
>
> About centralized logging, I'm trying to get logs to the Log
> Analytics usi

Re: [Dev] WSO2 AS integration with TomEE

[Lakshman Udayakantha]

Hi,

I have already added several samples and now writing test cases for them.
For now I can copy war files from samples/target folders to tomcat web app
folder and run the test. But with the offline discussion I had with KasunG,
this file copying will not going to work in future docker based test
environment.

@DarshanaW
How we are going to cater this situation?

Thanks

On Mon, Jul 18, 2016 at 4:59 PM, Kishanthan Thangarajah  wrote:

>
>
> On Mon, Jul 18, 2016 at 11:55 AM, Lakshman Udayakantha  > wrote:
>
>> Hi,
>>
>> As a part of this we will migrate samples and test cases from AS 5.3.0.
>> There are 45+ samples in AS 5.3.0. As per the offline chat with KasunG, It
>> will exclude axis2 samples from migration. Other JaxWS-RS, JavaEE samples
>> etc. and relevant test cases will be include in new AS.
>>
>
> +1.
>
> These samples will be shipped with AS and we also need to provide the
> similar ant run script / maven to build and deploy them.
>
>
>> Thanks
>>
>> On Fri, Jul 15, 2016 at 10:50 AM, Lakshman Udayakantha <
>> lakshm...@wso2.com> wrote:
>>
>>> [Adding KalpaW]
>>>
>>> On Thu, Jul 14, 2016 at 10:05 PM, Lakshman Udayakantha <
>>> lakshm...@wso2.com> wrote:
>>>
 Pull request is in [1]

 [1] https://github.com/wso2/product-as/pull/351

 Thanks

 On Thu, Jul 14, 2016 at 10:04 PM, Lakshman Udayakantha <
 lakshm...@wso2.com> wrote:

> Hi Carbon Team,
>
> Could you review and merge the pull which is done for the TomEE
> integration? After the offline discussion with KasunG, added a dummy
> runtime as well.
>
> Thanks
>
> On Thu, Jul 14, 2016 at 4:34 PM, KasunG Gajasinghe 
> wrote:
>
>>
>>
>> On Thu, Jul 14, 2016 at 4:27 PM, Lakshman Udayakantha <
>> lakshm...@wso2.com> wrote:
>>
>>> Hi KasunG,
>>>
>>> This was almost done except jaxrs_basic web app not deploying
>>> properly. Got exception [1]. Anyway I checked for the class which says 
>>> CNF
>>> and it was there in classpath.  This jaxrs_basic  web app needs CXF 
>>> runtime
>>> jars and this web app using to demonstrate custom runtime environment
>>> support. Anyhow TomEE already bundling CXF runtime, it seems not
>>> appropriate CXF as a separate runtime. right?.
>>>
>>
>> Yes, that seems to be the case. Since CXF is coming from TomEE, CXF
>> is not needed as a runtime. But, TomEE only packs CXF's jax-rs related
>> libs. We need to ship jax-ws libs as well.
>>
>>
>>> How about creating a separate run time rather than CXF and creating
>>> another web app to test that and bundling current CXF jars in lib 
>>> itself?
>>>
>>> [1]  SEVERE [localhost-startStop-1]
>>> org.apache.catalina.core.StandardContext.listenerStart Exception sending
>>> context initialized event to listener instance of class
>>> org.springframework.web.context.ContextLoaderListener
>>>
>>>  org.springframework.beans.factory.BeanDefinitionStoreException:
>>> Unexpected exception parsing XML document from ServletContext resource
>>> [/WEB-INF/customBeans.xml]; nested exception is
>>> org.springframework.beans.FatalBeanException: Invalid NamespaceHandler
>>> class [org.apache.cxf.jaxrs.spring.NamespaceHandler] for namespace [
>>> http://cxf.apache.org/jaxrs]: problem with handler class file or
>>> dependent class; nested exception is java.lang.NoClassDefFoundError:
>>> org/springframework/beans/factory/xml/NamespaceHandlerSupport
>>>
>>> at
>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:414)
>>>
>>> at
>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
>>>
>>> at
>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
>>>
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181)
>>>
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217)
>>>
>>> at
>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
>>>
>>> at
>>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
>>>
>>> at
>>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
>>>
>>> at
>>> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129)
>>>
>>> at
>>> org.springframework.context.support.AbstractApplicationContext

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Harsha Kumara]

Tested Throttling Levels of Resource Level, API Level, Subscription Level,
Application Level in both tenant and super tenant mode. Tested Blocking
conditions in both super tenant and tenant mode. Tested custom rules in
super tenant mode. Tested creation of throttling policies in admin
dashboard and applicability of them. Tested rate limiting and hard level
throttling in super tenant and tenant mode. No issue found.

[+] Go ahead and release.


On Thu, Jul 21, 2016 at 1:23 PM, Abimaran Kugathasan 
wrote:

> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>
> [+] Go ahead and release.
>
> On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva  wrote:
>
>> Tested integrating a Third Party Key Manager, for both Super Tenant and
>> Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
>> were found.
>>
>> [+] Go ahead and release.
>>
>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
>> wrote:
>>
>>>
>>> *WSO2 API Manager 2.0.0-RC3 Released*
>>>
>>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>>
>>>  Runtime :
>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>>  Analytics :
>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I will try using Puppet.
>

I think its okay to create a VM image with a specific product,
configurations and prerequisites. We can utilize that time for adding more
value to Azure related features.
​


> It wasn't a problem with log path/pattern, in fact I used the same log
> path that I used last time. I believe it was a bug from Azure side, please
> check the attached screenshots.
> Shall we please have the meeting on Friday?
>
> ​Right, got it!
​


> thank you,
>
> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>> the current progress of the project? Please let us know your preference.
>>
>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 *Auto scaling*


 Azure supports two paradigms of auto scaling, vertical and horizontal.
 Vertical scaling, also known as scale up and scale down, means increasing
 or decreasing virtual machine (VM) sizes in response to a workload. As I
 explained in one of my previous emails, vertical auto scaling is achieved
 through monitoring rules. We can set it to trigger an alarm when certain
 conditions are met and also as the action we can set up a runbook to scale
 up or down. I could successfully get VMs to scale up and down using this
 feature.

>>>
>>> ​We would use horizontal scaling in most scenarios.​
>>>
>>>

 Horizontal scaling, also referred to as scale out and scale in, where
 the number of VMs is altered depending on the workload. Horizontal scaling
 is achieved through virtual machine scale sets (VMSS). One important thing
 about VMSS is that the VMs included should be of the same size and have the
 same OS image. All the VMs in the scale set are added to the load balancer,
 as a backend pool. Backend pool is a pool of VMs which share the traffic
 coming via the load balancer. We can add auto scale rules, as to when
 additional VMs should be added and removed, based on the conditions. I
 could test some auto scale rules and observed VMs getting added to the
 backend pool. But one problem is that when these VMs getting added, it’s a
 whole new VM.  I’m trying to add custom made VMs which has a wso2 product
 installed and configured.

>>>
>>> ​Yes we would need a VM image with required WSO2 product and
>>> pre-requisites to test this. At WSO2 we use Puppet​
>>>
>>> ​for automating the installation process [1]. With Puppet we can use one
>>> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
>>> product installation at the VM startup.
>>>

 Note: only a limited horizontal scaling features are supported in the
 azure portal yet so I’m using REST API to create and manage auto scaling
 features.


 *Centralized logging*


 I was able to get log to Log Analytics using custom logs. I have
 collected logs generated from 2 wso2 application servers. You only have to
 add respective VMs to the Log analytics and set the path where logs are
 located. This feature was under public preview, which might have been one
 reason why it didn’t work last time when I tried.

>>>
>>> ​Was the issue with the log file path/pattern?​ Did it work once you
>>> remove that?
>>>
>>> [1]
>>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>>>
>>> ​Thanks​
>>>

 Thanks,

 On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email.
> I'm not going to be available today due to an unavoidable circumstance so
> can we please have the meeting on Wednesday? Extremely sorry if it made 
> any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have
>> a meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling 
>>> end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake <
 osura...@gmail.

Re: [Dev] Fwd: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online data for WSO2 Machine Learner-Samoa Integration

[Mahesh Dananjaya]

Hi All,
I am onto connecting cep streams with samoa streams to data analysis using
samoa framework. To connect samoa with cep siddhi event streams what i we
can do is that try to convert cep streams into samoa streams or else
writing wrpper for samoa for cep  streasm to be used. In both cases i have
to covert siddhi cep streasm into samoa streams. Samoa is using MOA to
analyse data. Moo contains ML framework to analyse stream data. Samoa is
wrapping MOA withsome of its classes.

Samoa streams is based on MOA, Instance and InstanceStreams. Samoa see
streams as a stream of instances [1]. So if we are going to convert cep
events into samoa instances , it will take time. But if we have some
similarity between cep siddhi streams and samoa streasm we can reduce the
time.
1. What is the underlying infrastructure for cep siddhi streasm.?
2. Are there anything as Instances or InstanceStreams kind of implmentation
underlying cep streams?
3. How can i get more underestanding on CEP siddhi streams.

On the other hand i can use my cep siddhi extension and put those events
into event queue and convert them into samoa instances and feed them into
samoa streaming ml topologies. There is another option. In Samoa what they
are basically doing is that wrapping MOA ML framework and write some
classes for build streaming ml topologies. So as the other option i can
wrap samoa moa with my design and use moa ml framework directly. (No need
for Samoa extension). I have building some topologies to streaming data
analysis [2]. Main problem is that lack of documentation. Anyway i had go
through their whole samoa design.thank you.
regards,
Mahesh.

[1]
https://github.com/apache/incubator-samoa/blob/master/samoa-api/src/main/java/org/apache/samoa/streams/clustering/ClusteringStream.java
[2]
https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming

On Mon, Jul 18, 2016 at 11:40 AM, Mahesh Dananjaya <
dananjayamah...@gmail.com> wrote:

> Hi Maheshakya,
> Samoa modules built as topologies that connect streams with the internal
> processors. I have already written some examples to test the ML algorithms
> and samoa analysis topologies. What we need to done is mostly developing a
> wrapper around samoa topologies to connect their input and output streams
> with our cep streams. So i am currently going through their stream
> architecture to connect our streams with their streams. Couple of examples
> exapaining samoa ml topologies and streaming can be found in my git hub
> repo [1]. Samoa using MOA ml algorithms by wrapping them with their
> classes. Initailly i am trying to develop a KMeansClustering analysis with
> cep streams with samoa ml topologies.
> And also i could not find a maven repo for samoa 0.4.0 incubating. So i am
> currently using my local m2 repo's samoa 0..4.0 incubating for my
> dependencies to work. The local one is built by original samoa source.thank
> you.
>
> regards,
> Mahesh.
>
> [1]
> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming
>
>
> On Mon, Jul 18, 2016 at 8:32 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi Mahesh,
>>
>> Can you  please share your samoa project?
>>
>> On Sun, Jul 17, 2016 at 11:19 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>>
>>> -- Forwarded message --
>>> From: Mahesh Dananjaya 
>>> Date: Sun, Jul 17, 2016 at 11:18 AM
>>> Subject: Re: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online
>>> data for WSO2 Machine Learner-Samoa Integration
>>> To: Maheshakya Wijewardena 
>>>
>>>
>>> Hi Maheshakaya,
>>> just need a little help. In Samoa when we want to run a class what is
>>> does it used this commands [1],
>>> 1. bin/samoa storm target/SAMOA-Storm-0.0.1-SNAPSHOT.jar
>>> "ClusteringEvaluation"
>>> 2. bin/samoa storm target/SAMOA-Storm-0.0.1-SNAPSHOT.jar
>>> "PrequentialEvaluation -d /tmp/dump.csv -i 100 -f 10 -l
>>> (classifiers.trees.VerticalHoeffdingTree -p 4) -s
>>> (generators.RandomTreeGenerator -c 2 -o 10 -u 10)"
>>>
>>> what is does is call a class named LocalDoTask [4] and pass this string
>>> as argument.After that that LocalDoTask call the relevent Tasks such as
>>> ClusteringEvaluation or PrequentialEvaluation. [2].
>>>
>>> Now i have add samoa dependencies to my new maven project, where i used
>>> original samoa source to write examples and test then earlier.Now i want to
>>> push them into my new java project with samoa dependencies. I added
>>> dependency and it was built fine. Now i am calling my local DoTask.java [3]
>>> file as same as i did with samoa with,
>>> java -cp target/streaming-1.0-SNAPSHOT.jar
>>> org.gsoc.samoa.streaming.DoTask
>>> "org.gsoc.samoa.streaming.ClusteringEvaluation"
>>> But seems to be i am incorrect in some place.
>>> Error: A JNI error has occurred, please check your installation and try
>>> again
>>> Exception in thread "main" java.lang.NoClassDefFoundErr

Re: [Dev] [VOTE] Release WSO2 MSF4J 2.0.0 RC3

[Thusitha Thilina Dayaratne]

Hi All,

We are calling of the vote due to a blocker[1]. We will fix the issue and
do a RC4 soon
[1] - https://wso2.org/jira/browse/WMS-80

Thanks
Thusitha

On Mon, Jul 18, 2016 at 6:44 AM, Rasika Perera  wrote:

> Hi All,
>
> I have tested MSF4J 2.0.0 RC2 with the following and found no issue.
>
> Correction. It should be MSF4J 2.0.0 RC3.
>
> Thanks
>
> On Sun, Jul 17, 2016 at 11:45 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>> I have tested MSF4J 2.0.0 RC2 with the following and found no issue.
>>
>>- Built and tested a sample for multivalued map of form-params.
>>- Built and tested a sample for responding a JSON String as
>>application/json contentType
>>
>> [x] Stable - go ahead and release
>>
>> Regards,
>> Rasika
>>
>> On Sun, Jul 17, 2016 at 6:39 PM, Ruwan Abeykoon  wrote:
>>
>>> +1
>>>
>>> I tested with a utility project [1] and found no issues.
>>>
>>> [x] Stable - Go ahead and release
>>>
>>> [1]https://github.com/ruwanta/delaying-proxy
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Fri, Jul 15, 2016 at 9:23 AM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the 3rd Release Candidate of the WSO2 MSF4J (Microservices
 Framework for Java) 2.0.0.

 Please download, test the framework and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 *​Source and binary distribution files:*
 *https://github.com/wso2/msf4j/releases/tag/v2.0.0-rc3
 *

 *Maven staging repository:*
 *https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1004
 *

 *The tag to be voted upon:*
 *https://github.com/wso2/msf4j/tree/v2.0.0-rc3
 *



 [ ] Broken - Do not release (explain why)
 [ ] Stable  - Go ahead and release

 Thank you,
 WSO2 MSF4J Team


 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina



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


>>>
>>>
>>> --
>>>
>>> *Ruwan Abeykoon*
>>> *Associate Director/Architect**,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> [image: wso2-signature-general.png] 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> [image: wso2-signature-general.png] 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Abimaran Kugathasan]

Tested Dynamic Endpoint, API Subscription/blocking/resubscription.

[+] Go ahead and release.

On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva  wrote:

> Tested integrating a Third Party Key Manager, for both Super Tenant and
> Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
> were found.
>
> [+] Go ahead and release.
>
> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
> wrote:
>
>>
>> *WSO2 API Manager 2.0.0-RC3 Released*
>>
>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>
>>  Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>  Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Amila De Silva]

Tested integrating a Third Party Key Manager, for both Super Tenant and
Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
were found.

[+] Go ahead and release.

On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
wrote:

>
> *WSO2 API Manager 2.0.0-RC3 Released*
>
> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC3 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev