Re: [Architecture] SSO Quick Start Guide for AS6
Hi KasunG, You can get the AS 6.0.0-m3 pack[2] and inside the samples directory you can find the sso-quickstart. Inside the sso-quickstart directory, you can find the readme file[3] which explains how to run the quickstart. [2] https://github.com/wso2/product-as/releases/tag/v6.0.0-m3 [3] https://github.com/wso2/product-as/blob/v6.0.0-m3/samples/appserver-sso-samples/sso-quickstart/README.md Thanks, Chanaka. On Tue, Sep 6, 2016 at 12:06 PM, KasunG Gajasinghe <kas...@wso2.com> wrote: > Hi Chanaka, > > Where can I find the guide to run the quickstart? > > Thanks. > > On Tue, Sep 6, 2016 at 11:35 AM, Chanaka Cooray <chana...@wso2.com> wrote: > >> Hi, >> >> From WSO2 Application Server(AS) 6.0.0-m3 onwards, it >> supports Single-Sign-On (SSO) for web applications with WSO2 Identity >> Server(IS). In addition to that, we are in the process of implementing >> $subject to demonstrate SSO functionality in AS 6.0.0 to the user with >> minimum configuration. >> >> The user would be able to run the sample by just running the script >> instead of going through the whole SSO documentation[1] to configure the >> SSO feature. The script is supposed to do the following things in order to >> configure the sample. >> >>- Configurations in both AS and IS >> - configure wso2as-web.xml and server.xml files in AS >> - configure service providers in IS >>- Deploy the SSO samples in AS >> - deploy two sample web apps in the web apps directory >>- Start the two servers (AS and IS) >>- Create a new user in IS to log into the web apps >> - using real world username and password will be more effective >> for a sample than the default admin user. >> >> Addition to this script, we provide another script to clean the >> configuration changes made in the main script. By running the clean script, >> the user would be able to bring the default configurations in the AS. >> >> [1] https://docs.wso2.com/display/AS600/Accessing+Applicatio >> ns+using+Single+Sign-On >> >> Thanks, >> Chanaka. >> -- >> Chanaka Cooray >> Software Engineer, WSO2 Inc. http://wso2.com >> Email: chana...@wso2.com >> Mobile: +94713149860 >> <https://wso2.com/signature> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] SSO Quick Start Guide for AS6
Hi, >From WSO2 Application Server(AS) 6.0.0-m3 onwards, it supports Single-Sign-On (SSO) for web applications with WSO2 Identity Server(IS). In addition to that, we are in the process of implementing $subject to demonstrate SSO functionality in AS 6.0.0 to the user with minimum configuration. The user would be able to run the sample by just running the script instead of going through the whole SSO documentation[1] to configure the SSO feature. The script is supposed to do the following things in order to configure the sample. - Configurations in both AS and IS - configure wso2as-web.xml and server.xml files in AS - configure service providers in IS - Deploy the SSO samples in AS - deploy two sample web apps in the web apps directory - Start the two servers (AS and IS) - Create a new user in IS to log into the web apps - using real world username and password will be more effective for a sample than the default admin user. Addition to this script, we provide another script to clean the configuration changes made in the main script. By running the clean script, the user would be able to bring the default configurations in the AS. [1] https://docs.wso2.com/display/AS600/Accessing+Applications+using+Single+Sign-On Thanks, Chanaka. -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] WSO2 Application Server 6.0.0-M3 Released !
WSO2 Application Server 6.0.0-M3 Released ! WSO2 Application Server 6.0.0 is the successor of the WSO2 Carbon based Application Server. It is a complete revamp and is based on vanilla Apache Tomcat 8. WSO2 provides a number of features by means of extensions to Apache Tomcat to integrate it with rest of the products of the WSO2 Carbon middleware platform. It provides first class support for generic web applications, JAX-RS/JAX-WS web applications and jaggery applications. The performance of the server and individual application can be monitored by integrating WSO2 Application Server with WSO2 Data Analytics Server. WSO2 Application Server is an open source project and it is available under the Apache Software License (v2.0) <http://www.apache.org/licenses/LICENSE-2.0.html>. Source and product distribution for this release is available here <https://github.com/wso2/product-as/releases/tag/v6.0.0-m3>. New Features - [WSAS-2191 <https://wso2.org/jira/browse/WSAS-2191>] - SAML 2.0 based Single-Sign-On (SSO) Apache Tomcat valve WSO2 Application Server now supports SSO for web applications with WSO2 Identity Server. We have introduced the SSO Quick Start <https://github.com/wso2/product-as/tree/v6.0.0-m3/samples/appserver-sso-samples/sso-quickstart> script to try out SSO functionality with one go. - [WSAS-2250 <https://wso2.org/jira/browse/WSAS-2250>] - Jaggery runtime support With this release of WSO2 Application Server we have introduced the Jaggery runtime. Jaggery applications can be deployed with this custom runtime. Improvements - [WSAS-2235 <https://wso2.org/jira/browse/WSAS-2235>] - Change the names of appserver-utils module classes into meaningful names with less confusion - [WSAS-2237 <https://wso2.org/jira/browse/WSAS-2237>] - Change of the location of the WSO2 AS web application descriptor, within a web application - [WSAS-2244 <https://wso2.org/jira/browse/WSAS-2244>] - Adding test cases for validating security related system properties. - [WSAS-2251 <https://wso2.org/jira/browse/WSAS-2251>] - SSO QuickStart Guide Tasks - [WSAS-2229 <https://wso2.org/jira/browse/WSAS-2229>] - Add a feature to test failing test cases in the integration tests - [WSAS-2230 <https://wso2.org/jira/browse/WSAS-2230>] - Merge jacoco integration test coverage reports - [WSAS-2242 <https://wso2.org/jira/browse/WSAS-2242>] - Update client-truststore.jks with the latest - [WSAS-2246 <https://wso2.org/jira/browse/WSAS-2246>] - Get rid of org.wso2.carbon.logging-4.4.3.jar in /lib - [WSAS-2252 <https://wso2.org/jira/browse/WSAS-2252>] - Set https enabled by default in server.xml - [WSAS-2253 <https://wso2.org/jira/browse/WSAS-2253>] - Shade commons-logging and log4j jars Key Features - HTTP Statistics Publishing to WSO2 Data Analytics Server - SAML based Single Sign On (SSO) for web applications - Support for Jaggery applications deployment - Webapp classloading runtimes Reporting Issues Issues, documentation errors and feature requests regarding WSO2 Application Server can be reported through the public issue tracking system. https://wso2.org/jira/browse/WSAS. Contact us WSO2 Application Server developers can be contacted via the Development <d...@wso2.org> and Architecture <architecture@wso2.org> mailing lists. Alternatively, questions can also be raised in the stackoverflow forum : http://stackoverflow.com/questions/tagged/wso2 Thank you for your interest in WSO2 Application Server. -The WSO2 Application Server Development Team - On Mon, Aug 1, 2016 at 11:10 AM, Chanaka Cooray <chana...@wso2.com> wrote: > WSO2 Application Server 6.0.0-M3 Released ! > Welcome to WSO2 Application Server, the successor of WSO2 Carbon based > Application Server. WSO2 Application Server 6.0.0 is a complete revamp and > is based on vanilla Apache Tomcat. WSO2 provides a number of features by > means of extensions to Tomcat to add/enhance the functionality. It provides > first class support for generic web applications, JAX-RS/JAX-WS web > applications and jaggery applications. The performance of the server and > individual application can be monitored by integrating WSO2 Application > Server with WSO2 Data Analytics Server. > > WSO2 Application Server is an open source project and it is available > under the Apache Software License (v2.0) > <http://www.apache.org/licenses/LICENSE-2.0.html>. > > Source and product distribution for this release is available here > <https://github.com/wso2/product-as/releases/tag/v6.0.0-m3>. > Key Features > >- HTTP Statistics Monitoring >- Webapp Classloading Runtimes >- Jaggery Runtime Support >- Accessing Applications using Single Sign-On &
[Architecture] WSO2 Application Server 6.0.0-M3 Released !
WSO2 Application Server 6.0.0-M3 Released ! Welcome to WSO2 Application Server, the successor of WSO2 Carbon based Application Server. WSO2 Application Server 6.0.0 is a complete revamp and is based on vanilla Apache Tomcat. WSO2 provides a number of features by means of extensions to Tomcat to add/enhance the functionality. It provides first class support for generic web applications, JAX-RS/JAX-WS web applications and jaggery applications. The performance of the server and individual application can be monitored by integrating WSO2 Application Server with WSO2 Data Analytics Server. WSO2 Application Server is an open source project and it is available under the Apache Software License (v2.0) <http://www.apache.org/licenses/LICENSE-2.0.html>. Source and product distribution for this release is available here <https://github.com/wso2/product-as/releases/tag/v6.0.0-m3>. Key Features - HTTP Statistics Monitoring - Webapp Classloading Runtimes - Jaggery Runtime Support - Accessing Applications using Single Sign-On Fixed Issues - https://wso2.org/jira/browse/WSAS-2194?filter=13173 Known Issues - https://wso2.org/jira/browse/WSAS-2248?filter=13174 Reporting Issues Issues, documentation errors and feature requests regarding WSO2 Application Server can be reported through the public issue tracking system. https://wso2.org/jira/browse/WSAS. Contact usWSO2 Application Server developers can be contacted via the Development and Architecture mailing lists. Alternatively, questions can also be raised in the stackoverflow forum : http://stackoverflow.com/questions/tagged/wso2 Thank you for your interest in WSO2 Application Server. *-The WSO2 Application Server Development Team -* -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server
;>>>>>>> apache tomcat server. So this will improve the flexibility of the >>>>>>>> jaggery >>>>>>>> apps. >>>>>>>> >>>>>>>> This is an extension for the Apache tomcat 8 to run the jaggery app >>>>>>>> without modifying it. Although this is implemented as a requirement of >>>>>>>> WSO2 >>>>>>>> Application Server 6, Users who want to run jaggery apps without >>>>>>>> jaggery >>>>>>>> server, can use this feature to run their jaggery apps in Apache tomcat >>>>>>>> server. >>>>>>>> >>>>>>>> I have attached the documentation and sample jaggery with this >>>>>>>> email. Please find these attachments and relevant jaggery branch >>>>>>>> here[1]. >>>>>>>> Please feel free to ask any questions. >>>>>>>> >>>>>>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Nisala >>>>>>>> >>>>>>>> -- >>>>>>>> *Nisala Niroshana Nanayakkara,* >>>>>>>> Software Engineer >>>>>>>> Mobile:(+94)717600022 >>>>>>>> WSO2 Inc., http://wso2.com/ >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> d...@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >>>>>>> email: kasung AT spamfree wso2.com >>>>>>> linked-in: http://lk.linkedin.com/in/gajasinghe >>>>>>> blog: http://kasunbg.org >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Nisala Niroshana Nanayakkara,* >>>>>> Software Engineer >>>>>> Mobile:(+94)717600022 >>>>>> WSO2 Inc., http://wso2.com/ >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> d...@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Sinthuja Rajendran* >>>>> Technical Lead >>>>> WSO2, Inc.:http://wso2.com >>>>> >>>>> Blog: http://sinthu-rajan.blogspot.com/ >>>>> Mobile: +94774273955 >>>>> >>>>> >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Manjula Rathnayaka >>>> Associate Technical Lead >>>> WSO2, Inc. >>>> Mobile:+94 77 743 1987 >>>> >>> >>> >>> >>> -- >>> *Nisala Niroshana Nanayakkara,* >>> Software Engineer >>> Mobile:(+94)717600022 >>> WSO2 Inc., http://wso2.com/ >>> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > Manjula Rathnayaka > Associate Technical Lead > WSO2, Inc. > Mobile:+94 77 743 1987 > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [C5] Upgrading Kernel Equinox version to Neon Releases
Hi KasunG, I have tested the carbon-feature-plugin and the kernel with the new upgrades and sent two PRs for both repos. But at first, as you said, carbon feature plugin has to be released in order to move the kernel to Neon release because neon plugins don't work with the old versions of tycho. Thanks, Chanaka. On Wed, Jul 6, 2016 at 11:42 AM, KasunG Gajasinghe <kas...@wso2.com> wrote: > > Chanaka, let's test the fix for carbon-feature-plugin, and go for an > immediate release. Kernel version upgrade can be followed after that. > > On Wed, Jul 6, 2016 at 11:39 AM, KasunG Gajasinghe <kas...@wso2.com> > wrote: > >> >> +1. It's good that we identified the issues that has previously prevented >> us updating to latest Equinox version. >> >> Thanks, >> KasunG >> >> On Tue, Jul 5, 2016 at 7:57 PM, Niranjan Karunanandham <niran...@wso2.com >> > wrote: >> >>> +1 to upgrade the tycho plugin. Currently we are using 0.13.0 and AFAIR >>> the latest one is 0.25.0. >>> >>> Regards, >>> Nira >>> >>> On Tue, Jul 5, 2016 at 3:11 PM, Sameera Jayasoma <same...@wso2.com> >>> wrote: >>> >>>> +1 for this. >>>> >>>> On Tue, Jul 5, 2016 at 2:48 PM, Chanaka Cooray <chana...@wso2.com> >>>> wrote: >>>> >>>>> [+architecture] >>>>> >>>>> On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray <chana...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> We have decided to upgrade the equinox version in kernel to Neon >>>>>> release which is the latest release of the equinox[1]. This has to be >>>>>> done >>>>>> due to several issues in kernel including [2] with the current equinox >>>>>> version. >>>>>> Addition to that, it is also required to upgrade tycho versions in >>>>>> carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8. >>>>>> >>>>>> [1] http://download.eclipse.org/equinox/ >>>>>> [2] https://wso2.org/jira/browse/CARBON-15976 >>>>>> [3] https://github.com/wso2/carbon-maven-plugins >>>>>> >>>>>> Thanks, >>>>>> Chanaka. >>>>>> -- >>>>>> Chanaka Cooray >>>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>>> Email: chana...@wso2.com >>>>>> Mobile: +94713149860 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Chanaka Cooray >>>>> Software Engineer, WSO2 Inc. http://wso2.com >>>>> Email: chana...@wso2.com >>>>> Mobile: +94713149860 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sameera Jayasoma, >>>> Software Architect, >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: same...@wso2.com >>>> blog: http://blog.sameera.org >>>> twitter: https://twitter.com/sameerajayasoma >>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>> Mobile: 0094776364456 >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> >>> *Niranjan Karunanandham* >>> Associate Technical Lead - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > > *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [C5] Upgrading Kernel Equinox version to Neon Releases
[+architecture] On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray <chana...@wso2.com> wrote: > Hi all, > > We have decided to upgrade the equinox version in kernel to Neon release > which is the latest release of the equinox[1]. This has to be done due to > several issues in kernel including [2] with the current equinox version. > Addition to that, it is also required to upgrade tycho versions in > carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8. > > [1] http://download.eclipse.org/equinox/ > [2] https://wso2.org/jira/browse/CARBON-15976 > [3] https://github.com/wso2/carbon-maven-plugins > > Thanks, > Chanaka. > -- > Chanaka Cooray > Software Engineer, WSO2 Inc. http://wso2.com > Email: chana...@wso2.com > Mobile: +94713149860 > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [C5] [OSGi] Pax Exam Container for Carbon 5 - In-Container Testing
Hi all, POC level implementation for the pax exam container has been completed for now. So we have discussed the following requirements as the initial step of the container implementation. - Should be able to provide local zip file or a maven distribution or an unpacked directory as the distribution for the container. - Target path(unpack directory) as optional, if not specified create a random folder for the distribution. - Create a pax exam feature for the kernal. - Migrate all the Carbon kernel OSGi tests to this new CarbonTestContainer. - create a C5 test distribution with that feature and custom config files if there are any. E.g. wso2carbon-kernel-test-5.1.0.zip - Check on PerClass, PerMethod, PerSuite exam reactor strategies. - Code coverage with jacoco. Thanks, Chanaka. On Tue, May 17, 2016 at 4:59 PM, Chanaka Cooray <chana...@wso2.com> wrote: > Hi all, > > I'm trying to implement the pax exam container for C5. I'm going to > implement the container like the existing Karaf container in pax exam[1]. > So initially there has to be two implementations of "TestContainer" and > "TestContainerFactory" interfaces in pax exam. Currently I'm working on > those. But this is still a POC level implementation. > > [1]. https://ops4j1.jira.com/wiki/display/PAXEXAM4/Karaf+Container > > Thanks, > Chanaka. > > On Sat, May 14, 2016 at 6:20 AM, Dharshana Warusavitharana < > dharsha...@wso2.com> wrote: > >> Hi, Manu/Sameera. >> >> In any case, OSGI Container based tests won't be unit tests. And if any >> test integrates more than one unit it would be an integration test in >> theory. But we cannot stick to hard and fast rules. Yes, I'm also against >> to the point calling PaxExan test are unit tests. But we have to use them >> to test our containerized platform. So we have to give guys the option to >> write a PaxExan test only and only if it could not be covered by a java >> level unit test. But at some point mocking becomes really expensive we have >> to use alternative paths , sometimes violating some basics. >> >> At the moment MB team is doing a great job maintaining good discipline in >> adding tests. Other teams must come to that level and be active and >> discuss before adding PaxEam tests. >> >> But what Sameera initiates here is different from both existing unit test >> and PaxExam tests. It should come under the feature level, not component >> level. So that we can test each feature basic functionalities like whether >> feature starts correctly with the base carbon features. Whether all ports >> are exposed as expected so on. >> >> My point here is we need some mechanism to say this bundle is working and >> activated correctly before it gets deployed in final product pack. So as my >> understanding this is not a unit test. But this will cover the feature >> level before we build up the final pack and test whole scenario in >> production like platform. >> >> Thank you, >> Dharshana. >> >> On Sat, May 14, 2016 at 12:15 AM, Manuranga Perera <m...@wso2.com> wrote: >> >>> In my view, >>> >>> A test is not a unit test if: >>>> >>>>- It talks to the database >>>>- It communicates across the network >>>>- It touches the file system >>>>- It can't run at the same time as any of your other unit tests >>>>- You have to do special things to your environment (such as >>>>editing config files) to run it. [1] >>>> >>>> But I am not saying integration tests are bad or anything. We need >>> integration tests, and PAX is a good way to do that. But those are >>> integration tests. >>> >>> >>> [1] http://www.artima.com/weblogs/viewpost.jsp?thread=126923 >>> >>> On Fri, May 13, 2016 at 2:11 PM, Sameera Jayasoma <same...@wso2.com> >>> wrote: >>> >>>> Manu, >>>> >>>> You are missing the whole point here. Just because we copy a file in >>>> our tests, they don't become integration tests. Can you tell me what an >>>> integration test from your understanding? >>>> >>>> We do not need to copy files and hard-code OSGi bundles once this Pax >>>> Exam container for Carbon 5 is available. >>>> >>>> On Fri, May 13, 2016 at 10:48 PM, Manuranga Perera <m...@wso2.com> >>>> wrote: >>>> >>>>> Hi Dharshana, >>>>> >>>>>> Avoid product teams to overuse containers to make it to the >>>
Re: [Architecture] [C5] [OSGi] Pax Exam Container for Carbon 5 - In-Container Testing
>>> Mobile: 0094776364456 >>> >>> Lean . Enterprise . Middleware >>> >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : m...@wso2.com >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Dharshana Warusavitharana > Senior Software Engineer , Test Automation > WSO2 Inc. http://wso2.com > email : dharsha...@wso2.com <dharsha...@wso2.com> > Tel : +94 11 214 5345 > Fax :+94 11 2145300 > cell : +94770342233 > blog : http://dharshanaw.blogspot.com > > lean . enterprise . middleware > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Introducing LDAP support to C5 carbon-datasources
Hi Omindu, Properties like retry interval and maximum retries are not standard LDAP connection initialization properties. We have to plug those functionalities externally. IMO, only standard LDAP connection initialization properties should have to be included at the datasource level. Thanks, Chanaka. On Mon, May 9, 2016 at 6:49 PM, Omindu Rathnaweera <omi...@wso2.com> wrote: > What will be the ideal place to include properties like retry interval and > maximum retries ? At the datasource level or the user-store configs level ? > > Regards, > Omindu. > > On Thu, May 5, 2016 at 11:09 AM, Chanaka Cooray <chana...@wso2.com> wrote: > >> Hi all, >> >> We are in the process of adding LDAP connection support >> to carbon-datasources [1]. In c4, all the LDAP connection initialization >> properties and user store properties are managed in user-mgt.xml. Refer >> the ReadWriteLDAPUserStoreManager in user-mgt.xml[2]. So the purpose of >> this is to separate out connection initialization details and manage them >> in carbon-datasource[1]. >> >> In LDAP, all the connection handling, operations are done using a >> DirContext [3]. But we have to create a DirContext every time when we have >> to do a LDAP operation. So we can not register a single instance of >> DirContext using JNDI. So according to the last discussion, we thought of >> registering a bean which includes LDAP connection initialization details >> instead of registering a connection source. So if someone wants to create a >> LDAP connection, they can get that bean using JNDI and create the LDAP >> Connection source using that bean. >> >> [1] https://github.com/wso2/carbon-datasources >> [2] >> https://github.com/wso2/carbon-kernel/blob/4.4.x/distribution/kernel/carbon-home/repository/conf/user-mgt.xml >> [3] >> https://docs.oracle.com/javase/7/docs/api/javax/naming/directory/DirContext.html >> >> Here are the connection parameters. >> >> >>- >> >>Connection initialization properties >> >> >> >> >> >> >> >> >> >> >> >> >>- >> >>DNS related properties >> >> >> >> >> >> >> >> >>- >> >>Connection pooling properties >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>- >> >>Additional Properties >> >> >> >> >> >> >> >> >> >> Thanks, >> >> Chanaka. >> -- >> Chanaka Cooray >> Software Engineer, WSO2 Inc. http://wso2.com >> Email: chana...@wso2.com >> Mobile: +94713149860 >> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Omindu Rathnaweera > Software Engineer, WSO2 Inc. > Mobile: +94 771 197 211 > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Introducing LDAP support to C5 carbon-datasources
Hi all, We are in the process of adding LDAP connection support to carbon-datasources [1]. In c4, all the LDAP connection initialization properties and user store properties are managed in user-mgt.xml. Refer the ReadWriteLDAPUserStoreManager in user-mgt.xml[2]. So the purpose of this is to separate out connection initialization details and manage them in carbon-datasource[1]. In LDAP, all the connection handling, operations are done using a DirContext [3]. But we have to create a DirContext every time when we have to do a LDAP operation. So we can not register a single instance of DirContext using JNDI. So according to the last discussion, we thought of registering a bean which includes LDAP connection initialization details instead of registering a connection source. So if someone wants to create a LDAP connection, they can get that bean using JNDI and create the LDAP Connection source using that bean. [1] https://github.com/wso2/carbon-datasources [2] https://github.com/wso2/carbon-kernel/blob/4.4.x/distribution/kernel/carbon-home/repository/conf/user-mgt.xml [3] https://docs.oracle.com/javase/7/docs/api/javax/naming/directory/DirContext.html Here are the connection parameters. - Connection initialization properties - DNS related properties - Connection pooling properties - Additional Properties Thanks, Chanaka. -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: chana...@wso2.com Mobile: +94713149860 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Operation Center
Hi all,
We are working on the WSO2 Operations Center project. Currently, OC web app
is deployed with a Jaggery API. Recently the UI part was separated from the
web app and data are exposed to different gadgets. And also there may be
performance issues in the future if we continue with Jaggery
implementation. As an initial step,we are going to replace Jaggery API with
JAX-RS.
There are two main interfaces,where the OCAgent is communicating with the
internal API and publishing data to external UI or ues gadgets via external
API.
I am working on the external API part. Here are the improvements done up to
now.
Currently I have implemented 3 rest calls in the external API.
*1. GET oc/servers*
Returns a JSON array containing the data of all servers.
*2. GET oc/servers/{server-id}*
Returns a JSON object containing the data of the specific server
*3. PUT oc/servers/{server-id}/commands/{command-id}*
This rest is used to execute a command using the UI interface. Currently we
have only 4 commands.
1.FORCE_SHUTDOWN
2.FORCE_RESTART
3.GRACEFUL_SHUTDOWN
4.GRACEFUL_RESTART
These commands are sent to the server as a response of the synchronization
message.
Thanks,
--
*Chanaka Sampath Cooray*
Software Engineering Intern,
WSO2 Lanka (pvt) Ltd.
Mobile:+94713614884
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Building WSO2 Carbon4-Kernel in Java 7 and Java 8
Hi, There is only one module[1] shows unit test failures in carbon 4.4.0-SNAPSHOT for java 7 and java 8. So far we've identified the test failures in the classes CommentsTest and HandlerTest in the module[1]. But there may be test failures in other test classes in the module[1] as well. And also there are integration test failures in the module[2]. We are working on that. [1] WSO2 Carbon - Registry Kernel [2] WSO2 Carbon - Integration Test Module(org.wso2.carbon.integration.test-new) Thanks, On Fri, Feb 13, 2015 at 4:57 PM, Chanaka Cooray chana...@wso2.com wrote: Hi all, We are trying to build Carbon4-Kernel to be compatible with Java 7,8. We've managed to fix all the test failures and compilation failures in wso2-axiom, wso2-axis2 and wso2-wss4j in Java 7 and Java 8. For the carbon4-kernel we fixed all the compilation failures in Java 7,8. But there are some test case failures we need to deal with. We disabled the axiom-osgi and axis2-osgi modules since those are not used in carbon4-kernel. And also for Java 8 there are some test failures in axis2-jibx module because they have not updated the JiBX version for Java 8 yet. So we removed that module from the axis2 as well. But that won't be a problem since JiBX is not used in carbon4-kernel. So the summary so far, 1. wso2-axiom - Fixed to build in java 7 and java 8 successfully.(Removed axiom-osgi module) 2. wso2-axis2 - Fixed to build in java 7 and java 8 successfully. (Removed axis2-osgi and axis2-jibx modules) 3. wso2-wss4j - Fixed to build in java 7 and java 8 successfully. 4. carbon4-kernel - Fixed to build in Java 7 and 8, but there are test failures for both versions. Suggestions and feedbacks are appreciated. Thanks, -- *Chanaka Sampath Cooray* Software Engineering Intern, WSO2 Lanka (pvt) Ltd. Mobile:+94713614884 -- *Chanaka Sampath Cooray* Software Engineering Intern, WSO2 Lanka (pvt) Ltd. Mobile:+94713614884 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Building WSO2 Carbon4-Kernel in Java 7 and Java 8
Hi all, We are trying to build Carbon4-Kernel to be compatible with Java 7,8. We've managed to fix all the test failures and compilation failures in wso2-axiom, wso2-axis2 and wso2-wss4j in Java 7 and Java 8. For the carbon4-kernel we fixed all the compilation failures in Java 7,8. But there are some test case failures we need to deal with. We disabled the axiom-osgi and axis2-osgi modules since those are not used in carbon4-kernel. And also for Java 8 there are some test failures in axis2-jibx module because they have not updated the JiBX version for Java 8 yet. So we removed that module from the axis2 as well. But that won't be a problem since JiBX is not used in carbon4-kernel. So the summary so far, 1. wso2-axiom - Fixed to build in java 7 and java 8 successfully.(Removed axiom-osgi module) 2. wso2-axis2 - Fixed to build in java 7 and java 8 successfully. (Removed axis2-osgi and axis2-jibx modules) 3. wso2-wss4j - Fixed to build in java 7 and java 8 successfully. 4. carbon4-kernel - Fixed to build in Java 7 and 8, but there are test failures for both versions. Suggestions and feedbacks are appreciated. Thanks, -- *Chanaka Sampath Cooray* Software Engineering Intern, WSO2 Lanka (pvt) Ltd. Mobile:+94713614884 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
