Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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
Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
So if we deploy an app into production, v1, then it works, then we deploy v2 into production and it does not work, how do we revert back to v1? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 1:50 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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 mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Connector:SugarCRM
Hi Malaka, SugarCRM does not provide direct operation for delete and update. Instead you can user set_entry and be sure to set deleted = 1 in your parameter array. This doesn't actually remove it from the database but will prevent it from being returned by Sugar unless you have specifically asked to see items that are marked as deleted. Thanks Indika -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-SugarCRM-tp89877p89985.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
Hi Samisa, Having application version v1 in production doesn't effect having v2 also in production. since artifacts of V1 and V2 are two different artifacts ( e.g. myapp-v1.war, myapp-v2.war) that will end up in relevant run time (e.g production app server). In that sense, demoting V2 also doesn't affect V1. How ever, I suspect what's explained above doesn't answer your question. If I understood right, your concern is about how to address the scenario where: user have a one build of the application version V1 ( lets call it V1.build1) working in Production. and for some reason it was demoted all the way back to 'Development'. Then, Developer makes some changes (V1.build2) - promotes to Testing - QA promotes to Production - now Production have V1.build2 - V1.build2 doesn't work in production. We don't have a solution for this right now. A way to solve this would be : 1. AF needs to have the ability to store multiple artifacts/builds of the same version in a storage. (and add notes, dates ,against these artifacts to so users can keep track) 2. Users ( /devops) should be able to deploy one of these artifacts in a Production ( we could allow similar functionality of other stages too) through UI. Thoughts? regards, Ramith On Thu, Dec 19, 2013 at 2:05 PM, Samisa Abeysinghe sam...@wso2.com wrote: So if we deploy an app into production, v1, then it works, then we deploy v2 into production and it does not work, how do we revert back to v1? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 1:50 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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 mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 776715671 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
Hi all, Do we need to support v1.build1, v1.build2 like artifacts when we have a version concept already such as v1, v2 ? It seems to me that, having v1.build1, v1,build2 introduces another version concept based on build version on top of v1(source version). thank you. On Thu, Dec 19, 2013 at 3:33 PM, Samisa Abeysinghe sam...@wso2.com wrote: I thought, if we had staging, we have a solution. Because, when v1.build2 goes into production, and fails, there is an already running v1.build1 to which we can transition smoothly. And v1.build1 is guaranteed to work, as that was the version which was in production prior to v1.build2. This is why I asked the original question, if there is no staging, how do we revert in case of failure in build2. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 2:54 PM, Ramith Jayasinghe ram...@wso2.comwrote: Hi Samisa, Having application version v1 in production doesn't effect having v2 also in production. since artifacts of V1 and V2 are two different artifacts ( e.g. myapp-v1.war, myapp-v2.war) that will end up in relevant run time (e.g production app server). In that sense, demoting V2 also doesn't affect V1. How ever, I suspect what's explained above doesn't answer your question. If I understood right, your concern is about how to address the scenario where: user have a one build of the application version V1 ( lets call it V1.build1) working in Production. and for some reason it was demoted all the way back to 'Development'. Then, Developer makes some changes (V1.build2) - promotes to Testing - QA promotes to Production - now Production have V1.build2 - V1.build2 doesn't work in production. We don't have a solution for this right now. A way to solve this would be : 1. AF needs to have the ability to store multiple artifacts/builds of the same version in a storage. (and add notes, dates ,against these artifacts to so users can keep track) 2. Users ( /devops) should be able to deploy one of these artifacts in a Production ( we could allow similar functionality of other stages too) through UI. Thoughts? regards, Ramith On Thu, Dec 19, 2013 at 2:05 PM, Samisa Abeysinghe sam...@wso2.comwrote: So if we deploy an app into production, v1, then it works, then we deploy v2 into production and it does not work, how do we revert back to v1? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 1:50 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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 mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 776715671 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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
Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
Hi Samisa, Having a 'Staging' doesn't seem to solve the problem. let me explain the work flow: V1.build1 is deployed in Production - Devops demote v1.build1 to 'Staging' - Dev ops demote v1.build1 to Testing - QA demote v1.build1 to Development - Developer make changes (and make V1.build2) and promotes to Testing - QA promotes (V1.build2) to Staging (This overwrites V1.build1) - Devops promote V1.build2 to Production - V1.build2 Crashes in Production. @Manjula, If users wants have a work flow (or a development process) where one version of the Application in production at any given time, then we don't need multiple builds per version. Because, when V2 of application goes to production, user can retire V1 (if V2 doesn't work then user can still bring V1 to production again, until V2 is fixed) However, If user needs multiple versions in production then this need arises. thoughts? On Thu, Dec 19, 2013 at 3:42 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi all, Do we need to support v1.build1, v1.build2 like artifacts when we have a version concept already such as v1, v2 ? It seems to me that, having v1.build1, v1,build2 introduces another version concept based on build version on top of v1(source version). thank you. On Thu, Dec 19, 2013 at 3:33 PM, Samisa Abeysinghe sam...@wso2.comwrote: I thought, if we had staging, we have a solution. Because, when v1.build2 goes into production, and fails, there is an already running v1.build1 to which we can transition smoothly. And v1.build1 is guaranteed to work, as that was the version which was in production prior to v1.build2. This is why I asked the original question, if there is no staging, how do we revert in case of failure in build2. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 2:54 PM, Ramith Jayasinghe ram...@wso2.comwrote: Hi Samisa, Having application version v1 in production doesn't effect having v2 also in production. since artifacts of V1 and V2 are two different artifacts ( e.g. myapp-v1.war, myapp-v2.war) that will end up in relevant run time (e.g production app server). In that sense, demoting V2 also doesn't affect V1. How ever, I suspect what's explained above doesn't answer your question. If I understood right, your concern is about how to address the scenario where: user have a one build of the application version V1 ( lets call it V1.build1) working in Production. and for some reason it was demoted all the way back to 'Development'. Then, Developer makes some changes (V1.build2) - promotes to Testing - QA promotes to Production - now Production have V1.build2 - V1.build2 doesn't work in production. We don't have a solution for this right now. A way to solve this would be : 1. AF needs to have the ability to store multiple artifacts/builds of the same version in a storage. (and add notes, dates ,against these artifacts to so users can keep track) 2. Users ( /devops) should be able to deploy one of these artifacts in a Production ( we could allow similar functionality of other stages too) through UI. Thoughts? regards, Ramith On Thu, Dec 19, 2013 at 2:05 PM, Samisa Abeysinghe sam...@wso2.comwrote: So if we deploy an app into production, v1, then it works, then we deploy v2 into production and it does not work, how do we revert back to v1? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 1:50 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- 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 mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com
Re: [Architecture] [Appfactory][Resources] Improve resource creation and Application Life cycle Management
The question is about promoting and demoting build2. For build1 if we deploy and that fails, there is no such scenario of service continuation as there was no service to start with. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 3:53 PM, Ramith Jayasinghe ram...@wso2.com wrote: Hi Samisa, Having a 'Staging' doesn't seem to solve the problem. let me explain the work flow: V1.build1 is deployed in Production - Devops demote v1.build1 to 'Staging' - Dev ops demote v1.build1 to Testing - QA demote v1.build1 to Development - Developer make changes (and make V1.build2) and promotes to Testing - QA promotes (V1.build2) to Staging (This overwrites V1.build1) - Devops promote V1.build2 to Production - V1.build2 Crashes in Production. @Manjula, If users wants have a work flow (or a development process) where one version of the Application in production at any given time, then we don't need multiple builds per version. Because, when V2 of application goes to production, user can retire V1 (if V2 doesn't work then user can still bring V1 to production again, until V2 is fixed) However, If user needs multiple versions in production then this need arises. thoughts? On Thu, Dec 19, 2013 at 3:42 PM, Manjula Rathnayake manju...@wso2.comwrote: Hi all, Do we need to support v1.build1, v1.build2 like artifacts when we have a version concept already such as v1, v2 ? It seems to me that, having v1.build1, v1,build2 introduces another version concept based on build version on top of v1(source version). thank you. On Thu, Dec 19, 2013 at 3:33 PM, Samisa Abeysinghe sam...@wso2.comwrote: I thought, if we had staging, we have a solution. Because, when v1.build2 goes into production, and fails, there is an already running v1.build1 to which we can transition smoothly. And v1.build1 is guaranteed to work, as that was the version which was in production prior to v1.build2. This is why I asked the original question, if there is no staging, how do we revert in case of failure in build2. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 2:54 PM, Ramith Jayasinghe ram...@wso2.comwrote: Hi Samisa, Having application version v1 in production doesn't effect having v2 also in production. since artifacts of V1 and V2 are two different artifacts ( e.g. myapp-v1.war, myapp-v2.war) that will end up in relevant run time (e.g production app server). In that sense, demoting V2 also doesn't affect V1. How ever, I suspect what's explained above doesn't answer your question. If I understood right, your concern is about how to address the scenario where: user have a one build of the application version V1 ( lets call it V1.build1) working in Production. and for some reason it was demoted all the way back to 'Development'. Then, Developer makes some changes (V1.build2) - promotes to Testing - QA promotes to Production - now Production have V1.build2 - V1.build2 doesn't work in production. We don't have a solution for this right now. A way to solve this would be : 1. AF needs to have the ability to store multiple artifacts/builds of the same version in a storage. (and add notes, dates ,against these artifacts to so users can keep track) 2. Users ( /devops) should be able to deploy one of these artifacts in a Production ( we could allow similar functionality of other stages too) through UI. Thoughts? regards, Ramith On Thu, Dec 19, 2013 at 2:05 PM, Samisa Abeysinghe sam...@wso2.comwrote: So if we deploy an app into production, v1, then it works, then we deploy v2 into production and it does not work, how do we revert back to v1? Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Thu, Dec 19, 2013 at 1:50 PM, Manjula Rathnayake manju...@wso2.com wrote: Hi Samisa, Sorry for late reply. On Thu, Dec 19, 2013 at 10:46 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Wed, Dec 11, 2013 at 9:25 PM, Samisa Abeysinghe sam...@wso2.comwrote: So, no staging right? If yes, then where do we roll back to in CI? Yes, No staging, but we have the support of adding, removing stages by configuring it that way. Regarding roll back, if the application is in Production, DevOps can roll back to Testing. Here, application will be undeployed from Production. However, in Testing stage, QA can demote the application without undeploying the application to continue testing. @Ramith, please share any missed information. thank you. PING, I never got a response for my query. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
Re: [Architecture] Meeting Notes { was : Re: Invitation: Carbon 5 User API Design Review}
Hi Prabath, One more suggestion I wanted to tell and missed is, what if we have the Identifier classes of each entity as a static nested class of the corresponding entity? This way it will make the packaging more neat. On Thu, Dec 19, 2013 at 1:26 PM, Prabath Siriwardena prab...@wso2.comwrote: Participants : Azeez, Srinath, Sameera,SameeraP Manoj, Kishanthan,Johann, Venura, Ishara, Chamath, Darshana, Pradeep, Prabath - Overall we agreed on the design. - Separate out IdentityService API in to tow top level APIs - one for store administration and another for user/group/role/permission administration - Authenticated user should be independent from the Authorization Store - JAAS implementation Next steps : - Commit the API code to Git - File based implementation for C5 - Validate the API with further implementations with LDAP/AD - Documentation Will schedule another review in January. Thanks a lot everyone for your time..! Thanks regards, -Prabath On Tue, Dec 17, 2013 at 3:15 PM, Johann Nallathamby joh...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Carbon 5 User API Design Review Carbon 5 User Core API Design - Public Review *When* Thu Dec 19, 2013 11am – 12pm Colombo *Where* LK 5th Floor Meeting Room - Garage (maphttp://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garagehl=en ) *Calendar* prab...@wso2.com *Who* • Johann Nallathamby - organizer • Chamath Gunawardana • architecture@wso2.org • Paul Fremantle • Dimuthu Leelarathne • Darshana Gunawardana • Sameera Jayasoma • Asela Pathberiya • Prabath Siriwardana • Srinath Perera • Afkham Azeez • Sanjiva Weerawarana • Dulanja Liyanage • Sumedha Rubasinghe • Ishara Karunarathna *Attachments* c5-user-core-api-highlevel-design.pnghttps://lh6.googleusercontent.com/DiBqCFm-4bjETgEgayV1xMMJ9zxe-NWrMl2MLEzcBhjGjCf3foc2nDDo8dcHorwC9MdBBBREPSmKrtxsbP-FDMo=s400 Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=1tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=3tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=2tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en* more options »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account prab...@wso2.com because you are subscribed for invitations on calendar prab...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Meeting Notes { was : Re: Invitation: Carbon 5 User API Design Review}
Hi Johann, Why would we need to do that? If we do so we cannot inherit the EntityIdentifier behavior isn't it? Therefore we need to change that in every class if we come across any issues. Can you please provide a sample why we need to add that as a inner class? Regards, Venura On Thu, Dec 19, 2013 at 6:07 PM, Johann Nallathamby joh...@wso2.com wrote: Hi Prabath, One more suggestion I wanted to tell and missed is, what if we have the Identifier classes of each entity as a static nested class of the corresponding entity? This way it will make the packaging more neat. On Thu, Dec 19, 2013 at 1:26 PM, Prabath Siriwardena prab...@wso2.comwrote: Participants : Azeez, Srinath, Sameera,SameeraP Manoj, Kishanthan,Johann, Venura, Ishara, Chamath, Darshana, Pradeep, Prabath - Overall we agreed on the design. - Separate out IdentityService API in to tow top level APIs - one for store administration and another for user/group/role/permission administration - Authenticated user should be independent from the Authorization Store - JAAS implementation Next steps : - Commit the API code to Git - File based implementation for C5 - Validate the API with further implementations with LDAP/AD - Documentation Will schedule another review in January. Thanks a lot everyone for your time..! Thanks regards, -Prabath On Tue, Dec 17, 2013 at 3:15 PM, Johann Nallathamby joh...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Carbon 5 User API Design Review Carbon 5 User Core API Design - Public Review *When* Thu Dec 19, 2013 11am – 12pm Colombo *Where* LK 5th Floor Meeting Room - Garage (maphttp://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garagehl=en ) *Calendar* prab...@wso2.com *Who* • Johann Nallathamby - organizer • Chamath Gunawardana • architecture@wso2.org • Paul Fremantle • Dimuthu Leelarathne • Darshana Gunawardana • Sameera Jayasoma • Asela Pathberiya • Prabath Siriwardana • Srinath Perera • Afkham Azeez • Sanjiva Weerawarana • Dulanja Liyanage • Sumedha Rubasinghe • Ishara Karunarathna *Attachments* c5-user-core-api-highlevel-design.pnghttps://lh6.googleusercontent.com/DiBqCFm-4bjETgEgayV1xMMJ9zxe-NWrMl2MLEzcBhjGjCf3foc2nDDo8dcHorwC9MdBBBREPSmKrtxsbP-FDMo=s400 Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=1tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=3tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=2tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en* more options »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account prab...@wso2.com because you are subscribed for invitations on calendar prab...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Senior Software Engineer Mobile: +94 71 82 300 20 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Meeting Notes { was : Re: Invitation: Carbon 5 User API Design Review}
A nested class should exist only to serve its enclosing class... if the purpose of it goes beyond that - then it should be a top level one. For that reason, I did't want to have Identifier classes as nested classes... Thanks regards, -Prabath On Thu, Dec 19, 2013 at 6:07 PM, Johann Nallathamby joh...@wso2.com wrote: Hi Prabath, One more suggestion I wanted to tell and missed is, what if we have the Identifier classes of each entity as a static nested class of the corresponding entity? This way it will make the packaging more neat. On Thu, Dec 19, 2013 at 1:26 PM, Prabath Siriwardena prab...@wso2.comwrote: Participants : Azeez, Srinath, Sameera,SameeraP Manoj, Kishanthan,Johann, Venura, Ishara, Chamath, Darshana, Pradeep, Prabath - Overall we agreed on the design. - Separate out IdentityService API in to tow top level APIs - one for store administration and another for user/group/role/permission administration - Authenticated user should be independent from the Authorization Store - JAAS implementation Next steps : - Commit the API code to Git - File based implementation for C5 - Validate the API with further implementations with LDAP/AD - Documentation Will schedule another review in January. Thanks a lot everyone for your time..! Thanks regards, -Prabath On Tue, Dec 17, 2013 at 3:15 PM, Johann Nallathamby joh...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Carbon 5 User API Design Review Carbon 5 User Core API Design - Public Review *When* Thu Dec 19, 2013 11am – 12pm Colombo *Where* LK 5th Floor Meeting Room - Garage (maphttp://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garagehl=en ) *Calendar* prab...@wso2.com *Who* • Johann Nallathamby - organizer • Chamath Gunawardana • architecture@wso2.org • Paul Fremantle • Dimuthu Leelarathne • Darshana Gunawardana • Sameera Jayasoma • Asela Pathberiya • Prabath Siriwardana • Srinath Perera • Afkham Azeez • Sanjiva Weerawarana • Dulanja Liyanage • Sumedha Rubasinghe • Ishara Karunarathna *Attachments* c5-user-core-api-highlevel-design.pnghttps://lh6.googleusercontent.com/DiBqCFm-4bjETgEgayV1xMMJ9zxe-NWrMl2MLEzcBhjGjCf3foc2nDDo8dcHorwC9MdBBBREPSmKrtxsbP-FDMo=s400 Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=1tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=3tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=2tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en* more options »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account prab...@wso2.com because you are subscribed for invitations on calendar prab...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Meeting Notes { was : Re: Invitation: Carbon 5 User API Design Review}
Hi Prabath, On Thu, Dec 19, 2013 at 7:56 PM, Prabath Siriwardena prab...@wso2.comwrote: A nested class should exist only to serve its enclosing class... if the purpose of it goes beyond that - then it should be a top level one. For that reason, I did't want to have Identifier classes as nested classes... I was only thinking about the readability aspect and packaging aspect. Otherwise there is no real reason for it. That's why I suggested static nested classes rather than non-static inner classes since they need to have existence without the existence of their enclosing class. May be I am wrong here. Thanks regards, -Prabath On Thu, Dec 19, 2013 at 6:07 PM, Johann Nallathamby joh...@wso2.comwrote: Hi Prabath, One more suggestion I wanted to tell and missed is, what if we have the Identifier classes of each entity as a static nested class of the corresponding entity? This way it will make the packaging more neat. On Thu, Dec 19, 2013 at 1:26 PM, Prabath Siriwardena prab...@wso2.comwrote: Participants : Azeez, Srinath, Sameera,SameeraP Manoj, Kishanthan,Johann, Venura, Ishara, Chamath, Darshana, Pradeep, Prabath - Overall we agreed on the design. - Separate out IdentityService API in to tow top level APIs - one for store administration and another for user/group/role/permission administration - Authenticated user should be independent from the Authorization Store - JAAS implementation Next steps : - Commit the API code to Git - File based implementation for C5 - Validate the API with further implementations with LDAP/AD - Documentation Will schedule another review in January. Thanks a lot everyone for your time..! Thanks regards, -Prabath On Tue, Dec 17, 2013 at 3:15 PM, Johann Nallathamby joh...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Carbon 5 User API Design Review Carbon 5 User Core API Design - Public Review *When* Thu Dec 19, 2013 11am – 12pm Colombo *Where* LK 5th Floor Meeting Room - Garage (maphttp://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garagehl=en ) *Calendar* prab...@wso2.com *Who* • Johann Nallathamby - organizer • Chamath Gunawardana • architecture@wso2.org • Paul Fremantle • Dimuthu Leelarathne • Darshana Gunawardana • Sameera Jayasoma • Asela Pathberiya • Prabath Siriwardana • Srinath Perera • Afkham Azeez • Sanjiva Weerawarana • Dulanja Liyanage • Sumedha Rubasinghe • Ishara Karunarathna *Attachments* c5-user-core-api-highlevel-design.pnghttps://lh6.googleusercontent.com/DiBqCFm-4bjETgEgayV1xMMJ9zxe-NWrMl2MLEzcBhjGjCf3foc2nDDo8dcHorwC9MdBBBREPSmKrtxsbP-FDMo=s400 Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=1tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=3tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=2tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en* more options »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account prab...@wso2.com because you are subscribed for invitations on calendar prab...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com
Re: [Architecture] Meeting Notes { was : Re: Invitation: Carbon 5 User API Design Review}
Yes.. you got a point - it only alters packaging - but, from design point of view, it adds bit confusion - that's why I do not prefer that quite.. Thanks regards, -Prabath On Thu, Dec 19, 2013 at 8:06 PM, Johann Nallathamby joh...@wso2.com wrote: Hi Prabath, On Thu, Dec 19, 2013 at 7:56 PM, Prabath Siriwardena prab...@wso2.comwrote: A nested class should exist only to serve its enclosing class... if the purpose of it goes beyond that - then it should be a top level one. For that reason, I did't want to have Identifier classes as nested classes... I was only thinking about the readability aspect and packaging aspect. Otherwise there is no real reason for it. That's why I suggested static nested classes rather than non-static inner classes since they need to have existence without the existence of their enclosing class. May be I am wrong here. Thanks regards, -Prabath On Thu, Dec 19, 2013 at 6:07 PM, Johann Nallathamby joh...@wso2.comwrote: Hi Prabath, One more suggestion I wanted to tell and missed is, what if we have the Identifier classes of each entity as a static nested class of the corresponding entity? This way it will make the packaging more neat. On Thu, Dec 19, 2013 at 1:26 PM, Prabath Siriwardena prab...@wso2.comwrote: Participants : Azeez, Srinath, Sameera,SameeraP Manoj, Kishanthan,Johann, Venura, Ishara, Chamath, Darshana, Pradeep, Prabath - Overall we agreed on the design. - Separate out IdentityService API in to tow top level APIs - one for store administration and another for user/group/role/permission administration - Authenticated user should be independent from the Authorization Store - JAAS implementation Next steps : - Commit the API code to Git - File based implementation for C5 - Validate the API with further implementations with LDAP/AD - Documentation Will schedule another review in January. Thanks a lot everyone for your time..! Thanks regards, -Prabath On Tue, Dec 17, 2013 at 3:15 PM, Johann Nallathamby joh...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Carbon 5 User API Design Review Carbon 5 User Core API Design - Public Review *When* Thu Dec 19, 2013 11am – 12pm Colombo *Where* LK 5th Floor Meeting Room - Garage (maphttp://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garagehl=en ) *Calendar* prab...@wso2.com *Who* • Johann Nallathamby - organizer • Chamath Gunawardana • architecture@wso2.org • Paul Fremantle • Dimuthu Leelarathne • Darshana Gunawardana • Sameera Jayasoma • Asela Pathberiya • Prabath Siriwardana • Srinath Perera • Afkham Azeez • Sanjiva Weerawarana • Dulanja Liyanage • Sumedha Rubasinghe • Ishara Karunarathna *Attachments* c5-user-core-api-highlevel-design.pnghttps://lh6.googleusercontent.com/DiBqCFm-4bjETgEgayV1xMMJ9zxe-NWrMl2MLEzcBhjGjCf3foc2nDDo8dcHorwC9MdBBBREPSmKrtxsbP-FDMo=s400 Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=1tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=3tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQrst=2tok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en* more options »https://www.google.com/calendar/event?action=VIEWeid=bTh1ZmxrY2p0YmlhaDcwZm51MDJvYnJoaWsgcHJhYmF0aEB3c28yLmNvbQtok=MTUjam9oYW5uQHdzbzIuY29tZjI0MmRkYzUxYWI1ZGViMWRlZDU4ZjdkZWZiNzkzODdiNzNmMWQ4Nwctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account prab...@wso2.com because you are subscribed for invitations on calendar prab...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732
[Architecture] [C5 ] What is the Carbon -Tomcat integration approach ?
I'm not quite sure whether we have already define the architectural
approach for ${Subject} in either way I have some inputs about
${Subject} from AS point of view.
If you go through Tomcat changelog[1] doc you can understand it's vital to
upgrade Tomcat version with AS releases when ever possible. Right now it's
required to do a new Kernal release or maintains a Kernal patch to upgrade
Tomcat version, it would be better if we can find a solid approach for this
from C5.
1.) My first suggestion is it would be great if we can move Tomcat out of
the Kernal but I'm not sure about the feasibility of doing this. WDYT ?
is this something possible ?
2.) If 1st option is not possible it would be nice if we can come up with a
architecture which facilitate to plug/change Tomcat version at
platform/product level. Say Kernal ships with a default Tomcat version
while there is a standard hook to plug custom Tomcat version while building
products. AFAIK other than AS other products can depends on Kernal's Tomcat
version. Only drawback is sometime AS can use one Tomcat version while
rest of the platform use another Tomcat version but compare to maintaining
cost for Kernal patch I'm OK to do this.
3.) Since we are expecting C5 remains for many years it would be better to
use Tomcat8 instead of Tomcat7. Tomcat8 RC packs already there but the
time of C5 1.0 releases happen Tomcat8 GA releases should be there.
Otherwise after 1 or 2 years we have to do a major upgrade.
[1] - http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
[2] - http://tomcat.apache.org/download-80.cgi
Thanks !
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
