Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Chathurika De Silva]

Hi Jagath

Thank you, will verify once the fix is given

Best Regards
Erandi

On Fri, Jul 22, 2016 at 7:23 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Chathurika,
>
> This will be solved with the fix which we are going to apply for [1].
> Issue is that Dev Studio calls admin services with additional '/' and it
> will be removed with the fix.
>
> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 6:54 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> A similar issue exists for un-deploying a CAPP and the issue is reported
>> as [1]. Would it be possible for us to get this fixed?
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-642
>>
>> Thank You
>> Erandi
>>
>> On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Awesome. Thanks!
>>>
>>> Cheers,
>>> Pubudu.
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Pubudu,

 We have already fixed this in the latest source and will share a pack
 soon.

 On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan 
 wrote:

> Hello Viraj and DevStudio team,
>
> We have observed the issue logged at [1] while testing ESB tooling
> shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists
> for both p2 repo as well as the pre-packaged Eclipse.
>
> Would it be possible for us to get this fix in with the next ESB pack
> released for testing? Thanks!
>
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-574
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>


 --
 Thank you and Best Regards,
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

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





>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
>
>


-- 
*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] [IS] user info enable updated_at parameter

[Farasath Ahamed]

+ dev

On Sat, Jul 23, 2016 at 1:06 AM, Farasath Ahamed  wrote:

> Hi Yasith,
>
> Can you provide a screenshot of your SP configuration?  Especially the
> claim configuration part of the Service Provider configuration.
> And also what is the Identity Server version you are trying this out with?
>
>
> Thanks,
>
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
> On Fri, Jul 22, 2016 at 4:22 PM, Yasith Lokuge 
> wrote:
>
>> Hi,
>>
>> I need to enable updated_at parameter in user info response.
>>
>> curl -X GET -H "Authorization: Bearer [ACCESS_TOKEN] "
>>
>> "https://52.8.36.61:9443/oauth2/userinfo?schema=openid;
>>
>>
>>
>> {
>>
>>   "phone_number": "919069395249",
>>
>>   “updated_at” : “some timestamp”
>>
>> }
>>
>> Currently I'm receiving only the phone_number parameter. I need to get
>> the updated_at parameter as well.
>> Please let me know the steps I should follow in order to do that.
>>
>> Thank you.
>> --
>> Yasith Lokuge
>>
>> Software Engineer
>> M: +94 7713 53682 | E: yas...@wso2telco.com
>> W: www.yasith.me
>>
>> WSO2.Telco Inc.
>> Level 4,
>> 20, Palm Grove, Colombo 03
>> Sri Lanka.
>> www.wso2telco.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Dashboard Server 2.1.0-M4 Released!

[Nisala Nanayakkara]

WSO2 Dashboard Server 2.1.0-M4 Released!

WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 4. This release comes with the following
bug fixes and features. You can download the distribution from [1].
Bug

   - [UES-971 ] - Gadgets are not
   rendering in tenant mode if the same gadget is not available in
   super-tenant store
   - [UES-972 ] - Advance UI elements
   does not work in chart wizard
   - [UES-973 ] - Remove the title
   bar in the view mode
   - [UES-987 ] - "undefined" color
   domain appears in chart preview in gadget generation wizard
   - [UES-988 ] - Line Chart Preview
   shows an extra incorrect point
   - [UES-989 ] - "Cannot read
   property 'style' of null" when editing User Preferences with Pubsub-2
   enabled

Improvement

   - [UES-974 ] - Make the security
   time-out of shindig to be configurable
   - [UES-985 ] - Treat dashboard
   theme as a personalization and persist within userspace rather than a cookie
   - [UES-994 ] - Shindig Feature to
   expose apis for getting dashboard name and ID

New Feature

   - [UES-991 ] - Multiple views
   support for page based on roles
   - [UES-992 ] - Download the
   dashboard page as pdf
   - [UES-993 ] - Support primitive
   edit operations (moving and delete gadgets) operations in the view mode

Task

   - [UES-968 ] - Move product-ds to
   kernel 4.4.6

Reporting Issues

Issues can be reported through the Public JIRA
 project for WSO2 Dashboard Server.


[1]-
https://github.com/wso2/product-ds/releases/download/v2.1.0-m4/wso2ds-2.1.0-M4.zip



Thanks,

Dashboard Server Team.


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB5] Improving ESB 5 logging

[Chanaka Fernando]

Hi Kasun,

Created a public JIRA[1] to track this improvement. We'll try our best to
incorporate this with ESB 5.0.0.

[1] https://wso2.org/jira/browse/ESBJAVA-4782

On Fri, Jul 22, 2016 at 9:42 PM, Ruwan Abeykoon  wrote:

> Hi All,
> While we are at it, can we add a known(and agreed) context property for
> correlation Id.
>
> e.g. "X-WSO2-CorrelationId" HTTP header(on inbound) -> context-property ->
> X-WSO2-CorrelationId HTTP header(on outbound)
>
> This ID needs to be generated if not received and should be present in all
> the transports (if technically allows)
>
> This will allow us to trace a request across different products.
>
> Cheers,
> Ruwan
>
> On Fri, Jul 22, 2016 at 11:28 AM, Kasun Indrasiri  wrote:
>
>> Hi,
>>
>> We need to improve ESB 5 logging, so that we can easily identify errors
>> and different states.
>>
>> - Timeouts : What timeout applies in a given error condition (global, EP,
>> or socket TO)
>> - Correlate connections, request, callbacks
>> - Add additional information such as endpoint that failed and the target
>> URL.
>> - Use different use cases that we can think of by considering error codes
>>
>> Isuru wrote a great troubleshooting guide for ESB[1]. I think its a good
>> starting point to understand different errors that can occur and our log
>> must reflect the exact reason for a given error condition.
>>
>> Need to do this before ESB 5 GA.
>>
>> [1]
>> http://wso2.com/library/articles/2014/05/wso2-esb-a-guide-to-troubleshoot/
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> 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
>
>


-- 
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

[Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC1

[Pubudu Gunatilaka]

Hi Devs,

This is the first release candidate (RC1) of WSO2 Puppet Modules 2.1.0
release. Please download, verify, and vote. Voting will be open for 72
hours or as needed.

This release fixes following issues:

https://wso2.org/jira/browse/PMODULES-16?filter=13155

​Source and binary distribution files:

https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1

The tag to be voted upon:

https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1

Release verification guide:

https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment

Refer modules README files for more details.

Please vote as follows.

[+] Stable - go ahead and release

[-]  Broken - do not release (please explain why)

Thank you,
WSO2 PaaS Team.

-- 
*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] Adding YARN configuration files in anlytics4x distributions

[Niranda Perera]

Hi all,

Since the YARN support for DAS, the following config files were added to
the spark server feature. [1]

Please add those files in the relevant bin.xml file in the product
analytic4x distribution to maintain the consistency [2]

Best

[1]
https://github.com/wso2/carbon-analytics/tree/master/features/analytics-processors/org.wso2.carbon.analytics.spark.server.feature/resources/yarn
[2]
https://github.com/wso2/product-das/commit/df328c73ead9ca11b4c3e3c91fbc8c95ea70620b

-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB5] Improving ESB 5 logging

[Ruwan Abeykoon]

Hi All,
While we are at it, can we add a known(and agreed) context property for
correlation Id.

e.g. "X-WSO2-CorrelationId" HTTP header(on inbound) -> context-property ->
X-WSO2-CorrelationId HTTP header(on outbound)

This ID needs to be generated if not received and should be present in all
the transports (if technically allows)

This will allow us to trace a request across different products.

Cheers,
Ruwan

On Fri, Jul 22, 2016 at 11:28 AM, Kasun Indrasiri  wrote:

> Hi,
>
> We need to improve ESB 5 logging, so that we can easily identify errors
> and different states.
>
> - Timeouts : What timeout applies in a given error condition (global, EP,
> or socket TO)
> - Correlate connections, request, callbacks
> - Add additional information such as endpoint that failed and the target
> URL.
> - Use different use cases that we can think of by considering error codes
>
> Isuru wrote a great troubleshooting guide for ESB[1]. I think its a good
> starting point to understand different errors that can occur and our log
> must reflect the exact reason for a given error condition.
>
> Need to do this before ESB 5 GA.
>
> [1]
> http://wso2.com/library/articles/2014/05/wso2-esb-a-guide-to-troubleshoot/
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> 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

[Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Anuruddha Liyanarachchi]

Hi Devs,

This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
release.

*This release fixes the following issues:*

https://wso2.org/jira/issues/?filter=13159

*Tag to be voted upon:*

https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1

*Source and distribution packages:*

https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1

Please download, test, and vote. The README file under the distribution
contains guide and instructions on how to try it out locally.

[+] Stable - Go ahead and release

[-] Broken - Do not release (explain why)



This vote will be open for 72 hours or as needed.

Regards,
WSO2 PaaS team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB5] Improving ESB 5 logging

[Kasun Indrasiri]

Hi,

We need to improve ESB 5 logging, so that we can easily identify errors and
different states.

- Timeouts : What timeout applies in a given error condition (global, EP,
or socket TO)
- Correlate connections, request, callbacks
- Add additional information such as endpoint that failed and the target
URL.
- Use different use cases that we can think of by considering error codes

Isuru wrote a great troubleshooting guide for ESB[1]. I think its a good
starting point to understand different errors that can occur and our log
must reflect the exact reason for a given error condition.

Need to do this before ESB 5 GA.

[1]
http://wso2.com/library/articles/2014/05/wso2-esb-a-guide-to-troubleshoot/

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

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
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.

Cheers,
Sachith

On Thu, Jul 21, 2016 at 10:57 PM, Jerad Rutnam  wrote:

> Hi Sachith,
>
> Please see my comments below,
>
> Cheers!
>
> 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).
>>
>
> I believe above requirement covers by the "Generate Gadget" feature. But
> we need to improve it little more. As we explained in the earlier call,
> this feature needs some user experience improvements. This is just the
> first cut of the feature.
>
> Not exactly, there are customizations that we do which cannot be covered
by the generate gadget feature such as sorting, aggregation, grouping
...etc. These cannot be done at the generate gadget level because it's not
a simple Lucene query. To give you an example, having a subscription to a
dropdown box which would decide which column to group by and do the
aggregation on the given time range.
One reason being that all the rest API calls are not handled at the
generate gadget level + we cannot accommodate dynamic queries at the gadget
creation.
@Dunith might be able to provide some more insight if required.

And I'm always +1 for improvements ;)


