[Architecture] Datamapper - Meeting notes for today's meeting (12/09/2013)
Hi all, Please find below points discussed at the meeting held on Datamapper today. - A proper language for the config file generated by visual editor. - Mapping should be done from one top level type to target top level type. - In the config, source and target are defined to be separate variables. Attributes of those will be called as variable_name.attribute in further code. map org.wso2.employee[var x] - org.example.wso2.datamapper.engineer[var y] ... y.fullname = concat(x.firstname, x.lastname) ... end - Finally decided to use javascript as the config language - Can inherit inbuilt capabilities of javascript. - No need to define a separate lexer or parser. *ESB editor* - Edit eclipse wizard theme to match ESB editor theme. - Remove inappropriate items from project right-click menu. - Pop-up properties window for ESB elements. - A way to create a main sequence from new object creation wizard. Thanks, -- *Gayan Kaushalya Yalpathwala* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 8682704 http://us13.wso2con.com/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Appfactory] Managing permissions in Appfactory at different levels
Hi, And from the dashboard side of things we will be having roles such as CXO, Admin and AppFactoryUser(everyone else not in CXO or Admin). The idea is to show different default dashboards to users who have these roles and also gadgets which can be added to their dashboards if they so require. What would an advanced user do more than a general user ? Not sure how the roles will be used within build and governance stories - an update on that would be good. We seem to have different roles for different purposes - we might have to list the requirements down and get a full list - and remove overlaps and have a common naming convention - e.g. based on user activities, user's level of proficiency etc.. Thank you, Shiro On Thu, Sep 12, 2013 at 11:10 AM, Asanka Dissanayake asan...@wso2.comwrote: Hi, Now we don't have Application level roles.We have tenant level roles (for the WSO2 Con). So once a user is added as a developer of the tenant .He belongs to every application inside the tenant. So basically it's like this. Users can be imported to tenant using bulk import and at the moment they are added, only default user role is assigned. Developer,QA,Dev ops becomes tenant level roles.Tenant admin can invite users (from the added users to the tenant) for these roles. And the same permissions as previous will be allowed at the tenant level. On Wed, Sep 11, 2013 at 9:59 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi all, Can someone explain how we are going to manage AF level permissions bound by roles like Developer, QA, DevOps and application level permissions required to build the application? For example, as the application developer, I need to manage set of roles(GeneralUser, AdvancedUser) to control the access to my application. And are we using a single LDAP to manage development and production users, applications? thank you. -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Asanka Dissanayake Software Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: asan...@wso2.com ruch...@wso2.com, blog: cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94 71 8373821* -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] API Manager 1.5.0 RC2, Released
*WSO2 API Manager 1.5.0, RC2 Released !* The second RC build of WSO2 API Manager 1.5.0, can be downloaded from [1]. Please find a summary of all changes/bug fixes, listed below. Bug Fixes - [APIMANAGER-1479 https://wso2.org/jira/browse/APIMANAGER-1479] - Couldn't change the Thumbnail Image - [APIMANAGER-1480 https://wso2.org/jira/browse/APIMANAGER-1480] - API Remove Ratings functionality does not work as expected - [APIMANAGER-1495 https://wso2.org/jira/browse/APIMANAGER-1495] - Error in sample “ Access YouTube Feeds Using an API” - [APIMANAGER-1505 https://wso2.org/jira/browse/APIMANAGER-1505] - Intermittent Cache initializing error - Embedded API Manager - [APIMANAGER-1510 https://wso2.org/jira/browse/APIMANAGER-1510] - Docs and About links in mgt console direct to documentation version 1.4.1 - [APIMANAGER-1517 https://wso2.org/jira/browse/APIMANAGER-1517] - Resource Level Throttling does not work as expected - [APIMANAGER-1545 https://wso2.org/jira/browse/APIMANAGER-1545] - Application level Throttling Tier always set as Unlimited - [APIMANAGER-1553 https://wso2.org/jira/browse/APIMANAGER-1553] - Error when running YouTube sample - [APIMANAGER-1556 https://wso2.org/jira/browse/APIMANAGER-1556] - [Distributed]API Invocation fails when using WSClient - [APIMANAGER-1558 https://wso2.org/jira/browse/APIMANAGER-1558] - APIMGT MSSQL script not running on MSSQL 2012 - [APIMANAGER-1564 https://wso2.org/jira/browse/APIMANAGER-1564] - Store header goes missing when a user unsubscribe by removing the subscription - [APIMANAGER-1565 https://wso2.org/jira/browse/APIMANAGER-1565] - Users can subscribe to APIs eventhough there are no subscription level tiers - [APIMANAGER-1566 https://wso2.org/jira/browse/APIMANAGER-1566] - Tier Availability levels are not getting updated. Updates only during a server restart - [APIMANAGER-1567 https://wso2.org/jira/browse/APIMANAGER-1567] - API Update does not work correctly in tenant mode - [APIMANAGER-1568 https://wso2.org/jira/browse/APIMANAGER-1568] - Once throttle:Attributes are added in to a defined tier, API cannot be invoked - [APIMANAGER-1570 https://wso2.org/jira/browse/APIMANAGER-1570] - Exception throws when invoking token API to generate user tokens from SAML2 assertions - [APIMANAGER-1575 https://wso2.org/jira/browse/APIMANAGER-1575] - Calling token API and revoke api via HTTPS is broken - [APIMANAGER-1578 https://wso2.org/jira/browse/APIMANAGER-1578] - Revoke Token feature is broken - [APIMANAGER-1580 https://wso2.org/jira/browse/APIMANAGER-1580] - When request url not contains a forward slash not getting any response - [APIMANAGER-1584 https://wso2.org/jira/browse/APIMANAGER-1584] - API Manager tables are not getting created in oracle database - [APIMANAGER-1587 https://wso2.org/jira/browse/APIMANAGER-1587] - When EnableJWTCache=true with claims, APIs cannot be invoked - [APIMANAGER-1592 https://wso2.org/jira/browse/APIMANAGER-1592] - SAML SSO redirection does not work - [APIMANAGER-1594 https://wso2.org/jira/browse/APIMANAGER-1594] - Invoking via swagger does not work correctly via firefox - [APIMANAGER-1595 https://wso2.org/jira/browse/APIMANAGER-1595] - Store APIs go missing when clicking on tags in tenant mode - [APIMANAGER-1602 https://wso2.org/jira/browse/APIMANAGER-1602] - Recently created APIs go missing from store - [APIMANAGER-1618 https://wso2.org/jira/browse/APIMANAGER-1618] - Once an API is blocked and try to publish Update button goes un responsive (disable) - [APIMANAGER-1620 https://wso2.org/jira/browse/APIMANAGER-1620] - Already subscribed user can subscribe to a deprecated API via a different application - [APIMANAGER-1621 https://wso2.org/jira/browse/APIMANAGER-1621] - Life cycle history does not show the latest activities in publisher - [APIMANAGER-1622 https://wso2.org/jira/browse/APIMANAGER-1622] - API provider is not shown when a user clicks in More APIs from section on an API in a different state in store - [APIMANAGER-1627 https://wso2.org/jira/browse/APIMANAGER-1627] - API Updated time in Store is always the API created time - [APIMANAGER-1629 https://wso2.org/jira/browse/APIMANAGER-1629] - User roles cannot be created in tenant mode when the user store is pointed to LDAP - [APIMANAGER-1639 https://wso2.org/jira/browse/APIMANAGER-1639] - [Intermittent] Issues in caching in permission in store side and login Improvements - [APIMANAGER-1537 https://wso2.org/jira/browse/APIMANAGER-1537] - Application Edit UI - UI Improvements 1 - [APIMANAGER-1538 https://wso2.org/jira/browse/APIMANAGER-1538] - Application Edit UI - UI Improvements 2 - [APIMANAGER-1539 https://wso2.org/jira/browse/APIMANAGER-1539] - Application Edit UI - UI Improvements 3 - [APIMANAGER-1540 https://wso2.org/jira/browse/APIMANAGER-1540] -
Re: [Architecture] [Appfactory] Managing permissions in Appfactory at different levels
Hi Shiro and Asanka, I understood how developer, QA, DevOps roles work within appfactory. What I try to understand is, as a developer, I want to provide authorization for my web application. For that, I want to utilize carbon permission model so that I can define different roles such as basicUser, advancedUser. For example, based on these roles, web application will show different themes, functionalities and so on. And how these roles basicUser, advancedUser differ from Developer, QA when it comes to management of roles. thank you. On Thu, Sep 12, 2013 at 3:48 AM, Shiroshica Kulatilake sh...@wso2.comwrote: Hi, And from the dashboard side of things we will be having roles such as CXO, Admin and AppFactoryUser(everyone else not in CXO or Admin). The idea is to show different default dashboards to users who have these roles and also gadgets which can be added to their dashboards if they so require. What would an advanced user do more than a general user ? Not sure how the roles will be used within build and governance stories - an update on that would be good. We seem to have different roles for different purposes - we might have to list the requirements down and get a full list - and remove overlaps and have a common naming convention - e.g. based on user activities, user's level of proficiency etc.. Thank you, Shiro On Thu, Sep 12, 2013 at 11:10 AM, Asanka Dissanayake asan...@wso2.comwrote: Hi, Now we don't have Application level roles.We have tenant level roles (for the WSO2 Con). So once a user is added as a developer of the tenant .He belongs to every application inside the tenant. So basically it's like this. Users can be imported to tenant using bulk import and at the moment they are added, only default user role is assigned. Developer,QA,Dev ops becomes tenant level roles.Tenant admin can invite users (from the added users to the tenant) for these roles. And the same permissions as previous will be allowed at the tenant level. On Wed, Sep 11, 2013 at 9:59 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi all, Can someone explain how we are going to manage AF level permissions bound by roles like Developer, QA, DevOps and application level permissions required to build the application? For example, as the application developer, I need to manage set of roles(GeneralUser, AdvancedUser) to control the access to my application. And are we using a single LDAP to manage development and production users, applications? thank you. -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Asanka Dissanayake Software Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: asan...@wso2.com ruch...@wso2.com, blog: cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94 71 8373821* -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] A Single Notification Story
This discussion is aimed at understanding the different implementations of Notifications within the platform, and unifying it. We want this to happen soon to make sure we have a generic model in place along with the Enterprise Store, G-Reg. You have been invited to the following event. Title: A Single Notification Story When: Mon Sep 16, 2013 1:30pm – 2:30pm Colombo Where: LK 7th Floor Meeting Room - Banksy Who: * Senaka Fernando - organizer * Srinath Perera * Sanjiva Weerawarana * Paul Fremantle * Nuwan Bandara * Sumedha Rubasinghe * Anjana Fernando * Dimuthu Leelarathne * Shammi Jayasinghe * Afkham Azeez - optional ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Revamping Message Store and Message Processor (MS/MP) Implementaion
Kasun, lets have automated tests to fully test the scenarios so it will save time in the future. MB team will also help. --Srinath On Tue, Sep 10, 2013 at 9:28 AM, Kasun Indrasiri ka...@wso2.com wrote: Hi Ishan/Shafreen, This needs to be done-done. Apparently, this was not tested properly with WSO2 MB, which was a main objective that we have clearly setup during the initial discussions. So, please do the needful and get this fully tested against MB. This needs to be done before M2 packs. Thanks. On Thu, Aug 8, 2013 at 4:40 PM, Samisa Abeysinghe sam...@wso2.com wrote: When you guys said 90% done, it apparently meant code complete that much. Please make sure to be done-done! On Wed, Aug 7, 2013 at 4:56 PM, Ishan Jayawardena is...@wso2.com wrote: We can use the existing samples with the new implementation. Although we have added several parameters and configuration changes to the new implementation, it is still fully backward compatible with the old configuration. For the new features/changes that we have implemented, we will add samples+documentation. We will also add integration tests. Thanks, Ishan. On Wed, Aug 7, 2013 at 4:40 PM, Samisa Abeysinghe sam...@wso2.comwrote: Samples? On Wed, Aug 7, 2013 at 9:23 AM, Ishan Jayawardena is...@wso2.comwrote: Hi Samisa, We will start working on the new documentation by the end of this week as we have completed most of the implementation. Hasitha, We use client ack in the new implementation, and there is only a single connection to produce messages and each consumer has its own connection. We are just using the raw JMS API and therefore we have not implemented any JMS Object caching within the message store or message processor apart from reusing the producer/consumer connections. Thanks, Ishan. On Wed, Aug 7, 2013 at 6:31 AM, Hasitha Hiranya hasit...@wso2.comwrote: Hi, ++1 for the new implementation. So new implementation utilizes Client Ack rather than message browse deliverif success consume ? What about connection caching, session caching and consumer caching? And how JMS transactions come into play? One of major problem previous implementation had was creating a two new connection for every message. I suppose we have got rid of all of such limitations with the new implementation. Thanks. On Wed, Aug 7, 2013 at 6:12 AM, Samisa Abeysinghe sam...@wso2.comwrote: Documentation? On Mon, Aug 5, 2013 at 10:08 AM, Kasun Indrasiri ka...@wso2.comwrote: It seems we are done with most of the core features and we should try to finish this off by this week. On Fri, Aug 2, 2013 at 9:36 AM, Isuru Udana isu...@wso2.comwrote: Hi, As planned earlier, we have completed most of the implementation (about 90%) by today. To be more specific following are the things we have completed so far. -MS/MP core functionality -New blocking sender which supports most of the endpoint functionality -Fixing the UIs accordingly -Fixing the deployers accordingly -Testing basic functionality of the new implementation (both UI and non UI stuff) We have to test the multiple consumer scenarios as well (one store/multiple processors) Following are the left items to be completed. -Finish the implementation of In memory Message-Store -Integrate Message processor with the new blocking sender -Fix few functions of JMX MBeans of Message-Processors -Fix the existing failing test cases Since the new blocking sender is implemented in a generic way (does not contain message-processor specific functionality), As a part of this effort, I am planning to integrate it with the Callout mediator as well. So that it will be a significant improvement for the Callout Mediator. +1. Next week we are planing to continue with testing the functionality including the MB integration, REST support, security,etc. Thanks. On Mon, Jul 29, 2013 at 10:41 AM, Shafreen Anfar shafr...@wso2.com wrote: Hi, Since the existing implementation of MS/MP is quite un-maintainable, we thought of revamping the existing implementation. Link[1] contains the rough component diagram of the existing MS/MP implementation. According to this design most of the work is done by the MessageStore class. It was implemented with basic queue operations and act as a proxy to the actual message stores such as in-memory-maps and JMS-Queues. However, this design didn't cope well with scenarios such as reliable messaging. For example, we came across a lot of integration issues while we were testing ESB-4.7.0 with WSO2-MB. Moreover, though message processors are implemented using Quartz, the existing implementation hasn't utilized it's APIs to the full extent. In addition to that current implementation is implemented basically focusing on SOAP messages. And In the current implementation none of the endpoint functionality is supported (security, RM, etc.). Only the Address endpoint type is
