Re: [Carbon-dev] WSO2 Committers += Chamath
Congratulations!! Regards Buddhika On Tue, Feb 14, 2012 at 1:38 PM, Tharindu Mathew thari...@wso2.com wrote: Hi Chamath, It's my pleasure to welcome you aboard as a WSO2 committer! Thank you for your contributions and hope you continue on your good work -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Upcoming Carbon 4.0.0 Release
Hi devs, Please find the work items of upcoming carbon core release. New Features === Tomcat OSGification - Pradeep/Dileepa - In Progress JVM Autoscalling - Nirmal/Azeez - In Progress CPU/Memoary usage per Tenant - Dimuthu/AmilaM/Amani - In Research Versioning Support for CAPP - Pradeep/Dileepa - Not started Ground work for Admin Service Security Framework - AmilaJ - In Progress Ground work for Admin Service - Shared Schema / JaxWS - Sagara - In Progress Ground work for Tenant partisioning - Sanjeewa/Ashansa/Azeez - Will start Ground work for Tenant aware load balancing - Sanjeewa/Ashansa/Azeez - Will start P2 feature improvement - Pradeep - Will start Other required work == SVN restructuring - Sameera/Pradeep - In Progress Upgrading orbit bundles to new version - Core - ??? - Need to start Caching issues - Senaka/DimuthuL Automated testing - Krishantha Clustering problems - Sanjeewa Exclude Dependencies in Core - ??? - Need to start Identify Carbon Core JIRAs to be fixed - DimuthuL We will copy the core build to specific location every Wednesday/Friday and send a mail. We also copy AS - ESB - Greg for QA. Our target is to release by end of March. thanks, dimuthul -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] WSO2 Committers += Chamath
Thanks.. :) I'll do my best.. On Tue, Feb 14, 2012 at 1:44 PM, Buddhika Chamith buddhi...@wso2.comwrote: Congratulations!! Regards Buddhika On Tue, Feb 14, 2012 at 1:38 PM, Tharindu Mathew thari...@wso2.comwrote: Hi Chamath, It's my pleasure to welcome you aboard as a WSO2 committer! Thank you for your contributions and hope you continue on your good work -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- _-_-_-_-_-_-_-_-_-_ Thanks Regards, Chamath. *+94 71 532 0009* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel-Orbit #6 was SUCCESSFUL. Change made by pradeep.
--- Carbon-Kernel Carbon-Kernel-Orbit #6 was successful. --- Code has been updated by pradeep. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONKERNELBUILD-6/ -- Code Changes -- pradeep (120759): adding the tomcat orbit bundle pradeep (120760): adding javax-servlet orbit bundle that provides servlet API 3.0 to carbon env. But the exported version is set to 2.4 for the moment since this breaks hard imports -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Upcoming Carbon 4.0.0 Release
On Tue, Feb 14, 2012 at 1:46 PM, Dimuthu Leelarathne dimut...@wso2.comwrote: Hi devs, Please find the work items of upcoming carbon core release. New Features === Tomcat OSGification - Pradeep/Dileepa - In Progress JVM Autoscalling - Nirmal/Azeez - In Progress CPU/Memoary usage per Tenant - Dimuthu/AmilaM/Amani - In Research Versioning Support for CAPP - Pradeep/Dileepa - Not started Ground work for Admin Service Security Framework - AmilaJ - In Progress Ground work for Admin Service - Shared Schema / JaxWS - Sagara - In Progress Ground work for Tenant partisioning - Sanjeewa/Ashansa/Azeez - Will start Ground work for Tenant aware load balancing - Sanjeewa/Ashansa/Azeez - Will start P2 feature improvement - Pradeep - Will start Other required work == SVN restructuring - Sameera/Pradeep - In Progress Upgrading orbit bundles to new version - Core - ??? - Need to start Caching issues - Senaka/DimuthuL Automated testing - Krishantha Clustering problems - Sanjeewa Exclude Dependencies in Core - ??? - Need to start Identify Carbon Core JIRAs to be fixed - DimuthuL We will copy the core build to specific location every Wednesday/Friday and send a mail. We also copy AS - ESB - Greg for QA. Our target is to release by end of March. When do we plan to feature complete? When would be the code freeze. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Cleaning up Carbon Authenticator Framework
Hi All, We had a review discussion on Carbon Authenticators and following are the review notes. 1. There are some common logic that should be implemented in every authenticator. Currently invoking this logic is duplicated among authenticators. So to avoid that we are planning to come up with an abstract Authenticator implementation. 2. As per now AuthenticationHandler first invokes AuthenticationAdmin and then it calls chain of authenticators. The AuthenticationAdmin call is not necessary. We need to refactor code in such a way that authenticator it self will only handle authenticating logic (Rather than within the Handler). 3. Properly implement authenticator chaining pattern. Make use “isHandle”, “priority”, “isAuthenticated” methods and make only authenticator aware about the logic. 4. After cleaning up the API, implement “Basic Auth” authenticator. (As first step) Thanks AmilaJ -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Mapping custom Context to Stratos applications
Hi We have a requirement to map custom context to stratos web application/ Services. And currently we are looking how this can be done in the load balancer side. Our main requirement is to map a service hosted in a tenant to be map to a given domain. For example https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/to https://FooService.com/ and the wsdl/try it urls should change accordingly. In order to do this loadbalancer should identify https://FooService.com/ is a request which should be sent for https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/and request should get forward to https://FooService.com/ without changing the browser URL. (Or else we need to have a tomcat valve to foward the URL in the tomcat side itself) Can this be done using URLRewrite mediator? (if we store the two URLs in a data store and let the load balancer knows the mapping)? Regards, Amani ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon kernel is Frozen for Commits from 9.00am IST on 14th Feb, 2012
Hi Pradeep/Sameera, On Tue, Feb 14, 2012 at 8:42 AM, Pradeep Fernando prad...@wso2.com wrote: Hi devs, We are going to freeze the carbon-kernel[1] trunk for ~2 days. We have uploaded all the carbon-kernel related snapshot artifacts to the nexus repos. Devs can work on their day to day development tasks without a problem. During the the frozen period, 1. we are going to merge the tomcat-bundle in to carbon trunk 2. remove outer lib of carbon distribution and move them to the plugins folder While looking at outer lib, i found that jsr107cache is used by some of the carbon core bundles. But in the new svn structure, it is placed under graphite/dependencies. I think this is wrong and this should be moved into carbon/dependencies(ie kernel) as it is used by the carbon core bundles. Thanks, Kishanthan. 3. fix product assembly scripts accordingly [1] https://svn.wso2.org/repos/wso2/trunk/carbon -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
On Tue, Feb 14, 2012 at 3:31 PM, Afkham Azeez az...@wso2.com wrote: On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com wrote: Hi All, We had a review discussion on Carbon Authenticators and following are the review notes. 1. There are some common logic that should be implemented in every authenticator. Currently invoking this logic is duplicated among authenticators. So to avoid that we are planning to come up with an abstract Authenticator implementation. 2. As per now AuthenticationHandler first invokes AuthenticationAdmin and then it calls chain of authenticators. The AuthenticationAdmin call is not necessary. We need to refactor code in such a way that authenticator it self will only handle authenticating logic (Rather than within the Handler). 3. Properly implement authenticator chaining pattern. Make use “isHandle” Shouldn't this be isHandle*d*? Yes.. we discussed today to change the name.. and suggestion was to rename it to canHandle().. Thanks regards, -Prabath , “priority”, “isAuthenticated” methods and make only authenticator aware about the logic. 4. After cleaning up the API, implement “Basic Auth” authenticator. (As first step) Thanks AmilaJ -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
On Tue, Feb 14, 2012 at 3:42 PM, Prabath Siriwardena prab...@wso2.com wrote: On Tue, Feb 14, 2012 at 3:31 PM, Afkham Azeez az...@wso2.com wrote: On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com wrote: Hi All, We had a review discussion on Carbon Authenticators and following are the review notes. 1. There are some common logic that should be implemented in every authenticator. Currently invoking this logic is duplicated among authenticators. So to avoid that we are planning to come up with an abstract Authenticator implementation. 2. As per now AuthenticationHandler first invokes AuthenticationAdmin and then it calls chain of authenticators. The AuthenticationAdmin call is not necessary. We need to refactor code in such a way that authenticator it self will only handle authenticating logic (Rather than within the Handler). 3. Properly implement authenticator chaining pattern. Make use “isHandle” Shouldn't this be isHandled? Yes.. we discussed today to change the name.. and suggestion was to rename it to canHandle().. Yes, names which i mentioned are not precise. Just wanted to give a high level idea of the process. Will name appropriately and after changes we can do a code review. Thanks AmilaJ Thanks regards, -Prabath , “priority”, “isAuthenticated” methods and make only authenticator aware about the logic. 4. After cleaning up the API, implement “Basic Auth” authenticator. (As first step) Thanks AmilaJ -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Afkham Azeez Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Upcoming Carbon 4.0.0 Release
Hi all, On Tue, Feb 14, 2012 at 2:37 PM, Samisa Abeysinghe sam...@wso2.com wrote: When do we plan to feature complete? 29th February is the planned date for feature complete build. When would be the code freeze. We are hoping to code freeze by 7th March. thanks, dimuthu Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Upcoming Carbon 4.0.0 Release
Sounds good. Please keep the list informed on the release progress. On Tue, Feb 14, 2012 at 5:11 PM, Dimuthu Leelarathne dimut...@wso2.comwrote: Hi all, On Tue, Feb 14, 2012 at 2:37 PM, Samisa Abeysinghe sam...@wso2.comwrote: When do we plan to feature complete? 29th February is the planned date for feature complete build. When would be the code freeze. We are hoping to code freeze by 7th March. thanks, dimuthu Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon kernel is Frozen for Commits from 9.00am IST on 14th Feb, 2012
On Tue, Feb 14, 2012 at 3:30 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi Pradeep/Sameera, On Tue, Feb 14, 2012 at 8:42 AM, Pradeep Fernando prad...@wso2.comwrote: Hi devs, We are going to freeze the carbon-kernel[1] trunk for ~2 days. We have uploaded all the carbon-kernel related snapshot artifacts to the nexus repos. Devs can work on their day to day development tasks without a problem. During the the frozen period, 1. we are going to merge the tomcat-bundle in to carbon trunk 2. remove outer lib of carbon distribution and move them to the plugins folder While looking at outer lib, i found that jsr107cache is used by some of the carbon core bundles. But in the new svn structure, it is placed under graphite/dependencies. I think this is wrong and this should be moved into carbon/dependencies(ie kernel) as it is used by the carbon core bundles. +1. Please move it if it is used by carbon core. ~Isuru Thanks, Kishanthan. 3. fix product assembly scripts accordingly [1] https://svn.wso2.org/repos/wso2/trunk/carbon -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Graphite-Build #15 has FAILED
--- Carbon-Kernel Graphite-Build #15 failed. --- This build was manually triggered by BambooBuilder. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-15/ -- Failing Jobs -- - Default Job (Default Stage): 4105 tests passed. -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
Hi, And we also discussed that we need to write an AbstractAuthenticator to make life easy for other people who are writing authenticators. thanks, dimuthu On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com wrote: Hi All, We had a review discussion on Carbon Authenticators and following are the review notes. 1. There are some common logic that should be implemented in every authenticator. Currently invoking this logic is duplicated among authenticators. So to avoid that we are planning to come up with an abstract Authenticator implementation. 2. As per now AuthenticationHandler first invokes AuthenticationAdmin and then it calls chain of authenticators. The AuthenticationAdmin call is not necessary. We need to refactor code in such a way that authenticator it self will only handle authenticating logic (Rather than within the Handler). 3. Properly implement authenticator chaining pattern. Make use “isHandle”, “priority”, “isAuthenticated” methods and make only authenticator aware about the logic. 4. After cleaning up the API, implement “Basic Auth” authenticator. (As first step) Thanks AmilaJ -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel-Orbit #7 was SUCCESSFUL. Change made by pradeep.
--- Carbon-Kernel Carbon-Kernel-Orbit #7 was successful. --- Code has been updated by pradeep. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONKERNELBUILD-7/ -- Code Changes -- pradeep (120780): adding version exports -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #7 has FAILED. Change made by kishanthan and pradeep.
--- Carbon-Kernel Carbon-Kernel #7 failed. --- Code has been updated by kishanthan, pradeep. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-7/ -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- pradeep (120782): bringing in the tomcat bundle in to carbon-kernel code base. kishanthan (120779): adding jsr107cache to core-dependencies and making an orbit bundle for jsr107cache -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #8 was SUCCESSFUL (with 2733 tests). Change made by pradeep.
--- Carbon-Kernel Carbon-Kernel #8 was successful. --- Code has been updated by pradeep. 2733 tests in total. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-8/ -- Code Changes -- pradeep (120783): adding tomcat.ext bundle pradeep (120785): update aggregate pom -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mapping custom Context to Stratos applications
Hi Amani, LB is the best place to do this URL mapping. Because these sort of stuff are not concerns of a particular Stratos service. If you look at other H/W load balancer, this features comes by default. I think it is the high time to implement this functionality in our WSO2 LB. Thanks, Sameera. On Tue, Feb 14, 2012 at 3:26 PM, Amani Soysa am...@wso2.com wrote: Hi We have a requirement to map custom context to stratos web application/ Services. And currently we are looking how this can be done in the load balancer side. Our main requirement is to map a service hosted in a tenant to be map to a given domain. For example https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/to https://FooService.com/ and the wsdl/try it urls should change accordingly. In order to do this loadbalancer should identify https://FooService.com/is a request which should be sent for https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/and request should get forward to https://FooService.com/ without changing the browser URL. (Or else we need to have a tomcat valve to foward the URL in the tomcat side itself) Can this be done using URLRewrite mediator? (if we store the two URLs in a data store and let the load balancer knows the mapping)? Regards, Amani ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon kernel is Frozen for Commits from 9.00am IST on 14th Feb, 2012
Hi Senaka, On Tue, Feb 14, 2012 at 3:30 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi Pradeep/Sameera, On Tue, Feb 14, 2012 at 8:42 AM, Pradeep Fernando prad...@wso2.comwrote: Hi devs, We are going to freeze the carbon-kernel[1] trunk for ~2 days. We have uploaded all the carbon-kernel related snapshot artifacts to the nexus repos. Devs can work on their day to day development tasks without a problem. During the the frozen period, 1. we are going to merge the tomcat-bundle in to carbon trunk 2. remove outer lib of carbon distribution and move them to the plugins folder While looking at outer lib, i found that jsr107cache is used by some of the carbon core bundles. But in the new svn structure, it is placed under graphite/dependencies. I think this is wrong and this should be moved into carbon/dependencies(ie kernel) as it is used by the carbon core bundles. Can you confirm this? Thanks, Sameera. Thanks, Kishanthan. 3. fix product assembly scripts accordingly [1] https://svn.wso2.org/repos/wso2/trunk/carbon -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
Hi Thilini, I would consider the writing the script is last option we should consider. :) How about a wsdl extension? Can you please explain it a bit more? Thanks, Sameera. On Tue, Feb 14, 2012 at 8:46 PM, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
Hi Amila,
+1 for the proposed changes. Please see my comments below.
On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com wrote:
Hi All,
We had a review discussion on Carbon Authenticators and following are
the review notes.
1. There are some common logic that should be implemented in every
authenticator. Currently invoking this logic is duplicated among
authenticators. So to avoid that we are planning to come up with an
abstract Authenticator implementation.
2. As per now AuthenticationHandler first invokes AuthenticationAdmin
and then it calls chain of authenticators. The AuthenticationAdmin
call is not necessary. We need to refactor code in such a way that
authenticator it self will only handle authenticating logic (Rather
than within the Handler).
3. Properly implement authenticator chaining pattern. Make use
“isHandle”, “priority”, “isAuthenticated” methods and make only
authenticator aware about the logic.
4. After cleaning up the API, implement “Basic Auth” authenticator.
(As first step)
5. Cleanup Carbon.UI framework to improve the plugability of custom
authenticators. I recently wrote an authenticator, but I had to hard code
some URLs in the CarbonSecurityHttpContext class. Please have a look at the
following method in this class.
private boolean skipSSOSessionInvalidation(String requestedURI) {
boolean skipSessionInvalidation = false;
if ((requestedURI.indexOf(/samlsso) -1)
|| (requestedURI.indexOf(sso-saml/login.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/login_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-saml/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-acs/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-auth/redirect_ajaxprocessor.jsp) -1)) {
skipSessionInvalidation = true;
}
return skipSessionInvalidation;
}
As a part of this effort, lets refactor this bit of code as well.
Thanks,
Sameera.
Thanks
AmilaJ
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Upcoming Carbon 4.0.0 Release
On Tue, Feb 14, 2012 at 1:46 PM, Dimuthu Leelarathne dimut...@wso2.comwrote: Hi devs, Please find the work items of upcoming carbon core release. New Features === Tomcat OSGification - Pradeep/Dileepa - In Progress JVM Autoscalling - Nirmal/Azeez - In Progress CPU/Memoary usage per Tenant - Dimuthu/AmilaM/Amani - In Research Versioning Support for CAPP - Pradeep/Dileepa - Not started Ground work for Admin Service Security Framework - AmilaJ - In Progress Ground work for Admin Service - Shared Schema / JaxWS - Sagara - In Progress Ground work for Tenant partisioning - Sanjeewa/Ashansa/Azeez - Will start Ground work for Tenant aware load balancing - Sanjeewa/Ashansa/Azeez - Will start P2 feature improvement - Pradeep - Will start P2 feature improvement will be take care of by Dileepa. * We need to refactor our UI framework a bit to avoid scenarios where developers have to hard-code URLs. Thanks, Sameera. Other required work == SVN restructuring - Sameera/Pradeep - In Progress Upgrading orbit bundles to new version - Core - ??? - Need to start Caching issues - Senaka/DimuthuL Automated testing - Krishantha Clustering problems - Sanjeewa Exclude Dependencies in Core - ??? - Need to start Identify Carbon Core JIRAs to be fixed - DimuthuL We will copy the core build to specific location every Wednesday/Friday and send a mail. We also copy AS - ESB - Greg for QA. Our target is to release by end of March. thanks, dimuthul -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
On Tue, Feb 14, 2012 at 9:32 PM, Sameera Jayasoma same...@wso2.com wrote:
Hi Amila,
+1 for the proposed changes. Please see my comments below.
On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com wrote:
Hi All,
We had a review discussion on Carbon Authenticators and following are
the review notes.
1. There are some common logic that should be implemented in every
authenticator. Currently invoking this logic is duplicated among
authenticators. So to avoid that we are planning to come up with an
abstract Authenticator implementation.
2. As per now AuthenticationHandler first invokes AuthenticationAdmin
and then it calls chain of authenticators. The AuthenticationAdmin
call is not necessary. We need to refactor code in such a way that
authenticator it self will only handle authenticating logic (Rather
than within the Handler).
3. Properly implement authenticator chaining pattern. Make use
“isHandle”, “priority”, “isAuthenticated” methods and make only
authenticator aware about the logic.
4. After cleaning up the API, implement “Basic Auth” authenticator.
(As first step)
5. Cleanup Carbon.UI framework to improve the plugability of custom
authenticators. I recently wrote an authenticator, but I had to hard code
some URLs in the CarbonSecurityHttpContext class. Please have a look at the
following method in this class.
private boolean skipSSOSessionInvalidation(String requestedURI) {
boolean skipSessionInvalidation = false;
if ((requestedURI.indexOf(/samlsso) -1)
|| (requestedURI.indexOf(sso-saml/login.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/login_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-saml/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-acs/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-auth/redirect_ajaxprocessor.jsp) -1)) {
skipSessionInvalidation = true;
}
return skipSessionInvalidation;
}
As a part of this effort, lets refactor this bit of code as well.
+1. Will take above into consideration as well. If possible please
create a carbon Jira and assigned to me.
Thanks
AmilaJ
Thanks,
Sameera.
Thanks
AmilaJ
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com* twitter: **http://twitter.com/keheliya* http://twitter.com/keheliya* linked-in: **http://lk.linkedin.com/in/keheliya*http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Shall we remove org.wso2.carbon.core.installer module ?
Hi, $subject. I don't think we are using it anymore. WDYT ? thanks, --Pradeep -- ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.com wrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. You meant to say each external Web service consumed by the business process or each invoke in a process. There can be multiple invokes which talks to the same service endpoint. Thanks, Sameera. Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com* twitter: **http://twitter.com/keheliya* http://twitter.com/keheliya* linked-in: **http://lk.linkedin.com/in/keheliya*http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Tue, Feb 14, 2012 at 10:06 PM, Sameera Jayasoma same...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.com wrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService//wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. You meant to say each external Web service consumed by the business process Yes or each invoke in a process. There can be multiple invokes which talks to the same service endpoint. Thanks, Sameera. Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change soap:address location for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists soap:address location for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Keheliya Gallaba Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, email: keheliya [AT] wso2.com mobile: +94 71 551 8881 blog: http://galpotha.wordpress.com twitter: http://twitter.com/keheliya linked-in: http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- - Waruna Ranasinghe Senior Software Engineer, WSO2 Mobile: +94 724 318285 BLOG: http://warunapw.blogspot.com www.wso2.com - Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
https://wso2.org/jira/browse/CARBON-12378
Thanks,
Sameera.
On Tue, Feb 14, 2012 at 9:50 PM, Amila Jayasekara ami...@wso2.com wrote:
On Tue, Feb 14, 2012 at 9:32 PM, Sameera Jayasoma same...@wso2.com
wrote:
Hi Amila,
+1 for the proposed changes. Please see my comments below.
On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com
wrote:
Hi All,
We had a review discussion on Carbon Authenticators and following are
the review notes.
1. There are some common logic that should be implemented in every
authenticator. Currently invoking this logic is duplicated among
authenticators. So to avoid that we are planning to come up with an
abstract Authenticator implementation.
2. As per now AuthenticationHandler first invokes AuthenticationAdmin
and then it calls chain of authenticators. The AuthenticationAdmin
call is not necessary. We need to refactor code in such a way that
authenticator it self will only handle authenticating logic (Rather
than within the Handler).
3. Properly implement authenticator chaining pattern. Make use
“isHandle”, “priority”, “isAuthenticated” methods and make only
authenticator aware about the logic.
4. After cleaning up the API, implement “Basic Auth” authenticator.
(As first step)
5. Cleanup Carbon.UI framework to improve the plugability of custom
authenticators. I recently wrote an authenticator, but I had to hard code
some URLs in the CarbonSecurityHttpContext class. Please have a look at
the
following method in this class.
private boolean skipSSOSessionInvalidation(String requestedURI) {
boolean skipSessionInvalidation = false;
if ((requestedURI.indexOf(/samlsso) -1)
|| (requestedURI.indexOf(sso-saml/login.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/login_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-saml/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-acs/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-auth/redirect_ajaxprocessor.jsp) -1)) {
skipSessionInvalidation = true;
}
return skipSessionInvalidation;
}
As a part of this effort, lets refactor this bit of code as well.
+1. Will take above into consideration as well. If possible please
create a carbon Jira and assigned to me.
Thanks
AmilaJ
Thanks,
Sameera.
Thanks
AmilaJ
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Tue, Feb 14, 2012 at 10:10 PM, Waruna Ranasinghe war...@wso2.com wrote: On Tue, Feb 14, 2012 at 10:06 PM, Sameera Jayasoma same...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.com wrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns= http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. You meant to say each external Web service consumed by the business process Yes Great. +1 for this approach, if these *.epr files can be store outside of the bpel package. :) Thanks, Sameera. or each invoke in a process. There can be multiple invokes which talks to the same service endpoint. Thanks, Sameera. Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change soap:address location for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists soap:address location for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Keheliya Gallaba Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, email: keheliya [AT] wso2.com mobile: +94 71 551 8881 blog: http://galpotha.wordpress.com twitter: http://twitter.com/keheliya linked-in: http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- - Waruna Ranasinghe Senior Software Engineer, WSO2 Mobile: +94 724 318285 BLOG: http://warunapw.blogspot.com www.wso2.com - Lean . Enterprise .
Re: [Carbon-dev] Shall we remove org.wso2.carbon.core.installer module ?
On Tue, Feb 14, 2012 at 10:04 PM, Pradeep Fernando prad...@wso2.com wrote: Hi, $subject. I don't think we are using it anymore. WDYT ? +1. Thanks, Sameera. thanks, --Pradeep -- ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] removing jars from ${carbon.home}/lib directory
Hi,
as the initial step, we removed below set of jars,
-includejavax.activation:activation:jar/include
-includeorg.apache.ant:ant:jar/include
-includeorg.apache.ant:ant-launcher:jar/include
-includeorg.apache.ant:ant-nodeps:jar/include
-includeaopalliance:aopalliance:jar/include
-includecommons-modeler:commons-modeler:jar/include
-includecommons-el:commons-el:jar/include
-includecommons-cli:commons-cli:jar/include
-includecommons-lang:commons-lang:jar/include
-
includeorg.apache.geronimo.specs.wso2:geronimo-jta_1.1_spec:jar/include
-
includecom.h2database.wso2:h2-database-engine:jar/include
-includejavax.ws.rs:jsr311-api:jar/include
-includelog4j:log4j:jar/include
-includeme.prettyprint.wso2:hector-core:jar/include
- includeorg.apache.cassandra:apache-cassandra:jar/include
-includelibthrift:libthrift:jar/include
- includeslf4j.wso2:slf4j/include
-includeorg.perf4j.wso2:perf4j:jar/include
-
includeorg.cliffc.high_scale_lib.wso2:high-scale-lib:jar/include
-
includeorg.wso2.carbon:org.wso2.carbon.core.installer:jar/include
-includeorg.igniterealtime.smack.wso2:smack:jar/include
-includeorg.igniterealtime.smack.wso2:smackx:jar/include
-includejavax.xml.stream:stax-api:jar/include
-includeorg.apache.woden.wso2:woden:jar/include
-includewrapper:wrapper:jar/include
-includexml-resolver:xml-resolver:jar/include
The above jars are not required for carbon-kernel startup/execution.
Product teams may create bundles out of above jars and pack them with their
features. Apart from above set of jars , I removed atomikos relaed jars as
well.
We should decide whether we are shipping atomikos with carbon-kernel /
shipping it as a separate feature.
Now we are working on ${carbon.home}/lib/api jars.
thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Carbon App server version is wrong in feature repo
Hi, $Subject, It should be changed to , synapse.version2.1.0-wso2v4/synapse.version -appserver.version4.1.0-SNAPSHOT/appserver.version +appserver.version4.5.0-SNAPSHOT/appserver.version esb.version4.0.0-SNAPSHOT/esb.version Thanks, -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Graphite-Build #16 has FAILED (10 tests failed). Change made by 5 authors.
--- Carbon-Kernel Graphite-Build #16 failed. --- Code has been updated by dharshana, ruchira, shammi, sanjayav, chanaka. 10/4460 tests failed. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/ -- Failing Jobs -- - Default Job (Default Stage): 10 of 4460 tests failed. -- Code Changes -- chanaka (120776): Diagram UI's Updated for cluster monitoring shammi (120778): Adding the Once in order support with new configuration dharshana (120786): Removing Framework Settings Class from all the module, Report Listner and manual surefire Report creator -- Tests -- New Test Failures (10) - BPSBPELServerManager: Start server - BPSCleanupServerManager: Start server - BPSSecurityServerManager: Start server - BPSTestServerManager: Start server - ESBTestServerManager: Start server - CEPTestServerManager: Start server - DSSTestServerManager: Start server - GSTestServerManager: Start server - ISTestServerManager: Start server - MSTestServerManager: Start server -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #9 was SUCCESSFUL (with 2733 tests). Change made by pradeep.
--- Carbon-Kernel Carbon-Kernel #9 was successful. --- Code has been updated by pradeep. 2733 tests in total. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-9/ -- Code Changes -- pradeep (120790): removing atomikos jars and /lib/core directory pradeep (120789): removing unncessary exports pradeep (120788): removing jars found under /lib -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Tue, Feb 14, 2012 at 10:17 PM, Sameera Jayasoma same...@wso2.com wrote: On Tue, Feb 14, 2012 at 10:10 PM, Waruna Ranasinghe war...@wso2.comwrote: On Tue, Feb 14, 2012 at 10:06 PM, Sameera Jayasoma same...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.com wrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns= http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. You meant to say each external Web service consumed by the business process Yes Great. +1 for this approach, if these *.epr files can be store outside of the bpel package. :) Yes, these can be stored outside the bpel package and we have to provide an absolute path. e.g endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config; endpointReference=file:/path/to/epr/ Thanks, AmilaM. Thanks, Sameera. or each invoke in a process. There can be multiple invokes which talks to the same service endpoint. Thanks, Sameera. Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change soap:address location for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists soap:address location for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Keheliya Gallaba Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, email: keheliya [AT] wso2.com mobile: +94 71 551 8881 blog: http://galpotha.wordpress.com twitter: http://twitter.com/keheliya linked-in: http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing
[Carbon-dev] ESB aggregate on complete (min, max ) values dose not take xpath expressions
Hi Regarding $subject , Can we do this WDYT ? we do have a scenario to Iterate over the nodes, filter out and continue and do the operations via service chaining, expression will determine how many messages it should wait before continue completion, and minimum number of messages will be count via the property expression Iterator property name=TARGET_USER expression=//a:Adviser/a:Id/ property name=ACCOUNT_COUNT value=0/ // doing role authentication ...returns ctx:PERM_RESULT (boolan value) filter source=$ctx:PERM_RESULT regex=true property name=ACCOUNT_COUNT expression=$ctx:ACCOUNT_COUNT + 1/ continue service chaining. filter /iterator aggregate completeCondition messageCount min=$ctx:ACCOUNT_COUNT max=-1/ $ctx:ACCOUNT_COUN can we provide like this /completeCondition onComplete xmlns:m0=http://ws.wso2.org/dataservice; expression=//m0:Clients sequence key=sequenceClientPolcies/ /onComplete /aggregate cheers Dushan Abeyruwan WSO2 Inc Senior Software Engineer Mobile:(+94)714408632 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mapping custom Context to Stratos applications
The thing is, WSO2 LB handles multiple domains. So, when a request such as http://foo.com/services/XXX comes in, it has to find out where to dispatch it to. For example, how do we know whether this request has to be forwarded to the AS or ESB if such a request comes in, and the LB is fronting bothe the AS ESB? There is more to this. The URLs in our components are calculated using the HostName field in the carbon.xml. Those also have to change depending on the context. For example, foo.com tenant will want to see its WSDL URLs as http://foo.com/services/XXX?wsdl not http://appserver.stratoslive.wso2.com/services/t/XXX?wsdl. In addition to URL displaying, there are many other areas which may need to be changed to handle such custom domains. This affects the whole platform. It is not a simple URL mapping problem. On Tue, Feb 14, 2012 at 9:18 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Amani, LB is the best place to do this URL mapping. Because these sort of stuff are not concerns of a particular Stratos service. If you look at other H/W load balancer, this features comes by default. I think it is the high time to implement this functionality in our WSO2 LB. Thanks, Sameera. On Tue, Feb 14, 2012 at 3:26 PM, Amani Soysa am...@wso2.com wrote: Hi We have a requirement to map custom context to stratos web application/ Services. And currently we are looking how this can be done in the load balancer side. Our main requirement is to map a service hosted in a tenant to be map to a given domain. For example https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/to https://FooService.com/ and the wsdl/try it urls should change accordingly. In order to do this loadbalancer should identify https://FooService.com/is a request which should be sent for https://appserver.stratoslive.wso2.com/services/t/amani123.com/FooService/and request should get forward to https://FooService.com/ without changing the browser URL. (Or else we need to have a tomcat valve to foward the URL in the tomcat side itself) Can this be done using URLRewrite mediator? (if we store the two URLs in a data store and let the load balancer knows the mapping)? Regards, Amani ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Shall we remove org.wso2.carbon.core.installer module ?
Looks like an old module that has been hanging around. We can get rid of it. On Tue, Feb 14, 2012 at 10:04 PM, Pradeep Fernando prad...@wso2.com wrote: Hi, $subject. I don't think we are using it anymore. WDYT ? thanks, --Pradeep -- -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cleaning up Carbon Authenticator Framework
On Tue, Feb 14, 2012 at 10:14 PM, Sameera Jayasoma same...@wso2.com wrote:
https://wso2.org/jira/browse/CARBON-12378
Thanks,
Sameera.
On Tue, Feb 14, 2012 at 9:50 PM, Amila Jayasekara ami...@wso2.com wrote:
On Tue, Feb 14, 2012 at 9:32 PM, Sameera Jayasoma same...@wso2.com
wrote:
Hi Amila,
+1 for the proposed changes. Please see my comments below.
On Tue, Feb 14, 2012 at 3:22 PM, Amila Jayasekara ami...@wso2.com
wrote:
Hi All,
We had a review discussion on Carbon Authenticators and following are
the review notes.
1. There are some common logic that should be implemented in every
authenticator. Currently invoking this logic is duplicated among
authenticators. So to avoid that we are planning to come up with an
abstract Authenticator implementation.
2. As per now AuthenticationHandler first invokes AuthenticationAdmin
and then it calls chain of authenticators. The AuthenticationAdmin
call is not necessary. We need to refactor code in such a way that
authenticator it self will only handle authenticating logic (Rather
than within the Handler).
3. Properly implement authenticator chaining pattern. Make use
“isHandle”, “priority”, “isAuthenticated” methods and make only
authenticator aware about the logic.
4. After cleaning up the API, implement “Basic Auth” authenticator.
(As first step)
5. Cleanup Carbon.UI framework to improve the plugability of custom
authenticators. I recently wrote an authenticator, but I had to hard
code
some URLs in the CarbonSecurityHttpContext class. Please have a look at
the
following method in this class.
private boolean skipSSOSessionInvalidation(String requestedURI) {
boolean skipSessionInvalidation = false;
if ((requestedURI.indexOf(/samlsso) -1)
|| (requestedURI.indexOf(sso-saml/login.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/login_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-saml/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-sso/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(sso-acs/redirect_ajaxprocessor.jsp) -1)
||
(requestedURI.indexOf(stratos-auth/redirect_ajaxprocessor.jsp) -1))
{
skipSessionInvalidation = true;
}
return skipSessionInvalidation;
}
As a part of this effort, lets refactor this bit of code as well.
I have looked into this already, I will come up with set of handler
implementations(same as axis2 handlers) to clean up that lengthy method. We
will discuss once I am done with the code.
Thank you.
+1. Will take above into consideration as well. If possible please
create a carbon Jira and assigned to me.
Thanks
AmilaJ
Thanks,
Sameera.
Thanks
AmilaJ
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Mobile : +94773330538
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.com wrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. Yes. That's true. But the initial thinking was to have a single config for each invocation. Thanks Thilini Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com* twitter: **http://twitter.com/keheliya* http://twitter.com/keheliya* linked-in: **http://lk.linkedin.com/in/keheliya*http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Wed, Feb 15, 2012 at 8:49 AM, Thilini Ishaka thil...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.comwrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. Yes. That's true. But the initial thinking was to have a single config for each invocation. I mean to avoid updating multiple configuration files. Thanks Thilini Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com* twitter: **http://twitter.com/keheliya* http://twitter.com/keheliya* linked-in: **http://lk.linkedin.com/in/keheliya*http://lk.linkedin.com/in/keheliya ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards Thilini Ishaka WSO2 Inc -- Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] removing jars from ${carbon.home}/lib directory
Let's ship atomikos as a separate feature.
On Tue, Feb 14, 2012 at 11:16 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
as the initial step, we removed below set of jars,
-includejavax.activation:activation:jar/include
-includeorg.apache.ant:ant:jar/include
-includeorg.apache.ant:ant-launcher:jar/include
-includeorg.apache.ant:ant-nodeps:jar/include
-includeaopalliance:aopalliance:jar/include
-includecommons-modeler:commons-modeler:jar/include
-includecommons-el:commons-el:jar/include
-includecommons-cli:commons-cli:jar/include
-includecommons-lang:commons-lang:jar/include
-
includeorg.apache.geronimo.specs.wso2:geronimo-jta_1.1_spec:jar/include
-
includecom.h2database.wso2:h2-database-engine:jar/include
-includejavax.ws.rs:jsr311-api:jar/include
-includelog4j:log4j:jar/include
-includeme.prettyprint.wso2:hector-core:jar/include
-
includeorg.apache.cassandra:apache-cassandra:jar/include
-includelibthrift:libthrift:jar/include
- includeslf4j.wso2:slf4j/include
-includeorg.perf4j.wso2:perf4j:jar/include
-
includeorg.cliffc.high_scale_lib.wso2:high-scale-lib:jar/include
-
includeorg.wso2.carbon:org.wso2.carbon.core.installer:jar/include
-includeorg.igniterealtime.smack.wso2:smack:jar/include
-
includeorg.igniterealtime.smack.wso2:smackx:jar/include
-includejavax.xml.stream:stax-api:jar/include
-includeorg.apache.woden.wso2:woden:jar/include
-includewrapper:wrapper:jar/include
-includexml-resolver:xml-resolver:jar/include
The above jars are not required for carbon-kernel startup/execution.
Product teams may create bundles out of above jars and pack them with their
features. Apart from above set of jars , I removed atomikos relaed jars as
well.
We should decide whether we are shipping atomikos with carbon-kernel /
shipping it as a separate feature.
Now we are working on ${carbon.home}/lib/api jars.
thanks,
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ESB aggregate on complete (min, max ) values dose not take xpath expressions
Should be implemented at Synapse level. Better to discuss this there and provide a patch. Thanks, Hiranya On Wed, Feb 15, 2012 at 7:27 AM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Regarding $subject , Can we do this WDYT ? we do have a scenario to Iterate over the nodes, filter out and continue and do the operations via service chaining, expression will determine how many messages it should wait before continue completion, and minimum number of messages will be count via the property expression Iterator property name=TARGET_USER expression=//a:Adviser/a:Id/ property name=ACCOUNT_COUNT value=0/ // doing role authentication ...returns ctx:PERM_RESULT (boolan value) filter source=$ctx:PERM_RESULT regex=true property name=ACCOUNT_COUNT expression=$ctx:ACCOUNT_COUNT + 1/ continue service chaining. filter /iterator aggregate completeCondition messageCount min=$ctx:ACCOUNT_COUNT max=-1/ $ctx:ACCOUNT_COUN can we provide like this /completeCondition onComplete xmlns:m0=http://ws.wso2.org/dataservice; expression=//m0:Clients sequence key=sequenceClientPolcies/ /onComplete /aggregate cheers Dushan Abeyruwan WSO2 Inc Senior Software Engineer Mobile:(+94)714408632 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Possible performance degrade after installing Carbon Studio 2.0.0-SNAPSHOT2
-- Forwarded message -- From: Harshana Martin harsh...@wso2.com Date: Wed, Feb 15, 2012 at 12:54 AM Subject: Re: Possible performance degrade after installing Carbon Studio 2.0.0-SNAPSHOT2 To: Sumedha Rubasinghe sume...@wso2.com, Chathuri Wimalasena chath...@wso2.com Hi Sumedha, This is possible for the first or second time after installing CS due to OSGi bundle wiring. Otherwise it should not happen. Can you reproduce this situation consistently? If yes, we may have to see what is going underneath. Anyway we have some caching solutions to be ported from 1.0.x branch to Trunk I believe. May be we can do that immediately and see whether it solves the issue. Thanks and Regards, Harshana On Tue, Feb 14, 2012 at 2:07 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Folks, I feel a huge performance degrade in Eclipse performance after installing Carbon Studio 2.0.0-SNAPSHOT2. I have other projects also loaded even the start up loading time has increased. -- /sumedha -- Harshana Martin Software Engineer WSO2 Inc. Web:http://wso2.com http://wso2.org Mobile: +94 716062650 Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 Twitter: http://twitter.com/harshana05 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Context mapping to Stratos Applications
Hi Since we work with two WebApp one is the main WebApp in AS and the other is the deployed WebApp in AS, it requires to forward the URL across WebApps according to offline discussion with Sameera. Are these two WebApp staying in the same Tomcat container? According to [1], to forward within different WebApp, they need to live in the same Tomcat container. [1] http://www.coderanch.com/t/512848/Servlets/java/Calling-another-web-app-RequestDispatcher On Thu, Feb 9, 2012 at 5:51 PM, Reka Thirunavukkarasu r...@wso2.com wrote: Hi I'm working on custom context mapping for web-apps in Stratos application server. In order to handle it, i want to redirect the user given url to the actual (current) url without user knowing the redirection. So RequestDispatcher is the possible one that i could use here. But when i used RequestDispatcher, it is looping several times and finally ends up with the login page. I found CarbonSecuredHttpContext in org.wso2.carbon.ui is doing some redirection for every secured request where after several looping only, one url is redirected in the browser. When i send the requested URL without any context (https://test.stratosapps.com:9446/), it is redirecting to response.sendRedirect(carbon) in CarbonSecuredHttpContext . So that login page finally ends up. When i login as a super tenant, i accessed http://example.stratosapps.com:9763 through http, same issue happens there as well. Can somebody suggest me how could i possibly do a redirection here for a url like https://example.stratosapps.com:9446/ to redirect https://example.stratosapps.com:9446/t/testdev.com/webapps/example in case example is the web-app? FYI=I have done the domain mapping in /etc/hosts. The relervant code is: RequestDispatcher requestDispatcher = request.getRequestDispatcher(/t/ testdev.com/webapps/example); requestDispatcher.forward(request,response); Regards, Reka ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Graphite-Build #16 has FAILED (10 tests failed). Change made by 5 authors.
Hi Nuwan, Could you please revert the commit you mistakenly did to : graphite/components/pom.xml Thanks Shammi On Tue, Feb 14, 2012 at 11:41 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Graphite-Buildhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #16http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/ failed Code has been updated by dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana, ruchira http://builder4.us1.wso2.org:/bamboo/browse/author/ruchira, shammi http://builder4.us1.wso2.org:/bamboo/browse/author/shammi, sanjayav http://builder4.us1.wso2.org:/bamboo/browse/author/sanjayav, chanaka http://builder4.us1.wso2.org:/bamboo/browse/author/chanaka. *10/4460* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/ (Default Stage) 181 minutes 10 of 4460 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit/ View all 7 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit/ dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana New TestNG test Runner 120787 dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana Removing Framework Settings Class from all the module, Report Listner and manual surefire Report creator 120786 ruchirahttp://builder4.us1.wso2.org:/bamboo/browse/author/ruchira Fixing build issue 120784 4 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/test 10 New Test Failures Test Job BPSBPELServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637818 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSCleanupServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637824 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSSecurityServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637830 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637809 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test ESBTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637829 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test CEPTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637805 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test DSSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637823 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test GSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637828 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test ISTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637817 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test MSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637812 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16 | Add
Re: [Carbon-dev] Context mapping to Stratos Applications
I don't think this is a question of forwarding between webapps. I thought this was being done using a Tomcat Valve. If so, the forwarding is done by this valve, which sits outside all webapps. On Wed, Feb 15, 2012 at 10:15 AM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi Since we work with two WebApp one is the main WebApp in AS and the other is the deployed WebApp in AS, it requires to forward the URL across WebApps according to offline discussion with Sameera. Are these two WebApp staying in the same Tomcat container? According to [1], to forward within different WebApp, they need to live in the same Tomcat container. [1] http://www.coderanch.com/t/512848/Servlets/java/Calling-another-web-app-RequestDispatcher On Thu, Feb 9, 2012 at 5:51 PM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi I'm working on custom context mapping for web-apps in Stratos application server. In order to handle it, i want to redirect the user given url to the actual (current) url without user knowing the redirection. So RequestDispatcher is the possible one that i could use here. But when i used RequestDispatcher, it is looping several times and finally ends up with the login page. I found CarbonSecuredHttpContext in org.wso2.carbon.ui is doing some redirection for every secured request where after several looping only, one url is redirected in the browser. When i send the requested URL without any context (https://test.stratosapps.com:9446/), it is redirecting to response.sendRedirect(carbon) in CarbonSecuredHttpContext . So that login page finally ends up. When i login as a super tenant, i accessed http://example.stratosapps.com:9763 through http, same issue happens there as well. Can somebody suggest me how could i possibly do a redirection here for a url like https://example.stratosapps.com:9446/ to redirect https://example.stratosapps.com:9446/t/testdev.com/webapps/example in case example is the web-app? FYI=I have done the domain mapping in /etc/hosts. The relervant code is: RequestDispatcher requestDispatcher = request.getRequestDispatcher(/t/ testdev.com/webapps/example); requestDispatcher.forward(request,response); Regards, Reka -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Graphite-Build #16 has FAILED (10 tests failed). Change made by 5 authors.
Hi, Done, sorry for the trouble. Regards, /Nuwan On Wed, Feb 15, 2012 at 10:18 AM, Shammi Jayasinghe sha...@wso2.com wrote: Hi Nuwan, Could you please revert the commit you mistakenly did to : graphite/components/pom.xml Thanks Shammi On Tue, Feb 14, 2012 at 11:41 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Graphite-Buildhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #16http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/ failed Code has been updated by dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana, ruchira http://builder4.us1.wso2.org:/bamboo/browse/author/ruchira, shammi http://builder4.us1.wso2.org:/bamboo/browse/author/shammi, sanjayavhttp://builder4.us1.wso2.org:/bamboo/browse/author/sanjayav, chanaka http://builder4.us1.wso2.org:/bamboo/browse/author/chanaka. *10/4460* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/ (Default Stage) 181 minutes 10 of 4460 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit/ View all 7 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit/ dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana New TestNG test Runner 120787 dharshanahttp://builder4.us1.wso2.org:/bamboo/browse/author/dharshana Removing Framework Settings Class from all the module, Report Listner and manual surefire Report creator 120786 ruchirahttp://builder4.us1.wso2.org:/bamboo/browse/author/ruchira Fixing build issue 120784 4 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/commit Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-16/test 10 New Test Failures Test Job BPSBPELServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637818 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSCleanupServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637824 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSSecurityServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637830 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test BPSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637809 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test ESBTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637829 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test CEPTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637805 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test DSSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637823 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test GSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637828 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test ISTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637817 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test MSTestServerManager startServerhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test/case/7637812 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-16/test
Re: [Carbon-dev] Issue with WSAuthorizationManager API
Hi Amila, On Wed, Feb 15, 2012 at 4:06 PM, Amila Suriarachchi am...@wso2.com wrote: is it possible to use XCMAL with entilement mediator? No, in this situation, we can't use it, we wrote a custom mediator to authorize a list of users inside a single flow, for a requirement we have. Cheers, Anjana. thanks, Amila. On Wed, Feb 15, 2012 at 10:19 AM, Anjana Fernando anj...@wso2.com wrote: Hi, I'm using the WSAuthorizationManager API to check for authorization for a user/resource/action combination. And for any user value, who is not even in the user store, with the action value read with any resource id, it always returns true, which is, it always says, the user is authorized. Is this some design decision or a bug? .. Cheers, Anjana. -- *Anjana Fernando* Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- *Anjana Fernando* Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon kernel is Frozen for Commits from 9.00am IST on 14th Feb, 2012
On Tue, Feb 14, 2012 at 9:24 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Senaka, On Tue, Feb 14, 2012 at 3:30 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi Pradeep/Sameera, On Tue, Feb 14, 2012 at 8:42 AM, Pradeep Fernando prad...@wso2.comwrote: Hi devs, We are going to freeze the carbon-kernel[1] trunk for ~2 days. We have uploaded all the carbon-kernel related snapshot artifacts to the nexus repos. Devs can work on their day to day development tasks without a problem. During the the frozen period, 1. we are going to merge the tomcat-bundle in to carbon trunk 2. remove outer lib of carbon distribution and move them to the plugins folder While looking at outer lib, i found that jsr107cache is used by some of the carbon core bundles. But in the new svn structure, it is placed under graphite/dependencies. I think this is wrong and this should be moved into carbon/dependencies(ie kernel) as it is used by the carbon core bundles. Can you confirm this? +1. jsr107cache is used by core libraries of carbon to provide the caching APIs. Thanks, Senaka. Thanks, Sameera. Thanks, Kishanthan. 3. fix product assembly scripts accordingly [1] https://svn.wso2.org/repos/wso2/trunk/carbon -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
Hi, I want to add some more information regarding this. Unified endpoint per each file is okey to go with as far as we do not need to edit configurations in any of the artifacts (deploy.xml, wsdl files, etc..) inside the BPEL package when deploying the same in different environments. When we keep the .epr files outside the BPEL package we need to give the absolute path for each .epr inside the deploy.xml as AmilaM mentioned. And this is the limitation I see. Can this be achieved by passing a parameter to deploy.xml to get the path from a system property? * invoke partnerLink=MultiplierPartnerLink* * service name=MultiplierService.wsdl:MultiplierService port=MultiplierServiceSOAP11port_http* *endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config* * endpointReference=$x /* * /service* */invoke* Thanks Thilini On Wed, Feb 15, 2012 at 8:52 AM, Thilini Ishaka thil...@wso2.com wrote: On Wed, Feb 15, 2012 at 8:49 AM, Thilini Ishaka thil...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.comwrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns= http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. Yes. That's true. But the initial thinking was to have a single config for each invocation. I mean to avoid updating multiple configuration files. Thanks Thilini Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com* twitter: **http://twitter.com/keheliya* http://twitter.com/keheliya* linked-in: **http://lk.linkedin.com/in/keheliya*http://lk.linkedin.com/in/keheliya
Re: [Carbon-dev] One step solution to change soap:address location of WSDL files, inside a BPEL package
On Wed, Feb 15, 2012 at 11:57 AM, Thilini Ishaka thil...@wso2.com wrote: Hi, I want to add some more information regarding this. Unified endpoint per each file is okey to go with as far as we do not need to edit configurations in any of the artifacts (deploy.xml, wsdl files, etc..) inside the BPEL package when deploying the same in different environments. When we keep the .epr files outside the BPEL package we need to give the absolute path for each .epr inside the deploy.xml as AmilaM mentioned. And this is the limitation I see. Can this be achieved by passing a parameter to deploy.xml to get the path from a system property? Yes, This is an useful improvement to maintain same BPEL artifacts in multiple environments. * invoke partnerLink=MultiplierPartnerLink* * service name=MultiplierService.wsdl:MultiplierService port=MultiplierServiceSOAP11port_http* *endpoint xmlns=http://wso2.org/bps/bpel/endpoint/config * * endpointReference=$x /* * /service* */invoke* Thanks Thilini On Wed, Feb 15, 2012 at 8:52 AM, Thilini Ishaka thil...@wso2.com wrote: On Wed, Feb 15, 2012 at 8:49 AM, Thilini Ishaka thil...@wso2.com wrote: On Tue, Feb 14, 2012 at 9:54 PM, Keheliya Gallaba kehel...@wso2.comwrote: Hi Thilini, I think currently we can have that functionality via unified endpoints. You can refer to an external endpoint configuration in the deploy.xml like the following: invoke partnerLink=CreditRatingPL service name=crns:CreditRatingService port=CreditRatingPort endpoint xmlns= http://wso2.org/bps/bpel/endpoint/config; endpointReference=CreditRatingService.epr/ /service /invoke That file can define an address like this: wsa:EndpointReference xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.w3schools.com uep_schema.xsd xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsdl11=http://schemas.xmlsoap.org/wsdl/; wsa:Addresshttp://localhost:9000/services/CreditRatingService/ /wsa:Address /wsa:EndpointReference One restriction is you will have to define a config file for each distinct invoke in a process. But the advantage is, when the environment changes you can just change the file without changing the deployment artifact. Yes. That's true. But the initial thinking was to have a single config for each invocation. I mean to avoid updating multiple configuration files. Thanks Thilini Regards, Keheliya On Tue, Feb 14, 2012 at 9:38 PM, Paul Fremantle p...@wso2.com wrote: Isn't this something that our endpoint unification is meant to take care of? Paul On 14 February 2012 15:16, Thilini Ishaka thil...@wso2.com wrote: Hi All, Consider a situation where we have multiple service (partner services) invocations in a business process. We need to change *soap:address location *for each and every wsdl once a particular service uri is changed from x to y. This is a frequent situation which we need one step solution. I would suggest two approaches as; Have a single configuration file which lists *soap:address location *for each wsdl (Then you only require to change the URIs inside the config file); 1. A script based solution. (perl/python) 2. Write an own wsdl extension What would be the best solution here? kindly appreciate your thoughts. Thanks Thilini Regards Thilini Ishaka WSO2 Inc ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Keheliya Gallaba* Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com, *email: **keheliya [AT] wso2.com* kehel...@wso2.com *mobile: +94 71 551 8881* *blog: **http://galpotha.wordpress.com* http://galpotha.wordpress.com *
Re: [Carbon-dev] Including a third part library
Actually there are several Java files require for the library. com.maxmind.geoip is used as the package name. Is it ok to change it as org.wso2.carbon.utils.geoip ? (Library is LGPL) Another problem I have is that the library needs the path of the database file as a path from the root. But with our OSGI bundles we found that the file can only be referred as an InputStream using getResourceAsStream function but not as a path from the root. In this case also we have to edit the library file to provide the file as an InputStream. Is it ok? or is there any workaround? On Wed, Feb 8, 2012 at 2:15 PM, Afkham Azeez az...@wso2.com wrote: How about adding that file to org.wso2.carbon.util jar with the proper attributions? On Wed, Feb 8, 2012 at 2:06 PM, Maninda Edirisooriya mani...@wso2.comwrote: I have to include a third party Java library with LGPL licences to convert IP addresses to geographical locations in the BAM2. It is only source a code file. (.java file) I have no idea where to add it. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