>
>> 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.
>>
>
> Correct me if i'm wrong, I believe you are referring to a blank gadget
> which has some basic styling included. If that is, I think we can add a
> blank gadget template without any issue. And +1 for that. That will make
> things more easier for gadget developers.
>

Yes, exactly. It would make it more simple for the gadget developers. But I
would like to raise one concern that we have right now with the current
"generic" gadget.

It does have the styling of the dashboard. But the moment you add a chart
to it (vizGrammar), it chart does not comply with the dashboard styling.
So I don't specifically know if adding a blank gadget would solve the
problem.

>
>
>>
>> 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).
>>
>
> --
> *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] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

[Rajith Vitharana]

Hi Chaminda,

Config level issues I can think of are as follows,
Have you encrypted "username:password" as a whole and provided in [1] or
separately encrypted them and added as colon separated value?
Have you provided same configs for decryption in axis2.xml
vfsTransportListner config? (For example if you use bouncycastle(BC) when
encrypting, then need to provide that for decryption as well)
Have you used a key with larger keystrength for encryption? (for example
2048 key strength). If so there was a issue with that and already fixed
with [2]


[1] - {wso2:vault-decrypt('encryptedValue')}
[2] - https://wso2.org/jira/browse/ESBJAVA-4770

Thanks,

On Fri, Jul 22, 2016 at 2:59 PM, Chaminda Jayawardena 
wrote:

> Hi,
>
> I followed the steps in [1] and getting below exception[2] when proxy
> service is invoked.
> I manually encrypted the username:password using ciphertool.sh and used
> encrypted value in the proxy service as below. And also I could success
> when the same user:pass combination is not encrypted.
> Anything missed here or just a bug ?
>
> * name="transport.vfs.FileURI">smb://{wso2:vault-decrypt('encrypted_user:pass_from_ciphertool')}@localhost/share/test1*
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4679
> [2]
> [2016-07-22 14:48:11,221] ERROR - VFSTransportListener Error checking for
> existence and readability : smb://@localhost/share/test1
> org.apache.commons.vfs2.FileSystemException: Could not determine the type
> of file "smb://localhost/share/test1".
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1523)
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:490)
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.exists(AbstractFileObject.java:478)
> at
> org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:294)
> at
> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:188)
> at
> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:134)
> at
> org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: jcifs.smb.SmbAuthException: Logon failure: unknown user name or
> bad password.
> at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:406)
> at jcifs.smb.SmbSession.send(SmbSession.java:218)
> at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
> at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
> at jcifs.smb.SmbFile.connect(SmbFile.java:954)
> at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
> at jcifs.smb.SmbFile.queryPath(SmbFile.java:1335)
> at jcifs.smb.SmbFile.exists(SmbFile.java:1417)
> at jcifs.smb.SmbFile.isDirectory(SmbFile.java:1490)
> at
> org.apache.commons.vfs2.provider.smb.SmbFileObject.createSmbFile(SmbFileObject.java:119)
> at
> org.apache.commons.vfs2.provider.smb.SmbFileObject.doAttach(SmbFileObject.java:71)
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1506)
> ... 10 more
>
>
>
>
> --
> Thanks & Regards
>
> *Chaminda Jayawardena*
> Senior Software Engineer - QA
> WSO2 Inc. - http://wso2.com
> +94-77-7725234
>



-- 
Rajith Vitharana

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94715883223
Blog : http://lankavitharana.blogspot.com/

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

Re: [Dev] [ESB] DataMapper issue

[Godwin Shrimal]

Jira [1] created.

[1] https://wso2.org/jira/browse/DEVTOOLESB-644


Thanks
Godwin


On Fri, Jul 22, 2016 at 9:07 AM, Viraj Rajaguru  wrote:

> Hi Godwin,
>
> We do not have a Jira for this improvement. Please create a Jira.
>
> Thanks,
> Viraj.
>
> On Tue, Jul 19, 2016 at 7:28 PM, Godwin Shrimal  wrote:
>
>> Hi Viraj,
>>
>> This is not a blocking thing and we can move forward by changing it from
>> the graphical view. But I think we need to figure out the proper way to fix
>> it. Do we have a jira for this already ?
>>
>>
>> Thanks
>> Godwin
>>
>>
>> On Mon, Jul 18, 2016 at 11:47 PM, Viraj Rajaguru  wrote:
>>
>>> Hi Godwin,
>>>
>>> In this use case, JSON schema generator will consider all the datatypes,
>>> but it will get the datatype of the last value of the array. See the below
>>> JSON representation of the XML
>>>
>>> {
>>>"employees":{
>>>   "firstname":"Demo",
>>>   "lastname":"Demo",
>>>   "addresses":{
>>>  "address":[
>>> {
>>>"add1":"No 827/B",
>>>"add2":"Gemunu Mawatha"
>>> },
>>> {
>>>"add1":321,
>>>"add2":"Mount Lavinia"
>>> }
>>>  ]
>>>   }
>>>}
>>> }
>>>
>>> Since the datatype of last "add1" is a NUMBER it will take that for the
>>> JSON schema. Hence we see it in the graphical tree.
>>>
>>> Issue is we have to select one of the datatypes among all the datatypes
>>> for the schema. Currently the convention is to get the last datatype. But
>>> as a fix, we can set high priority to STRING when we have to select one
>>> from multiple datatypes.
>>>
>>> Until we figure out that conventional issue, you can change the datatype
>>> of "add1" from the graphical view. Right click on the "add1" element from
>>> the tree --> Click "Edit Field" and then change the Schema type.
>>>
>>> Thanks,
>>> Viraj.
>>>
>>> On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela 
>>> wrote:
>>>
 Adding Sohani

 On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal 
 wrote:

> Hi All,
>
> When load following xml file in to data mapper (input/output), the
> add1 data type takes as NUMBER as in screenshot . It looks when there is 
> at
> least one record in the array with NUMBER it takes as NUMBER. I think It
> should consider all the values in the array.
>
> 
> Demo
> Demo
>
> 
>   
>   *No 827/B*
> Gemunu Mawatha
>   
>   
> *321*
> Mount Lavinia
>   
> 
> 
>
> [image: Inline image 2]
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



 --
 --

 *Nuwan Chamara Pallewela*


 *Software Engineer*

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

 Email   *nuw...@wso2.com *
 Mobile  *+94719079739 <%2B94719079739>@*



>>>
>>>
>>> --
>>> Viraj Rajaguru
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
*Godwin Amila Shrimal*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

Re: [Dev] [ESB] DataMapper issue

[Viraj Rajaguru]

Hi Godwin,

We do not have a Jira for this improvement. Please create a Jira.

Thanks,
Viraj.

On Tue, Jul 19, 2016 at 7:28 PM, Godwin Shrimal  wrote:

> Hi Viraj,
>
> This is not a blocking thing and we can move forward by changing it from
> the graphical view. But I think we need to figure out the proper way to fix
> it. Do we have a jira for this already ?
>
>
> Thanks
> Godwin
>
>
> On Mon, Jul 18, 2016 at 11:47 PM, Viraj Rajaguru  wrote:
>
>> Hi Godwin,
>>
>> In this use case, JSON schema generator will consider all the datatypes,
>> but it will get the datatype of the last value of the array. See the below
>> JSON representation of the XML
>>
>> {
>>"employees":{
>>   "firstname":"Demo",
>>   "lastname":"Demo",
>>   "addresses":{
>>  "address":[
>> {
>>"add1":"No 827/B",
>>"add2":"Gemunu Mawatha"
>> },
>> {
>>"add1":321,
>>"add2":"Mount Lavinia"
>> }
>>  ]
>>   }
>>}
>> }
>>
>> Since the datatype of last "add1" is a NUMBER it will take that for the
>> JSON schema. Hence we see it in the graphical tree.
>>
>> Issue is we have to select one of the datatypes among all the datatypes
>> for the schema. Currently the convention is to get the last datatype. But
>> as a fix, we can set high priority to STRING when we have to select one
>> from multiple datatypes.
>>
>> Until we figure out that conventional issue, you can change the datatype
>> of "add1" from the graphical view. Right click on the "add1" element from
>> the tree --> Click "Edit Field" and then change the Schema type.
>>
>> Thanks,
>> Viraj.
>>
>> On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela  wrote:
>>
>>> Adding Sohani
>>>
>>> On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal 
>>> wrote:
>>>
 Hi All,

 When load following xml file in to data mapper (input/output), the add1
 data type takes as NUMBER as in screenshot . It looks when there is at
 least one record in the array with NUMBER it takes as NUMBER. I think It
 should consider all the values in the array.

 
 Demo
 Demo

 
   
   *No 827/B*
 Gemunu Mawatha
   
   
 *321*
 Mount Lavinia
   
 
 

 [image: Inline image 2]
 Thanks
 Godwin

 --
 *Godwin Amila Shrimal*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D *
 twitter: https://twitter.com/godwinamila
 

>>>
>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Jagath Sisirakumara Ariyarathne]

Hi Chathurika,

This will be solved with the fix which we are going to apply for [1]. Issue
is that Dev Studio calls admin services with additional '/' and it will be
removed with the fix.

[1] - https://wso2.org/jira/browse/DEVTOOLESB-637

Thanks.

On Fri, Jul 22, 2016 at 6:54 PM, Chathurika De Silva 
wrote:

> Hi
>
> A similar issue exists for un-deploying a CAPP and the issue is reported
> as [1]. Would it be possible for us to get this fixed?
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-642
>
> Thank You
> Erandi
>
> On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan 
> wrote:
>
>> Awesome. Thanks!
>>
>> Cheers,
>> Pubudu.
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> We have already fixed this in the latest source and will share a pack
>>> soon.
>>>
>>> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hello Viraj and DevStudio team,

 We have observed the issue logged at [1] while testing ESB tooling
 shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists
 for both p2 repo as well as the pre-packaged Eclipse.

 Would it be possible for us to get this fix in with the next ESB pack
 released for testing? Thanks!


 [1] https://wso2.org/jira/browse/DEVTOOLESB-574

 Cheers,
 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 Linkedin: https://uk.linkedin.com/in/pubududp
 Medium: https://medium.com/@pubududp


>>>
>>>
>>> --
>>> Thank you and Best Regards,
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>
>
>
> --
> *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
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Chathurika De Silva]

Hi

A similar issue exists for un-deploying a CAPP and the issue is reported as
[1]. Would it be possible for us to get this fixed?

[1] https://wso2.org/jira/browse/DEVTOOLESB-642

Thank You
Erandi

On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan  wrote:

> Awesome. Thanks!
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>
> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando 
> wrote:
>
>> Hi Pubudu,
>>
>> We have already fixed this in the latest source and will share a pack
>> soon.
>>
>> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hello Viraj and DevStudio team,
>>>
>>> We have observed the issue logged at [1] while testing ESB tooling
>>> shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists for
>>> both p2 repo as well as the pre-packaged Eclipse.
>>>
>>> Would it be possible for us to get this fix in with the next ESB pack
>>> released for testing? Thanks!
>>>
>>>
>>> [1] https://wso2.org/jira/browse/DEVTOOLESB-574
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>


-- 
*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] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

I have created the API documentation and hosted in my google drive[1] i
will be preparing code inspection report as well will share it as soon as
well i also added github page also to the userstore script in here[2] as
well
[1] http://googledrive.com/host/0B__ZE1ru1jkXbDVoSDlveV9yNk0
[2] https://asanthamax.github.io/mongodbuserstore/

Thanks,
Asantha

On Tue, Jul 12, 2016 at 11:59 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
> sure we will arrange a hangout on next week and sure i will refer the link
> and do the necessary inspect in my code for any security vulnerabilities
> and update you sooner
>
> Thanks,
> Asantha
>
> On Tue, Jul 12, 2016 at 9:56 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> Thanks for the update. I'm out of the country this week and won't be
>> available. Let's have a hangout next week and discuss the final steps of
>> the project.
>>
>> Along with find bugs, if you haven't enabled findsecuritybugs plugin, you
>> can refer [1] and check if any security weaknesses are there in the code.
>>
>> [1]
>> http://tharindue.blogspot.in/2016/06/static-code-analysis-for-java-using.html
>>
>> Thanks,
>> TharinduE
>>
>> On Tue, Jul 12, 2016 at 5:32 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>> I have clean up the code according to find bug plugin and also for
>>> rollback purposes since it only concern when modifying or adding new user
>>> or role to user store i have manually added rollback option where if error
>>> occured all the changes done to db in code segment will be discard from db
>>> i updated the my repository with recent changes[1] now i preparing the
>>> documentation and test scripts.
>>>
>>> [1] https://github.com/asanthamax/mongodbuserstore
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Jul 4, 2016 at 2:54 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 thanks for the reply ,sure i will try out that and update the progress
 as soon as possible

 Thanks,
 Asantha

 On Mon, Jul 4, 2016 at 1:38 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asantha,
>
> While you are adding the roll back transaction capability, also look
> into testing a high load and try to generate database level exceptions.
> Once thing you can try out is writing a client for performing userstore
> manager operations such as add user, add role, login, logout etc. and play
> it with a high concurrency using Jmeter. Then we should be able to get a
> better understanding of transaction management with respective to MongoDB.
>
> Regards,
> TharinduE
>
> On Mon, Jul 4, 2016 at 10:57 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi all,
>>
>> i will be trying for implement roll back transactions capability in
>> MongoDB to add to MongoDB User Store[2] i found that MongoDB use a 
>> concept
>> call two phase commit[1] i trying to implement that inside my code but it
>> seems to be little complex and i think it may arise performance issue 
>> when
>> adding high load of dataset at once is there any other better method i 
>> can
>> achieve this task? any advices would be grateful
>>
>> [1]
>> https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/
>> [2] https://github.com/asanthamax/mongodbuserstore
>>
>> Thanks,
>> Asantha
>>
>> On Wed, Jun 29, 2016 at 2:55 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I have finished and added delete functions also to users ,roles and
>>> user claim deletions to my repo[1]
>>>
>>> [1] https://github.com/asanthamax/mongodbuserstore
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Jun 27, 2016 at 4:18 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi aiya,

 i have small problem in my research, i will be developing
 convolution neural network using deeplearning4j to detect frauds i have
 discovered some fraud patterns which can use to train my network but 
 the
 problem i having is,are there any possibility to add condition driven
 capability to dataset to train model

 Thanks,
 Asantha

 On Wed, Jun 22, 2016 at 9:35 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Good work Asantha... Meanwhile let's look at getting your research
> work published as well. I will provide feedback for the work so far in
> couple of days time. I have also completed the Mid Review based on 
> your
> current work where you are already ahead of schedule.
>
> Regards,
> TharinduE
>
> On Wed, Jun 22, 2016 at 9:41 PM, Asantha Thilina <

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

[Chathurika De Silva]

Hi Viraj

Thank you for your reply.

Agree with you on a proper graphical representation for a global constant
as it will increase usability.

Best Regards
Erandi

On Fri, Jul 22, 2016 at 5:47 PM, Viraj Rajaguru  wrote:

> Hi Chaturika,
>
> We got your point and we will consider this improvement for a next release
> with a proper graphical representation.
>
> BTW, we are encouraging users to write self contained custom functions as
> much as possible to reduce the complexity. So that its better to define
> constants within the custom function scope. Without having a proper
> graphical representation of the connectivity between a custom function and
> a global constant, facilitating such a feature might lead to a confusion.
>
> We had to introduce global variables concept, since there was no other
> option to achieve some use cases.
>
> Thanks,
> Viraj.
>
> On Fri, Jul 22, 2016 at 5:03 PM, Chathurika De Silva  > wrote:
>
>> Hi ESB Team
>>
>> Currently the constant operator provides just a setting of value and
>> mapping to an output. In the present mapping configuration the constant is
>> not defined as a constant, rather the defined value is assigned directly to
>> the relevant output.
>>
>> If there is a mechanism to define a global constant, this can be reused
>> (e.g. in custom functions) and hence will upgrade the usage of the data
>> mapper as well. I have created [1] for this and hope this will be
>> considered as this will add a greater value.
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-640
>>
>> Thank You
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
*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] [DEV][ESB Tooling] Improvement on constant operator

[Viraj Rajaguru]

Hi Chaturika,

We got your point and we will consider this improvement for a next release
with a proper graphical representation.

BTW, we are encouraging users to write self contained custom functions as
much as possible to reduce the complexity. So that its better to define
constants within the custom function scope. Without having a proper
graphical representation of the connectivity between a custom function and
a global constant, facilitating such a feature might lead to a confusion.

We had to introduce global variables concept, since there was no other
option to achieve some use cases.

Thanks,
Viraj.

On Fri, Jul 22, 2016 at 5:03 PM, Chathurika De Silva 
wrote:

> Hi ESB Team
>
> Currently the constant operator provides just a setting of value and
> mapping to an output. In the present mapping configuration the constant is
> not defined as a constant, rather the defined value is assigned directly to
> the relevant output.
>
> If there is a mechanism to define a global constant, this can be reused
> (e.g. in custom functions) and hence will upgrade the usage of the data
> mapper as well. I have created [1] for this and hope this will be
> considered as this will add a greater value.
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-640
>
> Thank You
> Erandi
>
> --
> *Chathurika Erandi*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC] Installing carbon analytics as a feature

[Sameera Gunarathne]

Hi Gimantha.

sure. I'll give it a try. Thanks

On Fri, Jul 22, 2016 at 5:28 PM, Gimantha Bandara  wrote:

> Hi Sameera,
>
> We bumped the version of carbon-analytics to 1.2.0-SNAPSHOT today and
> still the artifacts may not be available in the nexus repo. Can you please
> try to build the carbon-analytics repo locally and try to add the feature
> and see if it works?
>
> On Fri, Jul 22, 2016 at 5:21 PM, Sameera Gunarathne 
> wrote:
>
>> Hi all,
>>
>> I tried to install analytics features to PC from p2-gen as follows.
>>
>> 
>> org.wso2.carbon.analytics.core.feature.group
>> ${carbon.analytics.version}
>> 
>>
>> I have used 1.2.0-SNAPSHOT as the carbon analytics version. Then the
>> installation fails with the following log.
>>
>> Installation failed.Cannot complete the install because one or more
>> required items could not be found.
>>  Software being installed: WSO2 Carbon - Analytics Core Feature
>> 1.2.0.SNAPSHOT (org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
>>  Missing requirement: WSO2 Carbon - Analytics Data Migration Tool
>> 1.2.0.SNAPSHOT (org.wso2.carbon.analytics.tools.migration 1.2.0.SNAPSHOT)
>> requires 'package me.prettyprint.cassandra.serializers [1.0.0,2.0.0)' but
>> it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Analytics Core Feature 1.2.0.SNAPSHOT
>> (org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
>>   To: org.wso2.carbon.analytics.core.server.feature.group [1.2.0.SNAPSHOT]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Analytics Core Server Feature 1.2.0.SNAPSHOT
>> (org.wso2.carbon.analytics.core.server.feature.group 1.2.0.SNAPSHOT)
>>   To: org.wso2.carbon.analytics.tools.migration [1.2.0.SNAPSHOT]
>>
>>
>> Any help on this would be appreciated.
>>
>> Thanks.
>> Regards
>> --
>> Sameera Gunarathne
>> Software Engineer, WSO2 Inc. http://wso2.com
>> 
>> Email: samee...@wso2.com
>> Mobile: +94714155561
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Gimantha Bandara
> Software Engineer
> WSO2. Inc : http://wso2.com
> Mobile : +94714961919
>



-- 
Sameera Gunarathne
Software Engineer, WSO2 Inc. http://wso2.com

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

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Rasanjaya Subasinghe]

Hi all,

For the new patches we are triggering the service unit file and for
removing the previous pushed patches or lib files in agents, process with
the 'refresh' tag to end up with a clean configuration.

Thanks




On Fri, Jul 22, 2016 at 3:15 PM, Akila Ravihansa Perera 
wrote:

> Hi Rasanjaya,
>
> Yes, but those you mentioned may not be the only case where we need to
> restart the server. If a lib file is copied or removed that will need a
> restart as well. But for some files that may not be needed.
>
> Previously how did you track whether new patches were applied or existing
> patches were removed from Puppet side? Do we have to specify each patch
> number in Puppet manifest or Hiera?
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 2:17 PM, Rasanjaya Subasinghe 
> wrote:
>
>> Hi all,
>>
>> In general, we can use a bash Init file to maintain the wso2 server
>> state, which file is supposed to start, stop and restart the wso2 service
>> based on the configuration change on the master side. We can notify the
>> service unit file, though puppet relationship to restart the service for
>> any template change or new patch.
>>
>> Thanks
>>
>> On Fri, Jul 22, 2016 at 1:24 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>>
 3. Each and every time the config file change [Ex: axis2.xml] product
> gets deleted and start with the fresh configuration.
>

 ​Agree! It should not start from the beginning for a configuration
 change.

>>>
>>> This is now fixed in master branch. Basically Puppet runs in "refresh"
>>> mode by default. It will kill any running WSO2 process before applying
>>> configurations but will use the same pack if it has been already downloaded
>>> from Puppet master. Also it will apply new configurations on top of
>>> previous installation if it exists. You can control this behavior by
>>> setting "wso2::maintenance_mode" Hiera property. If you set it to "new"
>>> then any previous installation will be cleaned first; "zero" will clean the
>>> pack as well.
>>>
>>> However, we still need to improve on how product server is restarted;
>>> i.e. the server should be restarted only if there has been a change applied
>>> to template, patch list is updated, lib files are updated etc. But I don't
>>> think we can reliably detect (from Puppet side) whether server should be
>>> restarted or not. Perhaps a template change may not need a restart. So IMO,
>>> it's better to restart the server on every Puppet run. Any thoughts?
>>>
>>> Thanks.
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> --
>> Rasanjaya Subasinghe
>> Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka)
>> +94772250358
>> rasanj...@wso2.com
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
--
Rasanjaya Subasinghe
Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka)
+94772250358
rasanj...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Event tables in APIM statistics

[Malith Dhanushka]

Hi Rukshan,

Then thats fine use indexing if you are directly querying data from raw
tables( i suppose via gadgets). There is a performance advantage if you use
indexing instead of spark analytics, otherwise it is quite costly in
storage wise. So its better if you use indexing only for required
fields/tables.

Thanks,
Malith

On Fri, Jul 22, 2016 at 5:20 PM, Rukshan Premathunga 
wrote:

> Hi Malith,
>
> Yes in 1.10.0 event table index because we can fetch data from REST API.
> That was the only reason. Also didn't we get any performance improvements
> by indexing those columns?
>
> Thanks and Regards.
>
> On Fri, Jul 22, 2016 at 5:15 PM, Malith Dhanushka  wrote:
>
>> Hi Rukshan,
>>
>> Actually i was referring to APIM toolbox ships with 1.10.0 version. Same
>> thing applies to APIM analytics as well.
>>
>> Thanks,
>> Malith
>>
>> On Fri, Jul 22, 2016 at 5:03 PM, Rukshan Premathunga 
>> wrote:
>>
>>> Hi Malith,
>>>
>>> Some event tables are indexed because if there is a requirement to fetch
>>> data directly from DAS REST API we can used it without any additional
>>> summary tables.
>>>
>>> @Nirmal,
>>> are we using these table to read data directly from REST API other than
>>> summary Tables.
>>>
>>> Thanks and Regards.
>>>
>>> On Fri, Jul 22, 2016 at 3:26 PM, Malith Dhanushka 
>>> wrote:
>>>
 Hi APIM team,

 I noticed that event tables(raw data) in APIM statistics are indexed.
 Is there any particular reason for that?

 Thanks,
 Malith

 --
 Malith Dhanushka
 Senior Software Engineer - Data Technologies
 *WSO2, Inc. : wso2.com *
 *Mobile*  : +94 716 506 693

>>>
>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>>
>>
>>
>>
>> --
>> Malith Dhanushka
>> Senior Software Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com *
>> *Mobile*  : +94 716 506 693
>>
>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>



-- 
Malith Dhanushka
Senior Software Engineer - Data Technologies
*WSO2, Inc. : wso2.com *
*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC] Installing carbon analytics as a feature

[Gimantha Bandara]

Hi Sameera,

We bumped the version of carbon-analytics to 1.2.0-SNAPSHOT today and still
the artifacts may not be available in the nexus repo. Can you please try to
build the carbon-analytics repo locally and try to add the feature and see
if it works?

On Fri, Jul 22, 2016 at 5:21 PM, Sameera Gunarathne 
wrote:

> Hi all,
>
> I tried to install analytics features to PC from p2-gen as follows.
>
> 
> org.wso2.carbon.analytics.core.feature.group
> ${carbon.analytics.version}
> 
>
> I have used 1.2.0-SNAPSHOT as the carbon analytics version. Then the
> installation fails with the following log.
>
> Installation failed.Cannot complete the install because one or more
> required items could not be found.
>  Software being installed: WSO2 Carbon - Analytics Core Feature
> 1.2.0.SNAPSHOT (org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - Analytics Data Migration Tool
> 1.2.0.SNAPSHOT (org.wso2.carbon.analytics.tools.migration 1.2.0.SNAPSHOT)
> requires 'package me.prettyprint.cassandra.serializers [1.0.0,2.0.0)' but
> it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Analytics Core Feature 1.2.0.SNAPSHOT
> (org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
>   To: org.wso2.carbon.analytics.core.server.feature.group [1.2.0.SNAPSHOT]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Analytics Core Server Feature 1.2.0.SNAPSHOT
> (org.wso2.carbon.analytics.core.server.feature.group 1.2.0.SNAPSHOT)
>   To: org.wso2.carbon.analytics.tools.migration [1.2.0.SNAPSHOT]
>
>
> Any help on this would be appreciated.
>
> Thanks.
> Regards
> --
> Sameera Gunarathne
> Software Engineer, WSO2 Inc. http://wso2.com
> 
> Email: samee...@wso2.com
> Mobile: +94714155561
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PC] Installing carbon analytics as a feature

[Sameera Gunarathne]

Hi all,

I tried to install analytics features to PC from p2-gen as follows.


org.wso2.carbon.analytics.core.feature.group
${carbon.analytics.version}


I have used 1.2.0-SNAPSHOT as the carbon analytics version. Then the
installation fails with the following log.

Installation failed.Cannot complete the install because one or more
required items could not be found.
 Software being installed: WSO2 Carbon - Analytics Core Feature
1.2.0.SNAPSHOT (org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
 Missing requirement: WSO2 Carbon - Analytics Data Migration Tool
1.2.0.SNAPSHOT (org.wso2.carbon.analytics.tools.migration 1.2.0.SNAPSHOT)
requires 'package me.prettyprint.cassandra.serializers [1.0.0,2.0.0)' but
it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Analytics Core Feature 1.2.0.SNAPSHOT
(org.wso2.carbon.analytics.core.feature.group 1.2.0.SNAPSHOT)
  To: org.wso2.carbon.analytics.core.server.feature.group [1.2.0.SNAPSHOT]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Analytics Core Server Feature 1.2.0.SNAPSHOT
(org.wso2.carbon.analytics.core.server.feature.group 1.2.0.SNAPSHOT)
  To: org.wso2.carbon.analytics.tools.migration [1.2.0.SNAPSHOT]


Any help on this would be appreciated.

Thanks.
Regards
-- 
Sameera Gunarathne
Software Engineer, WSO2 Inc. http://wso2.com

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

Re: [Dev] Event tables in APIM statistics

[Rukshan Premathunga]

Hi Malith,

Yes in 1.10.0 event table index because we can fetch data from REST API.
That was the only reason. Also didn't we get any performance improvements
by indexing those columns?

Thanks and Regards.

On Fri, Jul 22, 2016 at 5:15 PM, Malith Dhanushka  wrote:

> Hi Rukshan,
>
> Actually i was referring to APIM toolbox ships with 1.10.0 version. Same
> thing applies to APIM analytics as well.
>
> Thanks,
> Malith
>
> On Fri, Jul 22, 2016 at 5:03 PM, Rukshan Premathunga 
> wrote:
>
>> Hi Malith,
>>
>> Some event tables are indexed because if there is a requirement to fetch
>> data directly from DAS REST API we can used it without any additional
>> summary tables.
>>
>> @Nirmal,
>> are we using these table to read data directly from REST API other than
>> summary Tables.
>>
>> Thanks and Regards.
>>
>> On Fri, Jul 22, 2016 at 3:26 PM, Malith Dhanushka 
>> wrote:
>>
>>> Hi APIM team,
>>>
>>> I noticed that event tables(raw data) in APIM statistics are indexed. Is
>>> there any particular reason for that?
>>>
>>> Thanks,
>>> Malith
>>>
>>> --
>>> Malith Dhanushka
>>> Senior Software Engineer - Data Technologies
>>> *WSO2, Inc. : wso2.com *
>>> *Mobile*  : +94 716 506 693
>>>
>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>



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

Re: [Dev] Event tables in APIM statistics

[Malith Dhanushka]

Hi Rukshan,

Actually i was referring to APIM toolbox ships with 1.10.0 version. Same
thing applies to APIM analytics as well.

Thanks,
Malith

On Fri, Jul 22, 2016 at 5:03 PM, Rukshan Premathunga 
wrote:

> Hi Malith,
>
> Some event tables are indexed because if there is a requirement to fetch
> data directly from DAS REST API we can used it without any additional
> summary tables.
>
> @Nirmal,
> are we using these table to read data directly from REST API other than
> summary Tables.
>
> Thanks and Regards.
>
> On Fri, Jul 22, 2016 at 3:26 PM, Malith Dhanushka  wrote:
>
>> Hi APIM team,
>>
>> I noticed that event tables(raw data) in APIM statistics are indexed. Is
>> there any particular reason for that?
>>
>> Thanks,
>> Malith
>>
>> --
>> Malith Dhanushka
>> Senior Software Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com *
>> *Mobile*  : +94 716 506 693
>>
>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>



-- 
Malith Dhanushka
Senior Software Engineer - Data Technologies
*WSO2, Inc. : wso2.com *
*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Event tables in APIM statistics

[Rukshan Premathunga]

Hi Malith,

Some event tables are indexed because if there is a requirement to fetch
data directly from DAS REST API we can used it without any additional
summary tables.

@Nirmal,
are we using these table to read data directly from REST API other than
summary Tables.

Thanks and Regards.

On Fri, Jul 22, 2016 at 3:26 PM, Malith Dhanushka  wrote:

> Hi APIM team,
>
> I noticed that event tables(raw data) in APIM statistics are indexed. Is
> there any particular reason for that?
>
> Thanks,
> Malith
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>



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

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

[Chathurika De Silva]

Hi ESB Team

Currently the constant operator provides just a setting of value and
mapping to an output. In the present mapping configuration the constant is
not defined as a constant, rather the defined value is assigned directly to
the relevant output.

If there is a mechanism to define a global constant, this can be reused
(e.g. in custom functions) and hence will upgrade the usage of the data
mapper as well. I have created [1] for this and hope this will be
considered as this will add a greater value.

[1] https://wso2.org/jira/browse/DEVTOOLESB-640

Thank You
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

[Dev] [PC] Setting permission for all the roles when state transitions take place in life cycles

[Yasima Dewmini]

Hi,

I need to set permission for all the roles including user defined roles,
when state transitions take place in life cycles. How can I achieve this?
And also admin can edit a process when that process is in retired state. I
need to avoid that scenario also.

Any thought regarding this is appreciated.

The life cycle is as follows.




http://www.w3.org/2005/07/scxml;
   version="1.0"
   initialstate="Development">




http://www.wso2.org/projects/registry/actions/get"/>
http://www.wso2.org/projects/registry/actions/add"/>
http://www.wso2.org/projects/registry/actions/delete"/>















http://www.wso2.org/projects/registry/actions/get"/>
http://www.wso2.org/projects/registry/actions/add"/>
http://www.wso2.org/projects/registry/actions/delete"/>


















http://www.wso2.org/projects/registry/actions/get"/>
http://www.wso2.org/projects/registry/actions/add"/>
http://www.wso2.org/projects/registry/actions/delete"/>








http://www.wso2.org/projects/registry/actions/get"/>
http://www.wso2.org/projects/registry/actions/add"/>
http://www.wso2.org/projects/registry/actions/delete"/>























Regards,
Yasima.


-- 
http://wso2.com/signatureYasima Dewmini
Software Engineer, WSO2, Inc.
Email: yas...@wso2.com
Mobile: +94713117081
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Problem when resolving Puppet Master from Agent

[Isuru Perera]

I'm glad to hear that it's fixed in master branch!

Thanks!

On Fri, Jul 22, 2016 at 3:37 PM, Akila Ravihansa Perera 
wrote:

> Hi Isuru,
>
> This was very recently fixed in master branch. Earlier we had a template
> for /etc/hosts which would not only overwrite the entries but also make it
> platform dependent. Now we have switched to Puppet "host" resource type
> which handles platform specific configuration.
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 3:29 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> I recently tried deploying WSO2 IS 5.1.0 using Puppet [1] and I followed
>> the guide in wiki [2].
>>
>> I used two VMs (created by Vagrant) for Master and Agent. When I run the
>> puppet agent, it overwrites the /etc/hosts entry added to Puppet Master
>> [3]. After that the puppet agent fails.
>>
>> Could you please check the guide again?
>>
>> Thanks!
>>
>> Best Regards,
>>
>> [1] https://github.com/wso2/puppet-modules
>> [2]
>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>> [3]
>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment#212-puppet-agent
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.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] [IS] user info enable updated_at parameter

[Yasith Lokuge]

Hi,

I need to enable updated_at parameter in user info response.

curl -X GET -H "Authorization: Bearer [ACCESS_TOKEN] "

"https://52.8.36.61:9443/oauth2/userinfo?schema=openid;



{

  "phone_number": "919069395249",

  “updated_at” : “some timestamp”

}

Currently I'm receiving only the phone_number parameter. I need to get the
updated_at parameter as well.
Please let me know the steps I should follow in order to do that.

Thank you.
-- 
Yasith Lokuge

Software Engineer
M: +94 7713 53682 | E: yas...@wso2telco.com
W: www.yasith.me

WSO2.Telco Inc.
Level 4,
20, Palm Grove, Colombo 03
Sri Lanka.
www.wso2telco.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: Releasing an update for DevS kernel 4.1.0

[Viraj Rajaguru]

-- Forwarded message --
From: Viraj Rajaguru 
Date: Fri, Jul 22, 2016 at 3:46 PM
Subject: Releasing an update for DevS kernel 4.1.0
To: Jasintha Dasanayake , Kavith Lokuhewage <
kav...@wso2.com>, Susinda Perera , Sohani Weerasinghe <
soh...@wso2.com>, Nuwan Pallewela , Chanaka Fernando <
chana...@wso2.com>, Jagath Sisirakumara Ariyarathne 


Hi DevS kernel team,

We faced an issue while deploying CAR files when webContextRoot is enabled
in carbon.xml. See the public Jira[1]. This needs to be fixed in
"devstudio-tooling-platform". Can we have this fix as an update for Kernel
4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
the jira.

BTW, is there any 4.1.0 update branch so that we can send pull requests?

Thanks,
Viraj.

[1] - https://wso2.org/jira/browse/DEVTOOLESB-637
-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068






-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
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

[Abimaran Kugathasan]

Tested Dynamic Endpoint, API Subscription/blocking/resubscription.

[+] Stable - go ahead and release

On Fri, Jul 22, 2016 at 3:10 PM, Malintha Amarasinghe 
wrote:

> Tested with reverse proxy: basic APIM Publisher/Store/Admin UI
> functionalities and Stats
> Tested Publisher/Store and Admin REST APIs
>
> [+] Stable - go ahead and release
>
> On Fri, Jul 22, 2016 at 2:47 PM, Abimaran Kugathasan 
> wrote:
>
>> Please find the P2-Repo here [1]
>>
>>
>> [1] :
>> https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/rc4/
>>
>> On Fri, Jul 22, 2016 at 2:41 PM, Lalaji Sureshika 
>> wrote:
>>
>>> Tested basic APIM flow+token  encryption+ scopes validation+lifecycle
>>> management with multiple api versions in both super tenant and tenant
>>> modes.No issues found.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Tested Distributed Setup with following.

 1. Throttling
 2. Statistics

 [+] Stable - go ahead and release

 Thanks


 On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:

> Tested the workflow extensions with WSO2 BPS for super tenant and
> tenant. Works fine.
>
> [+] Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha <
> uvin...@wso2.com> wrote:
>
>> Tested below with secure vault with custom key store
>>
>> 1. API publication and invocation tenant and super tenant
>> 2. Stats tenant and super tenant(Store and Publisher)
>> 3. Log Analyzer tenant and super tenant
>>
>> No issues found
>>
>> [+] Stable - go ahead and release.
>>
>>
>> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>>
>>> 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 <
>>> ruks...@wso2.com> 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 <
> abima...@wso2.com> 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
> 

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

[Sam Sivayogam]

Tested New API Subscriber Notification and custom rules
[+] Stable - go ahead and release

On Fri, Jul 22, 2016 at 3:34 PM, Abimaran Kugathasan 
wrote:

> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>
> [+] Stable - go ahead and release
>
> On Fri, Jul 22, 2016 at 3:10 PM, Malintha Amarasinghe 
> wrote:
>
>> Tested with reverse proxy: basic APIM Publisher/Store/Admin UI
>> functionalities and Stats
>> Tested Publisher/Store and Admin REST APIs
>>
>> [+] Stable - go ahead and release
>>
>> On Fri, Jul 22, 2016 at 2:47 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Please find the P2-Repo here [1]
>>>
>>>
>>> [1] :
>>> https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/rc4/
>>>
>>> On Fri, Jul 22, 2016 at 2:41 PM, Lalaji Sureshika 
>>> wrote:
>>>
 Tested basic APIM flow+token  encryption+ scopes validation+lifecycle
 management with multiple api versions in both super tenant and tenant
 modes.No issues found.

 [+] Stable - go ahead and release

 On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna <
 tharin...@wso2.com> wrote:

> Tested Distributed Setup with following.
>
> 1. Throttling
> 2. Statistics
>
> [+] Stable - go ahead and release
>
> Thanks
>
>
> On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:
>
>> Tested the workflow extensions with WSO2 BPS for super tenant and
>> tenant. Works fine.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha <
>> uvin...@wso2.com> wrote:
>>
>>> Tested below with secure vault with custom key store
>>>
>>> 1. API publication and invocation tenant and super tenant
>>> 2. Stats tenant and super tenant(Store and Publisher)
>>> 3. Log Analyzer tenant and super tenant
>>>
>>> No issues found
>>>
>>> [+] Stable - go ahead and release.
>>>
>>>
>>> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>>>
 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 <
 ruks...@wso2.com> 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 <
> thili...@wso2.com> 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 <
>> abima...@wso2.com> 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 

Re: [Dev] Problem when resolving Puppet Master from Agent

[Akila Ravihansa Perera]

Hi Isuru,

This was very recently fixed in master branch. Earlier we had a template
for /etc/hosts which would not only overwrite the entries but also make it
platform dependent. Now we have switched to Puppet "host" resource type
which handles platform specific configuration.

Thanks.

On Fri, Jul 22, 2016 at 3:29 PM, Isuru Perera  wrote:

> Hi,
>
> I recently tried deploying WSO2 IS 5.1.0 using Puppet [1] and I followed
> the guide in wiki [2].
>
> I used two VMs (created by Vagrant) for Master and Agent. When I run the
> puppet agent, it overwrites the /etc/hosts entry added to Puppet Master
> [3]. After that the puppet agent fails.
>
> Could you please check the guide again?
>
> Thanks!
>
> Best Regards,
>
> [1] https://github.com/wso2/puppet-modules
> [2]
> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
> [3]
> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment#212-puppet-agent
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
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

[Dev] Problem when resolving Puppet Master from Agent

[Isuru Perera]

Hi,

I recently tried deploying WSO2 IS 5.1.0 using Puppet [1] and I followed
the guide in wiki [2].

I used two VMs (created by Vagrant) for Master and Agent. When I run the
puppet agent, it overwrites the /etc/hosts entry added to Puppet Master
[3]. After that the puppet agent fails.

Could you please check the guide again?

Thanks!

Best Regards,

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

-- 
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] Event tables in APIM statistics

[Malith Dhanushka]

Hi APIM team,

I noticed that event tables(raw data) in APIM statistics are indexed. Is
there any particular reason for that?

Thanks,
Malith

-- 
Malith Dhanushka
Senior Software Engineer - Data Technologies
*WSO2, Inc. : wso2.com *
*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Rasanjaya Subasinghe]

Hi all,

Beneath are some behaviors I was noticed during the LW Dev configuration.

1. Mysql connector needs to copy each and every product.  Anyhow, in cloud
puppet modules we used to place it in wso2base module.

2. A Pupppetmaster host entry gets deleted in /etc/hosts file once we run
the puppet in agent nodes. [Added this IP into hiera common.yaml, due to
resolve the master's IP]

3. Each and every time the config file change [Ex: axis2.xml] product gets
deleted and start with the fresh configuration.

4. In clustering, Is there any reason to use the  sub_domain
[Ex:sub_domain: worker]? In cloud we are not using this anymore.  This used
to identify the manager, worker separation in previous Stratos and now this
will treat through the URL and LB [AWS LB or Nginx]. So then we can specify
this configuration in default.yaml in the relevant product.  No need to
reiterate again and again.

Thanks

On Mon, Jul 18, 2016 at 7:35 PM, Imesh Gunaratne  wrote:

> On Mon, Jul 18, 2016 at 5:44 PM, Manula Waidyanatha 
>  wrote:
>
>
>> What is the reason for checking `@clustering['aws']` in every line in
>> aws.erb[1] file?
>> It doesn't do any harm, but there is no point in checking it since
>> aws.erb file is included to axis2.xml.erb only in the aws clustering
>> mode.
>
>
> ​Thanks for pointing Manula! It was my mistake!​
>
> On Mon, Jul 18, 2016 at 6:05 PM, Lakmal Warusawithana 
> wrote:
>
>> @Imesh, Shall we remove unnecessary if conditions in aws.erb.
>>
>> ​Yes Lakmal! I fixed it and pushed changes. Please see the latest
> template and sample Hiera data config [1], [2]:
>
> [1]
> https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/templates/clustering/aws.erb
> [2]
> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2bps/3.5.1/default/manager.yaml#L36
>
> Thanks
> ​
>
>
>> thanks
>>
>> On Mon, Jul 18, 2016 at 2:39 PM, Imesh Gunaratne  wrote:
>>
>>> I just added AWS membership scheme template and a sample configuration
>>> to BPS 3.5.1 [1].
>>> @Rasanjaya: Would you mind trying this out?
>>>
>>> [1]
>>> https://github.com/wso2/puppet-modules/commit/af14b15d2361f311f6de328141c3ad2cb57428d9
>>>
>>> Thanks
>>>
>>> On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne  wrote:
>>>
 Hi Devs,

 It looks like we have missed $subject:

 https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering

 https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode

 Thanks

 --
 *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


>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.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
>
>


-- 
--
Rasanjaya Subasinghe
Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka)
+94772250358
rasanj...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Srinath Perera]

Hi Mahesh,

On Thu, Jul 21, 2016 at 2:10 PM, Mahesh Dananjaya  wrote:

> 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.
>
I think this is OK. I assume this is much easier. Let's do this and check
the performance.


> 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.
>

If we use MOA directly, would we loose the distributed support in SAOMA.
Let's do a call when you can, so we can dsicuss this in detail.

--Srinath



> 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 

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Akila Ravihansa Perera]

Hi Rasanjaya,

Yes, but those you mentioned may not be the only case where we need to
restart the server. If a lib file is copied or removed that will need a
restart as well. But for some files that may not be needed.

Previously how did you track whether new patches were applied or existing
patches were removed from Puppet side? Do we have to specify each patch
number in Puppet manifest or Hiera?

Thanks.

On Fri, Jul 22, 2016 at 2:17 PM, Rasanjaya Subasinghe 
wrote:

> Hi all,
>
> In general, we can use a bash Init file to maintain the wso2 server state,
> which file is supposed to start, stop and restart the wso2 service based on
> the configuration change on the master side. We can notify the service unit
> file, though puppet relationship to restart the service for any template
> change or new patch.
>
> Thanks
>
> On Fri, Jul 22, 2016 at 1:24 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>>
>>> 3. Each and every time the config file change [Ex: axis2.xml] product
 gets deleted and start with the fresh configuration.

>>>
>>> ​Agree! It should not start from the beginning for a configuration
>>> change.
>>>
>>
>> This is now fixed in master branch. Basically Puppet runs in "refresh"
>> mode by default. It will kill any running WSO2 process before applying
>> configurations but will use the same pack if it has been already downloaded
>> from Puppet master. Also it will apply new configurations on top of
>> previous installation if it exists. You can control this behavior by
>> setting "wso2::maintenance_mode" Hiera property. If you set it to "new"
>> then any previous installation will be cleaned first; "zero" will clean the
>> pack as well.
>>
>> However, we still need to improve on how product server is restarted;
>> i.e. the server should be restarted only if there has been a change applied
>> to template, patch list is updated, lib files are updated etc. But I don't
>> think we can reliably detect (from Puppet side) whether server should be
>> restarted or not. Perhaps a template change may not need a restart. So IMO,
>> it's better to restart the server on every Puppet run. Any thoughts?
>>
>> Thanks.
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> --
> Rasanjaya Subasinghe
> Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka)
> +94772250358
> rasanj...@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] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

[Malintha Amarasinghe]

Tested with reverse proxy: basic APIM Publisher/Store/Admin UI
functionalities and Stats
Tested Publisher/Store and Admin REST APIs

[+] Stable - go ahead and release

On Fri, Jul 22, 2016 at 2:47 PM, Abimaran Kugathasan 
wrote:

> Please find the P2-Repo here [1]
>
>
> [1] :
> https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/rc4/
>
> On Fri, Jul 22, 2016 at 2:41 PM, Lalaji Sureshika  wrote:
>
>> Tested basic APIM flow+token  encryption+ scopes validation+lifecycle
>> management with multiple api versions in both super tenant and tenant
>> modes.No issues found.
>>
>> [+] Stable - go ahead and release
>>
>> On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna <
>> tharin...@wso2.com> wrote:
>>
>>> Tested Distributed Setup with following.
>>>
>>> 1. Throttling
>>> 2. Statistics
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:
>>>
 Tested the workflow extensions with WSO2 BPS for super tenant and
 tenant. Works fine.

 [+] Stable - go ahead and release

 Thanks.

 On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha <
 uvin...@wso2.com> wrote:

> Tested below with secure vault with custom key store
>
> 1. API publication and invocation tenant and super tenant
> 2. Stats tenant and super tenant(Store and Publisher)
> 3. Log Analyzer tenant and super tenant
>
> No issues found
>
> [+] Stable - go ahead and release.
>
>
> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>
>> 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 <
>> ruks...@wso2.com> 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 <
 abima...@wso2.com> 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
>>>

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

[Sriskandarajah Suhothayan]

On Fri, Jul 22, 2016 at 3:00 PM, Johann Nallathamby  wrote:

>
>
> On Fri, Jul 22, 2016 at 8:33 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan <
>> s...@wso2.com> wrote:
>>
>>>
>>>
>>> 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.
>>>
>> In this case, from IS side, without parsing only the user claims needed
>> for a particular email template(i.e.user claim values for the placeholders
>> in email template), we have to pass all the user claims as arbitrary data
>> values. In that case there's no need for loading the template from the
>> registry in IS side. So that in analytics side, all the values needed for
>> filling out the template will be there. Will check on that.
>>
>
> I don't think it will be a good solution. There can be sensitive
> information in the claims which we can't send. So for this release it's OK
> if we read the template in both sides - security is more important than
> performance; or read it only in IS side - but additionally send all those
> claims as arbitrary data as well, so if some one wants can use them in CEP
> side by their output adaptors.
>

I think then we can have a common configuration in IS side to specify what
are the claims that should be added to notifications.

Regards
Suho


>
>
>>>
 (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 <%28%2B94%29%20779%20756%20757> | blog:
>>> 

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

[Thusitha Thilina Dayaratne]

Hi All,

Thank you for testing the WSO2 MSF4J 2.0.0-rc4. We are closing this vote.
This vote has passed with 3 +1s and 0 -1s. Therefore we will proceed with
the MSF4J 2.0.0 release.

Thanks
Thusitha

On Fri, Jul 22, 2016 at 3:04 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi All,
>
> I've tested following samples and found no issues.
>
>- helloworld
>- spring-helloworld
>- basicauth-security
>- jpa
>
> [x] Stable - Go ahead and release.
>
> Thanks
> Thusitha
>
>
> On Fri, Jul 22, 2016 at 2:55 PM, Prabushi Samarakoon 
> wrote:
>
>> Hi All,
>>
>> I have tested for file upload(POST) using "multipart/form-data" enctype
>> for product UUF, which didn't support in previous releases. It is working
>> fine now.
>>
>> [x] Stable - Go ahead and release.
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 11:02 AM, Dulanja Liyanage 
>> wrote:
>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Prabushi Samarakoon*
>> Software Engineer
>> Mobile: +94715434580
>> Email: prabus...@wso2.com
>>
>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>


-- 
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 MSF4J 2.0.0 RC4

[Thusitha Thilina Dayaratne]

Hi All,

I've tested following samples and found no issues.

   - helloworld
   - spring-helloworld
   - basicauth-security
   - jpa

[x] Stable - Go ahead and release.

Thanks
Thusitha


On Fri, Jul 22, 2016 at 2:55 PM, Prabushi Samarakoon 
wrote:

> Hi All,
>
> I have tested for file upload(POST) using "multipart/form-data" enctype
> for product UUF, which didn't support in previous releases. It is working
> fine now.
>
> [x] Stable - Go ahead and release.
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 11:02 AM, Dulanja Liyanage 
> wrote:
>
>> 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
>>
>>
>
>
> --
> *Prabushi Samarakoon*
> Software Engineer
> Mobile: +94715434580
> Email: prabus...@wso2.com
>



-- 
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] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Johann Nallathamby]

On Fri, Jul 22, 2016 at 8:33 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi,
>
> On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan  > wrote:
>
>>
>>
>> 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.
>>
> In this case, from IS side, without parsing only the user claims needed
> for a particular email template(i.e.user claim values for the placeholders
> in email template), we have to pass all the user claims as arbitrary data
> values. In that case there's no need for loading the template from the
> registry in IS side. So that in analytics side, all the values needed for
> filling out the template will be there. Will check on that.
>

I don't think it will be a good solution. There can be sensitive
information in the claims which we can't send. So for this release it's OK
if we read the template in both sides - security is more important than
performance; or read it only in IS side - but additionally send all those
claims as arbitrary data as well, so if some one wants can use them in CEP
side by their output adaptors.


>>
>>> (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 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ twitter:
>> http://twitter.com/suhothayan  | linked-in:
>> http://lk.linkedin.com/in/suhothayan *
>>
>
>
>
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255
>



-- 
Thanks & 

[Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

[Chaminda Jayawardena]

Hi,

I followed the steps in [1] and getting below exception[2] when proxy
service is invoked.
I manually encrypted the username:password using ciphertool.sh and used
encrypted value in the proxy service as below. And also I could success
when the same user:pass combination is not encrypted.
Anything missed here or just a bug ?

*smb://{wso2:vault-decrypt('encrypted_user:pass_from_ciphertool')}@localhost/share/test1*

[1] https://wso2.org/jira/browse/ESBJAVA-4679
[2]
[2016-07-22 14:48:11,221] ERROR - VFSTransportListener Error checking for
existence and readability : smb://@localhost/share/test1
org.apache.commons.vfs2.FileSystemException: Could not determine the type
of file "smb://localhost/share/test1".
at
org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1523)
at
org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:490)
at
org.apache.commons.vfs2.provider.AbstractFileObject.exists(AbstractFileObject.java:478)
at
org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:294)
at
org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:188)
at
org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:134)
at
org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: jcifs.smb.SmbAuthException: Logon failure: unknown user name or
bad password.
at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:406)
at jcifs.smb.SmbSession.send(SmbSession.java:218)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
at jcifs.smb.SmbFile.connect(SmbFile.java:954)
at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
at jcifs.smb.SmbFile.queryPath(SmbFile.java:1335)
at jcifs.smb.SmbFile.exists(SmbFile.java:1417)
at jcifs.smb.SmbFile.isDirectory(SmbFile.java:1490)
at
org.apache.commons.vfs2.provider.smb.SmbFileObject.createSmbFile(SmbFileObject.java:119)
at
org.apache.commons.vfs2.provider.smb.SmbFileObject.doAttach(SmbFileObject.java:71)
at
org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1506)
... 10 more




-- 
Thanks & Regards

*Chaminda Jayawardena*
Senior Software Engineer - QA
WSO2 Inc. - http://wso2.com
+94-77-7725234
___
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

[Johann Nallathamby]

On Fri, Jul 22, 2016 at 7:58 AM, Sriskandarajah Suhothayan 
wrote:

>
>
> 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?
>

+1. We should write a TenantMgtListener and create these items when a
tenant is created.


>
> 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 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 
Thanks & Regards,

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

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Prabushi Samarakoon]

Hi All,

I have tested for file upload(POST) using "multipart/form-data" enctype for
product UUF, which didn't support in previous releases. It is working fine
now.

[x] Stable - Go ahead and release.

Thanks.

On Fri, Jul 22, 2016 at 11:02 AM, Dulanja Liyanage  wrote:

> 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
>
>


-- 
*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

[Abimaran Kugathasan]

Please find the P2-Repo here [1]


[1] : https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/rc4/

On Fri, Jul 22, 2016 at 2:41 PM, Lalaji Sureshika  wrote:

> Tested basic APIM flow+token  encryption+ scopes validation+lifecycle
> management with multiple api versions in both super tenant and tenant
> modes.No issues found.
>
> [+] Stable - go ahead and release
>
> On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna  > wrote:
>
>> Tested Distributed Setup with following.
>>
>> 1. Throttling
>> 2. Statistics
>>
>> [+] Stable - go ahead and release
>>
>> Thanks
>>
>>
>> On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:
>>
>>> Tested the workflow extensions with WSO2 BPS for super tenant and
>>> tenant. Works fine.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks.
>>>
>>> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
 Tested below with secure vault with custom key store

 1. API publication and invocation tenant and super tenant
 2. Stats tenant and super tenant(Store and Publisher)
 3. Log Analyzer tenant and super tenant

 No issues found

 [+] Stable - go ahead and release.


 On 22 July 2016 at 12:20, Roshan Wijesena  wrote:

> 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 <
> ruks...@wso2.com> 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 <
>>> abima...@wso2.com> 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 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> Architecture mailing list
> architect...@wso2.org
> 

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

[Lalaji Sureshika]

Tested basic APIM flow+token  encryption+ scopes validation+lifecycle
management with multiple api versions in both super tenant and tenant
modes.No issues found.

[+] Stable - go ahead and release

On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna 
wrote:

> Tested Distributed Setup with following.
>
> 1. Throttling
> 2. Statistics
>
> [+] Stable - go ahead and release
>
> Thanks
>
>
> On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:
>
>> Tested the workflow extensions with WSO2 BPS for super tenant and tenant.
>> Works fine.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha > > wrote:
>>
>>> Tested below with secure vault with custom key store
>>>
>>> 1. API publication and invocation tenant and super tenant
>>> 2. Stats tenant and super tenant(Store and Publisher)
>>> 3. Log Analyzer tenant and super tenant
>>>
>>> No issues found
>>>
>>> [+] Stable - go ahead and release.
>>>
>>>
>>> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>>>
 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 <
>> abima...@wso2.com> 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 <%2B94719154640>*
 Email: ros...@wso2.com
 *WSO2, Inc. :** wso2.com *
 lean.enterprise.middleware.

 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Regards,
>>> Uvindra
>>>
>>> Mobile: 33962
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chamin Dias
>> *Software Engineer*
>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
>> Email : 

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

[Harsha Kumara]

Tested Throttling Levels of Resource Level, API, Subscription, and
Application 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 in both tenant and super tenant spaces.
Tested rate limiting and hard level throttling in super tenant and tenant
mode. No issue found.

[+] Stable - go ahead and release

Thanks
Harsha

On Fri, Jul 22, 2016 at 2:29 PM, Tharindu Dharmarathna 
wrote:

> Tested Distributed Setup with following.
>
> 1. Throttling
> 2. Statistics
>
> [+] Stable - go ahead and release
>
> Thanks
>
>
> On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:
>
>> Tested the workflow extensions with WSO2 BPS for super tenant and tenant.
>> Works fine.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks.
>>
>> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha > > wrote:
>>
>>> Tested below with secure vault with custom key store
>>>
>>> 1. API publication and invocation tenant and super tenant
>>> 2. Stats tenant and super tenant(Store and Publisher)
>>> 3. Log Analyzer tenant and super tenant
>>>
>>> No issues found
>>>
>>> [+] Stable - go ahead and release.
>>>
>>>
>>> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>>>
 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 <
>> abima...@wso2.com> 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 <%2B94719154640>*
 Email: ros...@wso2.com
 *WSO2, Inc. :** wso2.com *
 lean.enterprise.middleware.

 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Regards,
>>> Uvindra
>>>
>>> 

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

[Tharindu Dharmarathna]

Tested Distributed Setup with following.

1. Throttling
2. Statistics

[+] Stable - go ahead and release

Thanks


On Fri, Jul 22, 2016 at 2:00 PM, Chamin Dias  wrote:

> Tested the workflow extensions with WSO2 BPS for super tenant and tenant.
> Works fine.
>
> [+] Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Tested below with secure vault with custom key store
>>
>> 1. API publication and invocation tenant and super tenant
>> 2. Stats tenant and super tenant(Store and Publisher)
>> 3. Log Analyzer tenant and super tenant
>>
>> No issues found
>>
>> [+] Stable - go ahead and release.
>>
>>
>> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>>
>>> 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 <
> abima...@wso2.com> 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 <%2B94719154640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Chamin Dias
> *Software Engineer*
> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
> Email : cham...@wso2.com
> Blog : https://chamindias.wordpress.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Tharindu Dharmarathna*Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [MySql5.7] Concern about MySql 5.7 scripts running with -Dsetup

[Kishanthan Thangarajah]

"-Dsetup" is a development time option and in production it is not used
mostly. Users manually populate the DB's using relevant scripts by
executing them separately. Due to this fact only, we did not invest time in
supporting mysql 5.7 with "-Dsetup" option. We have documented this also :
https://docs.wso2.com/display/ADMIN447/Setting+up+MySQL

We cannot remove this option from 4.4.x kernel as we do only patch releases
on top of it.

On Wed, Jul 13, 2016 at 11:42 AM, Pubudu Priyashan  wrote:

> +1 to Nuwan's suggestion.
>
> I too have experienced inconsistencies in the past while using the -Dsetup
> when configuring the databases where we still have to manually execute the
> scripts. Since we are not using this feature in production environments I
> think it wouldn't hurt to get rid of this all together. Since we can always
> run the relevant scripts manually, if there is no significant advantage of
> keeping this feature I think it's a good idea to remove it. Just my
> personal opinion.
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>
> On Wed, Jul 13, 2016 at 11:35 AM, Nuwan Dias  wrote:
>
>> Practically the -Dsetup option is never used in production. All "real"
>> users of our products have DB admins and all that who carefully evaluate
>> and execute our DB scripts on their Database servers. They would never
>> allow a product startup process to create tables and indexes at will on
>> their database servers.
>>
>> So I think we should just remove this option all together. I know we've
>> done that on C5 but it probably makes sense to remove this option in C4
>> products as well. We sometimes even have to make design changes to our
>> features to support this option (when two features have their own DB
>> scripts). And I think its a complete waste because we're compromising the
>> design of our products to support a feature thats never used in the real
>> world.
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Jul 13, 2016 at 11:05 AM, Pubudu Priyashan 
>> wrote:
>>
>>>
>>> Hi all,
>>>
>>> When we use MySql 5.7 as the DB and start the server with -Dsetup
>>> without manually executing the scripts at DB level, we have observed the
>>> issue logged at [1] while testing wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack.
>>> The reason behind this is, by default the pack is picking up mysql.sql
>>> script located at [$HOME]/dbscripts directory when started with -Dsetup. A
>>> solution was suggested in this comment [2] to rename the mysql5.7.sql
>>> scripts as mysql.sql when using MySql 5.7 db and we have verified that this
>>> suggestion fixed the issue. We have logged a doc JIRA to include that
>>> information at [3] for now.
>>>
>>> Our concern is since this is going to affect all the products when using
>>> MySql5.7 do we have a better solution to automatically select the
>>> mysql version without having to rename the script? Is it possible to add a
>>> property to define the db version somewhere and then point to the relevant
>>> script without renaming the script when starting with -Dsetup? Or any
>>> better solution if possible. Appreciate your feedback on this. Thanks!
>>>
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4748
>>> [2]
>>> https://wso2.org/jira/browse/ESBJAVA-4748?focusedCommentId=123463=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-123463
>>> [3] https://wso2.org/jira/browse/DOCUMENTATION-3604
>>>
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>


-- 
*Kishanthan Thangarajah*
Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Afkham Azeez]

I have tested the pet store sample with analytics & everything is working
fine.

[x ] Stable  - Go ahead and release

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
> 
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

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

[Isuru Perera]

Hi Rasika,

When you disable Metrics, the reporters will not be started and the Metrics
won't be calculated. We cannot avoid the Metrics initialization by
disabling it. So, when you disable Metrics, you will only see logs for
creating the reporters. The reporter starting logs should not be there.

The MSF4J feature is importing the
org.wso2.carbon.metrics.jdbc.core.feature and
org.wso2.carbon.metrics.das.core.feature [1]. The
org.wso2.carbon.metrics.jdbc.core.feature requires a datasource and that's
why you must be seeing a Hikari Pool initializing at the startup. The
org.wso2.carbon.metrics.jdbc.core.feature is importing the datasources
feature, which creates Hikari Pools.

How did you measure the time added by Carbon Metrics feature? In Carbon
Metrics repository, there is a sample distribution [2] and it takes 2
seconds to start the server (in my machine). Will you be able to test the
same distribution and check how long does it take to start the server?

I think we should have included a separate feature for MSF4J analytics. We
already have a separate modules for MSF4J core and MSF4J analytics. So,
there should be a separate feature for MSF4J analytics. When there is a
separate MSF4J analytics feature, the products can include only if the
analytics are required. (MSF4J team, WDYT?).

[1]
https://github.com/wso2/msf4j/blob/v2.0.0-rc4/features/org.wso2.msf4j.feature/pom.xml#L244-L251
[2] https://github.com/wso2/carbon-metrics/tree/v2.0.0/distribution

On Fri, Jul 22, 2016 at 11:05 AM, Rasika Perera  wrote:

> ​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
>



-- 
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

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

[Chamin Dias]

Tested the workflow extensions with WSO2 BPS for super tenant and tenant.
Works fine.

[+] Stable - go ahead and release

Thanks.

On Fri, Jul 22, 2016 at 1:41 PM, Uvindra Dias Jayasinha 
wrote:

> Tested below with secure vault with custom key store
>
> 1. API publication and invocation tenant and super tenant
> 2. Stats tenant and super tenant(Store and Publisher)
> 3. Log Analyzer tenant and super tenant
>
> No issues found
>
> [+] Stable - go ahead and release.
>
>
> On 22 July 2016 at 12:20, Roshan Wijesena  wrote:
>
>> 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 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chamin Dias
*Software Engineer*
Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
Email : cham...@wso2.com
Blog : https://chamindias.wordpress.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

[Uvindra Dias Jayasinha]

Tested below with secure vault with custom key store

1. API publication and invocation tenant and super tenant
2. Stats tenant and super tenant(Store and Publisher)
3. Log Analyzer tenant and super tenant

No issues found

[+] Stable - go ahead and release.


On 22 July 2016 at 12:20, Roshan Wijesena  wrote:

> 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 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,
Uvindra

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

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Akila Ravihansa Perera]

Hi,


> 3. Each and every time the config file change [Ex: axis2.xml] product gets
>> deleted and start with the fresh configuration.
>>
>
> ​Agree! It should not start from the beginning for a configuration change.
>

This is now fixed in master branch. Basically Puppet runs in "refresh" mode
by default. It will kill any running WSO2 process before applying
configurations but will use the same pack if it has been already downloaded
from Puppet master. Also it will apply new configurations on top of
previous installation if it exists. You can control this behavior by
setting "wso2::maintenance_mode" Hiera property. If you set it to "new"
then any previous installation will be cleaned first; "zero" will clean the
pack as well.

However, we still need to improve on how product server is restarted; i.e.
the server should be restarted only if there has been a change applied to
template, patch list is updated, lib files are updated etc. But I don't
think we can reliably detect (from Puppet side) whether server should be
restarted or not. Perhaps a template change may not need a restart. So IMO,
it's better to restart the server on every Puppet run. Any thoughts?

Thanks.

-- 
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] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Indunil Upeksha Rathnayake]

Hi,

On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan 
wrote:

>
>
> 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.
>
In this case, from IS side, without parsing only the user claims needed for
a particular email template(i.e.user claim values for the placeholders in
email template), we have to pass all the user claims as arbitrary data
values. In that case there's no need for loading the template from the
registry in IS side. So that in analytics side, all the values needed for
filling out the template will be there. Will check on that.

>
>
>> (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 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 
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] [DEV][ESB Tooling] Data mapper interprets multiplication of negative integers by zero results in signed zero

[Nuwan Pallewela]

Hi Chanaka,


On Fri, Jul 22, 2016 at 12:47 PM, Chanaka Fernando 
wrote:

> Hi Chathurika,
>
> We understand your point. But this is not a functional blocker. We will
> reduce the priority of this issue and as NuwanP mentioned in the ticket,
> this needs to be fixed from the JS engine level. If we are going to deal
> with that, it will reduce the performance of the entire data mapper and we
> cannot go down this path.
>
> @NuwanP: Please report a JIRA against the JS engine and reduce the
> priority of this issue and keep it opened.
>
Sure. I will do.

>
> Thanks,
> Chanaka
>
> On Fri, Jul 22, 2016 at 12:39 PM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi
>>
>> Currently in data mapper, the multiplication of -2 * 0 results in -0.
>> Ideally in basic mathematics the value zero should not have any - or +
>> marking on it. I have reported [1] regarding this and according to jira's
>> comments if this is to be fixed the -0 should be converted to string and
>> then again to a number and it is shown as a concern there that this will
>> have a performance impact due to unnecessary operations.
>>
>> Signed zero itself is used for some mathematical operations[2]  but
>> seemingly there is no such operation that uses signed zero available in
>> data mapper currently. So rather than shipping signed zero, can we ship it
>> to adhere the basic mathematics (if there's no hidden usage of signed -0
>> that is) because first impression matters and first impression depends on
>> minor things like these as well.
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-627
>> [2] https://en.wikipedia.org/wiki/Signed_zero
>>
>> 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 
>
>
>
>
>
>
>
Thanks,
Nuwan

-- 
--

*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] Data mapper interprets multiplication of negative integers by zero results in signed zero

[Chanaka Fernando]

Hi Chathurika,

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

@NuwanP: Please report a JIRA against the JS engine and reduce the priority
of this issue and keep it opened.

Thanks,
Chanaka

On Fri, Jul 22, 2016 at 12:39 PM, Chathurika De Silva 
wrote:

> Hi
>
> Currently in data mapper, the multiplication of -2 * 0 results in -0.
> Ideally in basic mathematics the value zero should not have any - or +
> marking on it. I have reported [1] regarding this and according to jira's
> comments if this is to be fixed the -0 should be converted to string and
> then again to a number and it is shown as a concern there that this will
> have a performance impact due to unnecessary operations.
>
> Signed zero itself is used for some mathematical operations[2]  but
> seemingly there is no such operation that uses signed zero available in
> data mapper currently. So rather than shipping signed zero, can we ship it
> to adhere the basic mathematics (if there's no hidden usage of signed -0
> that is) because first impression matters and first impression depends on
> minor things like these as well.
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-627
> [2] https://en.wikipedia.org/wiki/Signed_zero
>
> 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] Moving carbon dashboards version to 2.0.0-SNAPSHOT

[Nuwan Dias]

Sorry for being late on this but why are we doing a major version bump if
the changes are backwards compatible? It goes against the meaning of the
semantic versioning strategy and gives a wrong impression to the consumers
of this feature/component thinking that there are backwards incompatible
API changes and hence discouraging quick upgrades from the earlier version.

Thanks,
NuwanD.

On Fri, Jul 8, 2016 at 5:58 PM, Tanya Madurapperuma  wrote:

> Pushed the changes to master.
>
> Thanks,
> Tanya
>
> On Fri, Jul 8, 2016 at 5:40 PM, Dunith Dhanushka  wrote:
>
>> Hi Tanya,
>>
>> Thanks for the explanation. We assume any feature that will be added
>> later will backward compatible.
>>
>> Regards,
>> Dunith
>>
>> On Fri, Jul 8, 2016 at 5:18 PM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Dunith,
>>>
>>> All the new features were there on the 1.0.20-SNAPSHOT version. AFAIK
>>> you have already verified your build with 1.0.20-SNAPSHOT. Hence this will
>>> just be a version change for you.
>>> Let us know if you have any concerns.
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Fri, Jul 8, 2016 at 5:13 PM, Dunith Dhanushka 
>>> wrote:
>>>
 Hi Tanya,

 On second thought, can you be specific on new features?

 Since we are on the verge of DAS 3.1.0 release today, it's better to go
 without new features. Can you merge 4.4.7 related security fixes to
 1.0.20-SNAPSHOT ?

 Thanks,
 Dunith


 On Fri, Jul 8, 2016 at 4:59 PM, Dunith Dhanushka 
 wrote:

> Ack!
>
> On Fri, Jul 8, 2016 at 4:56 PM, Tanya Madurapperuma 
> wrote:
>
>> Hi all,
>>
>> We will be $ Subject from 1.0.20-SNAPSHOT. Reason is we have new
>> features added and also upgraded the carbon kernel version to 4.4.7.
>>
>> Please note this if you are pointing to carbon dashboards
>> 1.0.20-SNAPSHOT in any of your repos atm.
>>
>> Thanks,
>> Tanya
>>
>> --
>> Tanya Madurapperuma
>>
>> Senior Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>> Blog : http://tanyamadurapperuma.blogspot.com
>>
>
>
>
> --
> Regards,
>
> Dunith Dhanushka,
> Associate Technical Lead
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - *https://medium.com/@dunithd *
> Twitter - @dunithd 
>



 --
 Regards,

 Dunith Dhanushka,
 Associate Technical Lead
 WSO2 Inc,

 Mobile - +94 71 8615744
 Blog - *https://medium.com/@dunithd *
 Twitter - @dunithd 

>>>
>>>
>>>
>>> --
>>> Tanya Madurapperuma
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc. : wso2.com
>>> Mobile : +94718184439
>>> Blog : http://tanyamadurapperuma.blogspot.com
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Associate Technical Lead
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - *https://medium.com/@dunithd *
>> Twitter - @dunithd 
>>
>
>
>
> --
> Tanya Madurapperuma
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
> Blog : http://tanyamadurapperuma.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

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

[Chathurika De Silva]

Hi

Currently in data mapper, the multiplication of -2 * 0 results in -0.
Ideally in basic mathematics the value zero should not have any - or +
marking on it. I have reported [1] regarding this and according to jira's
comments if this is to be fixed the -0 should be converted to string and
then again to a number and it is shown as a concern there that this will
have a performance impact due to unnecessary operations.

Signed zero itself is used for some mathematical operations[2]  but
seemingly there is no such operation that uses signed zero available in
data mapper currently. So rather than shipping signed zero, can we ship it
to adhere the basic mathematics (if there's no hidden usage of signed -0
that is) because first impression matters and first impression depends on
minor things like these as well.

[1] https://wso2.org/jira/browse/DEVTOOLESB-627
[2] https://en.wikipedia.org/wiki/Signed_zero

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] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Gobinath Loganathan]

Hi Suho and all,

The problem has been identified and fixed with the new commit [1].
According to this commit, the following changes have been done:

(1) No need to use arbitrary_ prefix anywhere.
(2) The publisher will first check for payload data, if not available it
will check for the arbitrary data. Therefore use the arbitrary data map
keys as they are. [2][3]
(3) Arbitrary data can be used in dynamic properties. [3]

[1]
https://github.com/wso2/carbon-analytics-common/commit/f1d5cafe92e9b71b884a9a4838e2cc446cf83685

[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#L168

[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#L339

On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan 
wrote:

>
>
> 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 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 
*Gobinath **Loganathan*
Software Engineer, WSO2 Inc. http://wso2.com

Email  : gobin...@wso2.com
Mobile : (+94) 770 780 210
Blog: javahelps.com 

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