Re: [Dev] App-Manager 1.0 Release Testing Update
Also we have started testing earlier enough I guess. Pavithra started testing the previous packs in last August/Spetember. And this round of testing started in January. The problem was some features were not ready and features changed through out last couple of months, which invalidates the tests we did and have to do it again. On Tue, Apr 7, 2015 at 1:49 PM, Nirodha Pramod niro...@wso2.com wrote: Hi, Our concerns were that we had the above mentioned L1s and L2s and added new features in the latest packs, which makes it not ready to be released in two more days. And we have been getting packs like every other day(some with config changes too) so it is a bit hard to manage testing on all the given packs. So to do a decent release we would need more time to test. Since we were running low on headcount we could not allocate more than one in past few weeks. However we have allocated another person to help with AppM testing. Thanks, Nirodha On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Shakar, All these are available on packs. Problems - we now have 8 L1s, 26 L2s - QA was running low on resources, so only one engineer was available for last 2+ weeks - So QA wants to test more On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Yes, thats all fine. I am asking when we will get the pack with all these features/ changes done. Meaning the proper alpha with features frozen. If we still don't know that date, it is also fine, but we can plan the QA based on that. On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe sume...@wso2.com wrote: On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the
Re: [Dev] App-Manager 1.0 Release Testing Update
Hi Sumedha, Yes, thats all fine. I am asking when we will get the pack with all these features/ changes done. Meaning the proper alpha with features frozen. If we still don't know that date, it is also fine, but we can plan the QA based on that. On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe sume...@wso2.com wrote: On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the latest pack in [1]. We could find root cause for some of the intermittent issues that you have reported. But we included some debug logs to possible places, so that we can narrow down the issue if it appeared on latest pack too. Please enable jaggery debug logs before you start testing the pack. [1]. http://builder1.us1.wso2.org/~appm/19-03-2015/ Regards, Dinusha. On Tue, Mar 17, 2015 at 6:39 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, Meeting Notes - AM team will try to fix all the issues related to instability and share a new pack tomorrow. - Testing on oracle will be done based on the time available before the expected release date. - Long running test has to be run by the QA team. (on a standalone setup) - All features and UI's are currently finalized and no major changes will happen. With Regards, On Tue, Mar 17, 2015 at 6:14 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi Dinusha, Sorry for the ambiguity in the mail. Please see my comments in-line Hi All, This is to update the current status of the App Manger release cycle. We had issues initially when testing due to following reasons - There was no decided permission model embedded to AM. This is finalized and we are not going to change the model ! There is a mail thread for this
Re: [Dev] App-Manager 1.0 Release Testing Update
Shakar, All these are available on packs. Problems - we now have 8 L1s, 26 L2s - QA was running low on resources, so only one engineer was available for last 2+ weeks - So QA wants to test more On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Yes, thats all fine. I am asking when we will get the pack with all these features/ changes done. Meaning the proper alpha with features frozen. If we still don't know that date, it is also fine, but we can plan the QA based on that. On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe sume...@wso2.com wrote: On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the latest pack in [1]. We could find root cause for some of the intermittent issues that you have reported. But we included some debug logs to possible places, so that we can narrow down the issue if it appeared on latest pack too. Please enable jaggery debug logs before you start testing the pack. [1]. http://builder1.us1.wso2.org/~appm/19-03-2015/ Regards, Dinusha. On Tue, Mar 17, 2015 at 6:39 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, Meeting Notes - AM team will try to fix all the issues related to instability and share a new pack tomorrow. - Testing on oracle will be done based on the time available before the expected release date. - Long running test has to be run by the QA team. (on a standalone setup) - All features and UI's are currently finalized and no major changes will happen. With Regards, On Tue, Mar 17, 2015 at 6:14 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi Dinusha, Sorry for the ambiguity in the mail. Please see my comments in-line Hi All,
[Dev] Please review and merge PR
Hi Carbon Team, Please review and merge [1] related to the redmine issue [2]. [1] - https://github.com/wso2/carbon4-kernel/pull/198 [2] - https://redmine.wso2.com/issues/3686 Thanks. -- Jagath Ariyarathne Technical Lead WSO2 Inc. http://wso2.com/ Email: jaga...@wso2.com Mob : +94 77 386 7048 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] App-Manager 1.0 Release Testing Update
On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Shakar, All these are available on packs. AFAIK, following features were introduced from the 5th April pack (day before yesterday). So we cannot say we had those features already :) - App Discovery - New Stats pages - Sample Deploying feature AFAIU, we are going to have one/two new features added to the pack which will be given today (maybe low priority but still it's new :) ) Problems - we now have 8 L1s, 26 L2s - QA was running low on resources, so only one engineer was available for last 2+ weeks Partially agree on this. We had Sandapa and had to move her for support. But Nuwan joined testing last week. The reason for not assigning too many QA resources was that we didn't have a feature frozen pack/proper planned release date. - So QA wants to test more On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Yes, thats all fine. I am asking when we will get the pack with all these features/ changes done. Meaning the proper alpha with features frozen. If we still don't know that date, it is also fine, but we can plan the QA based on that. On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe sume...@wso2.com wrote: On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the latest pack in [1]. We could find root cause for some of the intermittent issues that you have reported. But we included some debug logs to possible places, so that we can narrow down the issue if it appeared on latest pack too. Please enable jaggery debug logs before you start testing the pack. [1].
Re: [Dev] App-Manager 1.0 Release Testing Update
Hi, Our concerns were that we had the above mentioned L1s and L2s and added new features in the latest packs, which makes it not ready to be released in two more days. And we have been getting packs like every other day(some with config changes too) so it is a bit hard to manage testing on all the given packs. So to do a decent release we would need more time to test. Since we were running low on headcount we could not allocate more than one in past few weeks. However we have allocated another person to help with AppM testing. Thanks, Nirodha On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Shakar, All these are available on packs. Problems - we now have 8 L1s, 26 L2s - QA was running low on resources, so only one engineer was available for last 2+ weeks - So QA wants to test more On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Yes, thats all fine. I am asking when we will get the pack with all these features/ changes done. Meaning the proper alpha with features frozen. If we still don't know that date, it is also fine, but we can plan the QA based on that. On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe sume...@wso2.com wrote: On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the latest pack in [1]. We could find root cause for some of the intermittent issues that you have reported. But we included some debug logs to possible places, so that we can narrow down the issue if it appeared on latest pack too. Please enable jaggery debug logs before you start testing the pack. [1]. http://builder1.us1.wso2.org/~appm/19-03-2015/ Regards, Dinusha. On Tue, Mar 17, 2015 at 6:39 PM, Yasassri
Re: [Dev] User Manager MySQL Exception
Hi Kasun, I clustered IS 5.0.0 recently using mysql-connector-java-5.1.34-bin.jar and mysql version I used was 5.5.35. I didn't get an exception as such. Cheers! Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Tue, Apr 7, 2015 at 11:12 AM, Inshaf Mahath ins...@wso2.com wrote: Hi Kasun, Did you try on mysql-connector-java-5.1.30.jar? I faced some issues because of different version of jars. But 5.1.30 worked for me. On Tue, Apr 7, 2015 at 1:26 AM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi All, I'm getting a MySQL Error (com.mysql.jdbc.exceptions.MySQLSyntaxErrorException) when I'm trying to manager users via Carbon console. MySQL version in the server is 5.5.41 and the connectorJ version is 5.1.35. I have tried the solution suggested by Darshana in [1] and it did not work for me. Any idea how to resolve this? [1] - https://wso2.org/jira/browse/IDENTITY-1641 Thanks -- Kasun Dananjaya Delgolla Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Tel: +94 11 214 5345 Fax: +94 11 2145300 Mob: + 94 771 771 015 Blog: http://kddcodingparadise.blogspot.com Linkedin: *http://lk.linkedin.com/in/kasundananjaya http://lk.linkedin.com/in/kasundananjaya* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Inshaf Mahath Associate Software Engineer Mobile: +94775907181 WSO2 Inc. Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Applying QOS from developer studio with ESB 4.9.0 release
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Apr 7, 2015 at 11:19 AM, Nandika Jayawardana nand...@wso2.com
wrote:
Yes. Lets have a meeting and get at least one person from all the affected
teams.
Regards
Nandika
On Tue, Apr 7, 2015 at 11:08 AM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Sohani,
Shall we arrange a meeting to discuss this and finalize the approach?
Looks like we have several approaches but still we have not agreed on a
proper solution.
+1. It seems everyone is free tomorrow morning. Therefore, I'll arrange a
meeting tomorrow at 11am.
Thanks,
Sohani
Thanks,
Chanaka
On Tue, Apr 7, 2015 at 10:12 AM, Nandika Jayawardana nand...@wso2.com
wrote:
In BPS, we have to pack the policy file within the bpel project itself
and refer to it in the deploy.xml. We are going to have to update the
deployment code as we are creating the axis service objects dynamically.
Regards
Nandika
On Tue, Apr 7, 2015 at 10:04 AM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Johann/KasunG/Kishanthan,
What would be the way forward to support this feature? We can have the
Developer Studio story completed if we use the allowRoles parameter with
the *SecurityDeploymentIntercepter *class updating the DB. If we are
going with the registry resource property approach, we need to implement
the same logic at a proper place in the identity component.
WDYT?
Thanks,
Chanaka
On Mon, Apr 6, 2015 at 12:25 PM, Johann Nallathamby joh...@wso2.com
wrote:
Hi Kasun/Kishanthan,
Any idea why this was removed ? I thought security-mgt is maintained
by IS team. But looks like others are also working on this component.
On Mon, Apr 6, 2015 at 12:05 PM, Sohani Weerasinghe soh...@wso2.com
wrote:
@Chanaka: Thanks for investigating on this issue.
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Mon, Apr 6, 2015 at 12:02 PM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Johann,
After looking through the new implementation of the
*SecurityDeploymentIntercepter.java
*file in the latest GIT source code[1] , I could find that this
allowRoles parameter related implementation has been removed. Entire
implementation of the *applySecurityParameters(AxisService service,
SecurityScenario secScenario)* method has been removed and that
method is blank. What is the reason for this?
@Sohani: This is the reason that this parameter is not working in
the latest 4.9.0 ESB pack.
[1]
https://github.com/wso2/carbon-identity/blob/master/components/security/org.wso2.carbon.security.mgt/src/main/java/org/wso2/carbon/security/deployment/SecurityDeploymentInterceptor.java
Thanks,
Chanaka
On Mon, Apr 6, 2015 at 11:35 AM, Chanaka Fernando chana...@wso2.com
wrote:
Hi KasunG,
I have checked on the source code of the previous implementation
and according to that, when applying security through Management
console
and through allowRoles service parameter, it executes the same code
on
the Security side (please see below).
*SecurityConfigAdmin.java (Executes when applying through
Management Console)*
if (userGroups != null) {
for (String value : userGroups) {
AuthorizationManager acAdmin =
realm.getAuthorizationManager();
acAdmin.authorizeRole(value,
serviceGroupId+/+service.getName(),
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
}
}
*SecurityDeploymentIntercepter.java (Executes when applying through
allowRoles parameter)*
Parameter allowRolesParameter =
service.getParameter(allowRoles);
if(allowRolesParameter!= null
allowRolesParameter.getValue() != null){
AuthorizationManager manager =
userRealm.getAuthorizationManager();
String resourceName = serviceGroupId + / +
serviceName;
String[] roles =
manager.getAllowedRolesForResource(resourceName,
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
if(roles != null){
for (String role : roles) {
manager.clearRoleAuthorization(role,
resourceName,
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
}
}
String value = (String)
allowRolesParameter.getValue();
String[] allowRoles = value.split(,) ;
if(allowRoles != null){
for(String role : allowRoles){
userRealm.getAuthorizationManager().authorizeRole(role, resourceName,
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
}
}
}
Since this is a service level parameter, we can use this for all
Re: [Dev] App-Manager 1.0 Release Testing Update
On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Sumedha, Dinusha, When do we have the alpha release with feature frozen? Hi Shankar, We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/ lists out all public packs we have hosted). Then Isabelle Chris used this alpha pack to do a series of partner briefings. After these briefings we got feedback to improve following areas: 1. App Publishing flow is too lengthy for a newbie 2. App Policy Mgt should be separated out from App Publishing (thread: [APPM] [IS] Change of XACML based authorization) 3. Make graphs more aesthetic 4. Improve first timers experience better by adding a sample app deployer (thread: dev: App Manager sample deployer) We also discovered following: - We only support EMM 1.0. So need to add support for both EMM 1.0.0 MDM 2.0.0 (thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App Management feature to App Manager) - ES only supports permission check for login only. So we had to implement permission model on top of ES (thread : Life Cycles transition for Apps in APPM) Apart from this RuwanA finished his project on App Discovery (thread: [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS) So after the alpha on 23rd of December, above are the changes we introduced apart from fixing issues reported. On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, This is to update the Latest progress on App Manager Release testing. Currently there are following blockers and critical issues. IMHO these need to be fixed before the release. - Oracle DB script related issues. - BAM toolbox issues/ Stats related issues - Single Logout - BPS integration issues. (Was Fixed with the latest pack (5th April Pack), yet to verify the fix) - Session Related issues. etc. Some of these issues are listed from [1] - [9]. In total(Open, Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues and 15 L4 L5 issues. Along the way we faced several challenges when testing APP-M apart from the blocking issues we faced, following new features were added - App Discovery - New Stats pages - Sample Deploying feature Some features also got changed - EMM integration - XACML policy UI etc. There were some configuration level changes in web-apps as well as in app-manager.xml/ user-mgt.xml which affected the Automation process. Lack of documentation was another issue we faced. Currently we are in the process of testing untested areas and bug fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether we can do a proper round of testing before the planned release date. [1] - https://wso2.org/jira/browse/APPM-718 [2] - https://wso2.org/jira/browse/APPM-715 [3] - https://wso2.org/jira/browse/APPM-686 [4] - https://wso2.org/jira/browse/APPM-651 [5] - https://wso2.org/jira/browse/APPM-481 [6] - https://wso2.org/jira/browse/APPM-324 [7] - https://wso2.org/jira/browse/APPM-511 [8] - https://wso2.org/jira/browse/APPM-544 [9] - https://wso2.org/jira/browse/APPM-639 With Regards, On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, Please find the latest pack in [1]. We could find root cause for some of the intermittent issues that you have reported. But we included some debug logs to possible places, so that we can narrow down the issue if it appeared on latest pack too. Please enable jaggery debug logs before you start testing the pack. [1]. http://builder1.us1.wso2.org/~appm/19-03-2015/ Regards, Dinusha. On Tue, Mar 17, 2015 at 6:39 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, Meeting Notes - AM team will try to fix all the issues related to instability and share a new pack tomorrow. - Testing on oracle will be done based on the time available before the expected release date. - Long running test has to be run by the QA team. (on a standalone setup) - All features and UI's are currently finalized and no major changes will happen. With Regards, On Tue, Mar 17, 2015 at 6:14 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi Dinusha, Sorry for the ambiguity in the mail. Please see my comments in-line Hi All, This is to update the current status of the App Manger release cycle. We had issues initially when testing due to following reasons - There was no decided permission model embedded to AM. This is finalized and we are not going to change the model ! There is a mail thread for this even ! This is an issue we had before March 6th pack, As mentioned the permission model is finalized ATM. - UI got changed along the way There were some usability improvements done after reviewing with UX team. - Features were not finalized. What you mean by features are not finalized ? Along the way there were some new
[Dev] https://github.com/wso2/carbon-commons/pull/75
Hi Carbon Team, Please review and merge [1]. Related jira [2] [1] https://github.com/wso2/carbon-commons/pull/75 [2] https://wso2.org/jira/browse/ESBJAVA-2506 Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Applying QOS from developer studio with ESB 4.9.0 release
Hi All,
Please note that I have arranged a meeting tomorrow at 11am to 12pm to
discuss about this further.
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Apr 7, 2015 at 11:41 AM, Sohani Weerasinghe soh...@wso2.com wrote:
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Apr 7, 2015 at 11:19 AM, Nandika Jayawardana nand...@wso2.com
wrote:
Yes. Lets have a meeting and get at least one person from all the
affected teams.
Regards
Nandika
On Tue, Apr 7, 2015 at 11:08 AM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Sohani,
Shall we arrange a meeting to discuss this and finalize the approach?
Looks like we have several approaches but still we have not agreed on a
proper solution.
+1. It seems everyone is free tomorrow morning. Therefore, I'll arrange a
meeting tomorrow at 11am.
Thanks,
Sohani
Thanks,
Chanaka
On Tue, Apr 7, 2015 at 10:12 AM, Nandika Jayawardana nand...@wso2.com
wrote:
In BPS, we have to pack the policy file within the bpel project itself
and refer to it in the deploy.xml. We are going to have to update the
deployment code as we are creating the axis service objects dynamically.
Regards
Nandika
On Tue, Apr 7, 2015 at 10:04 AM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Johann/KasunG/Kishanthan,
What would be the way forward to support this feature? We can have the
Developer Studio story completed if we use the allowRoles parameter with
the *SecurityDeploymentIntercepter *class updating the DB. If we are
going with the registry resource property approach, we need to implement
the same logic at a proper place in the identity component.
WDYT?
Thanks,
Chanaka
On Mon, Apr 6, 2015 at 12:25 PM, Johann Nallathamby joh...@wso2.com
wrote:
Hi Kasun/Kishanthan,
Any idea why this was removed ? I thought security-mgt is maintained
by IS team. But looks like others are also working on this component.
On Mon, Apr 6, 2015 at 12:05 PM, Sohani Weerasinghe soh...@wso2.com
wrote:
@Chanaka: Thanks for investigating on this issue.
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Mon, Apr 6, 2015 at 12:02 PM, Chanaka Fernando chana...@wso2.com
wrote:
Hi Johann,
After looking through the new implementation of the
*SecurityDeploymentIntercepter.java
*file in the latest GIT source code[1] , I could find that this
allowRoles parameter related implementation has been removed. Entire
implementation of the *applySecurityParameters(AxisService
service, SecurityScenario secScenario)* method has been removed
and that method is blank. What is the reason for this?
@Sohani: This is the reason that this parameter is not working in
the latest 4.9.0 ESB pack.
[1]
https://github.com/wso2/carbon-identity/blob/master/components/security/org.wso2.carbon.security.mgt/src/main/java/org/wso2/carbon/security/deployment/SecurityDeploymentInterceptor.java
Thanks,
Chanaka
On Mon, Apr 6, 2015 at 11:35 AM, Chanaka Fernando
chana...@wso2.com wrote:
Hi KasunG,
I have checked on the source code of the previous implementation
and according to that, when applying security through Management
console
and through allowRoles service parameter, it executes the same code
on
the Security side (please see below).
*SecurityConfigAdmin.java (Executes when applying through
Management Console)*
if (userGroups != null) {
for (String value : userGroups) {
AuthorizationManager acAdmin =
realm.getAuthorizationManager();
acAdmin.authorizeRole(value,
serviceGroupId+/+service.getName(),
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
}
}
*SecurityDeploymentIntercepter.java (Executes when applying
through allowRoles parameter)*
Parameter allowRolesParameter =
service.getParameter(allowRoles);
if(allowRolesParameter!= null
allowRolesParameter.getValue() != null){
AuthorizationManager manager =
userRealm.getAuthorizationManager();
String resourceName = serviceGroupId + / +
serviceName;
String[] roles =
manager.getAllowedRolesForResource(resourceName,
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
if(roles != null){
for (String role : roles) {
manager.clearRoleAuthorization(role,
resourceName,
UserCoreConstants.INVOKE_SERVICE_PERMISSION);
}
}
String value = (String)
Re: [Dev] User Manager MySQL Exception
Hi Inshaf, I have tried using mysql-connector-java-5.1.30.jar, but I'm still getting the same issue. I think it's something with the mysql version + connector compatibility. @Sewmini - You might be using the correct combination. I will have to try that as well. But if anyone can give a solution to this which prevent me from changing versions would be great. Thanks On Tue, Apr 7, 2015 at 4:25 AM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi Kasun, I clustered IS 5.0.0 recently using mysql-connector-java-5.1.34-bin.jar and mysql version I used was 5.5.35. I didn't get an exception as such. Cheers! Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Tue, Apr 7, 2015 at 11:12 AM, Inshaf Mahath ins...@wso2.com wrote: Hi Kasun, Did you try on mysql-connector-java-5.1.30.jar? I faced some issues because of different version of jars. But 5.1.30 worked for me. On Tue, Apr 7, 2015 at 1:26 AM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi All, I'm getting a MySQL Error (com.mysql.jdbc.exceptions.MySQLSyntaxErrorException) when I'm trying to manager users via Carbon console. MySQL version in the server is 5.5.41 and the connectorJ version is 5.1.35. I have tried the solution suggested by Darshana in [1] and it did not work for me. Any idea how to resolve this? [1] - https://wso2.org/jira/browse/IDENTITY-1641 Thanks -- Kasun Dananjaya Delgolla Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Tel: +94 11 214 5345 Fax: +94 11 2145300 Mob: + 94 771 771 015 Blog: http://kddcodingparadise.blogspot.com Linkedin: *http://lk.linkedin.com/in/kasundananjaya http://lk.linkedin.com/in/kasundananjaya* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Inshaf Mahath Associate Software Engineer Mobile: +94775907181 WSO2 Inc. Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Kasun Dananjaya Delgolla Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Tel: +94 11 214 5345 Fax: +94 11 2145300 Mob: + 94 771 771 015 Blog: http://kddcodingparadise.blogspot.com Linkedin: *http://lk.linkedin.com/in/kasundananjaya http://lk.linkedin.com/in/kasundananjaya* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Kafka Inbound in ESB cluster mode.
Hi Chanaka,Ravindra, I was able to fix the issue as you suggested to create a new esb cluster setup. Thanks, Kathees On Tue, Apr 7, 2015 at 10:24 AM, Kathees Rajendram kath...@wso2.com wrote: Hi Chanaka, No,I created the esb cluster setup without elb and tested on that.I am getting same issue. Thanks, Kathees On Tue, Apr 7, 2015 at 9:59 AM, Chanaka Fernando chana...@wso2.com wrote: Hi Kathees, Have you been able to fix your issue with the given suggestions? Thanks, Chanaka On Mon, Apr 6, 2015 at 4:34 PM, Kathees Rajendram kath...@wso2.com wrote: Hi Chanaka, Ok I will create the cluster setup without ELB. @Ravindra, I created the cluster with M8 pack which was built from developer branch. Ok I will try the cluster with esb M8 pack [1]. [1] - https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/ Thanks, Kathees On Mon, Apr 6, 2015 at 3:03 PM, Ravindra Ranwala ravin...@wso2.com wrote: Hi Kathees, I'm not sure which ESB pack are you using. Anyway the M8 pack [1] was working fine for me. Could you please try that out and let us know. [1] https://svn.wso2.org/repos/wso2/people/chanakaf/Alpha-Release/ Thanks Regards, On Mon, Apr 6, 2015 at 2:53 PM, Chanaka Fernando chana...@wso2.com wrote: Hi Kathees, Can you setup a cluster without ELB and check on that? Thanks, Chanaka On Mon, Apr 6, 2015 at 2:50 PM, Kathees Rajendram kath...@wso2.com wrote: Hi Chanaka,Ravindra, I have the setup with a elb,a manager node and a worker node. As Chanaka mentioned I changed taskServerCount parameter value to 1 in both manager and worker node. Still I am getting the same error in both manager and worker node. Thanks, Kathees On Mon, Apr 6, 2015 at 2:24 PM, Chanaka Fernando chana...@wso2.com wrote: [Adding Kathees] On Mon, Apr 6, 2015 at 2:23 PM, Ravindra Ranwala ravin...@wso2.com wrote: Hi Chanaka, Yes, I have encountered with this error while I was testing MSMP tasks in cluster mode. It was an intermittent issue. @Kathees: Could you please restart the manager node again and make sure that you have started one or more workers in the meantime as Chanaka mentioned. AFAIK, manager node collects them as pending tasks and schedules later once workers joined the cluster. Thanks Regards, On Mon, Apr 6, 2015 at 2:12 PM, Chanaka Fernando chana...@wso2.com wrote: Hi Ravindra/Maheeka, Have you observed such an issue when you were testing tasks in cluster mode? Thanks, Chanaka -- Forwarded message -- From: Chanaka Fernando chana...@wso2.com Date: Mon, Apr 6, 2015 at 1:42 PM Subject: Re: Testing Kafka Inbound in ESB cluster mode. To: Kathees Rajendram kath...@wso2.com Cc: DEV dev@wso2.org, Kasun Indrasiri ka...@wso2.com Hi Kathees, Have you started the worker nodes? By theory, Tasks are running on worker nodes. You need to have at least 1 worker node to start executing the tasks. Also there is another configuration file which controls the minimum number of instances to start executing the tasks. This can be configured in the *ESB_HOME/repository/conf/etc/tasks-config.xml* file with the below parameter. taskServerCount2/taskServerCount The value of 2 means that cluster will wait until 2 worker nodes are started for the execution of tasks. Thanks, Chanaka On Mon, Apr 6, 2015 at 12:49 PM, Kathees Rajendram kath...@wso2.com wrote: Hi, I tested Kafka inbound in esb cluster mode. I have added required patches and inbound configuration in manager node. When I start the manger node I am getting following error. Am I missing anything? [2015-04-06 12:32:55,977] INFO - NTaskTaskManager Initialized task manager on manager node. Tenant [-1234] [2015-04-06 12:32:56,089] ERROR - NTaskTaskManager Scheduling task [[NTask::-1234::MyKAFKAListenerEP-KAFKA-EP]::KAFKA-EP] FAILED. Error: No available task nodes for resolving a task location org.wso2.carbon.ntask.common.TaskException: No available task nodes for resolving a task location at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getTaskLocation(ClusteredTaskManager.java:224) at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.locateMemberForTask(ClusteredTaskManager.java:201) at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.getMemberIdFromTaskName(ClusteredTaskManager.java:275) at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager.scheduleTask(ClusteredTaskManager.java:86) at org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NTaskTaskManager.java:82) at org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskTaskManager.java:320) at org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTaskTaskManager.java:332) at org.wso2.carbon.mediation.ntask.internal.NtaskService.updateAndCleanupObservers(NtaskService.java:103) at
Re: [Dev] Implementing HTML support for E-mail Notifications
I'll work with him Suho On Mon, Apr 6, 2015 at 5:23 PM, Kasun Bandara kas...@wso2.com wrote: Thank you for the prompt response @Sagara. I'll do. On Mon, Apr 6, 2015 at 5:18 PM, Sagara Gunathunga sag...@wso2.com wrote: AFAIR Suho showed some stuff related to this feature, please talk to him. Thanks ! On Mon, Apr 6, 2015 at 5:12 PM, Kasun Bandara kas...@wso2.com wrote: Hi Devs, Currently I'm in the middle of assessing the viability of implementing JIRA issue [1] as a sub task of my fast track training project. It's regarding *HTML template support for email notifications*. After carrying out a study on HTML Email developing, i have found that there *isn't* any proper standard (standardized and compatible way that can be rendered by all the email clients) when developing HTML enabled email messages [2] [3]. And i have also found that there are significant amount of constraints embedded with HTML Email such as Higher probability of spamming, End user display issues [Email client incompatibilities] , Development constraints etc . [3] [4]. I would like to know whether there are other viable options or standards i can refer to design and implement the above $subject. Thanks Regards. [1] https://wso2.org/jira/browse/IDENTITY-2989 [2] http://webdesign.tutsplus.com/tutorials/what-you-should-know-about-html-email--webdesign-12908 [3] http://emailmarketing.comm100.com/email-marketing-tutorial/what-is-html-email.aspx [4] http://www.activecampaign.com/email-design-guide/ https://wso2.org/jira/browse/IDENTITY-2989 -- Kasun Bandara *Software Engineer* Mobile : +94 (0) 718 338 360 %2B94%20%280%29%20773%20451194 kas...@wso2.com thili...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Kasun Bandara *Software Engineer* Mobile : +94 (0) 718 338 360 %2B94%20%280%29%20773%20451194 kas...@wso2.com thili...@wso2.com -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Publishing Gmail Connector
Hi Shenthuran, Yeap both does the similar functionality, however interfaces are quite different. Thus better to go with as new connector. On Mon, Mar 23, 2015 at 8:59 AM, Senduran Balasubramaniyam sendu...@wso2.com wrote: Hi Keerthika, I think it is better to publish with different version, rather than publishing as a new connector. Since both the connectors have similar functionality. But I wonder how to support if we have to upload both the connectors in ESB. Regards Senduran On Fri, Mar 20, 2015 at 12:25 PM, Keerthika Mahendralingam keerth...@wso2.com wrote: Hi All, Currently we have two different Gmail connectors based on sdk and rest api. How to publish these in connector store? Do I need to publish these as different connectors with different names or with versioning? Thanks, -- dev-requ...@wso2.org Keerthika Mahendralingam Associate Software Engineer Mobile :+94 (0) 776 121144 keerth...@wso2.com WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Senduran * Software Engineer, WSO2, Inc.; http://wso2.com/ http://wso2.com/ Mobile: +94 77 952 6548 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com http://wso2.com/* *Mobile:(+94)777219209* [image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn] http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare] http://www.slideshare.net/vanjikumaran 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, re-transmit, 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Adding apacheds/1.5.7.wso2v3 and nimbus/2.26.1.wso2v3
Fixed the PR [1] with mentioned changes. Thanks. [1]. https://github.com/wso2/orbit/pull/80 Regards, Prasad. On Fri, Apr 3, 2015 at 3:18 AM, Aruna Karunarathna ar...@wso2.com wrote: Hi Prasad, Please follow the Orbit bundle release guide. I have added some comments regarding the PR. Please check. Regards, Aruna On Wed, Apr 1, 2015 at 11:41 PM, Prasad Tissera pras...@wso2.com wrote: Hi Kernel team, Can you please review and merge [1]. [1]. https://github.com/wso2/orbit/pull/80 Thanks, -- Prasad Tissera Software Engineer. Mobile : +94777223444 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com -- Prasad Tissera Software Engineer. Mobile : +94777223444 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error adding API in 1.9.0 pack
Hi, I tried to run some UI tests in APIM git 1.9.0 code base. Found out that error occurs while adding API. Tried the same thing with built pack manually and error is there. Is this known bug? It says constraint violation in AM_API table. I checked the h2 DB. There were no records in the DB. [2015-04-07 19:14:33,647] ERROR - ApiMgtDAO Error while adding the API: admin-ww-1.0.0 to the database org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: CONSTRAINT_INDEX_73 ON PUBLIC.AM_API(API_PROVIDER, API_NAME, API_VERSION); SQL statement: INSERT INTO AM_API (API_PROVIDER, API_NAME, API_VERSION, CONTEXT) VALUES (?,?,?,?) [23001-140] at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) at org.h2.message.DbException.get(DbException.java:167) at org.h2.message.DbException.get(DbException.java:144) at org.h2.index.BaseIndex.getDuplicateKeyException(BaseIndex.java:157) at org.h2.index.PageBtree.find(PageBtree.java:121) at org.h2.index.PageBtreeLeaf.addRow(PageBtreeLeaf.java:138) at org.h2.index.PageBtreeLeaf.addRowTry(PageBtreeLeaf.java:93) at org.h2.index.PageBtreeIndex.addRow(PageBtreeIndex.java:90) at org.h2.index.PageBtreeIndex.add(PageBtreeIndex.java:81) at org.h2.table.RegularTable.addRow(RegularTable.java:116) at org.h2.command.dml.Insert.insertRows(Insert.java:120) at org.h2.command.dml.Insert.update(Insert.java:82) at org.h2.command.CommandContainer.update(CommandContainer.java:70) at org.h2.command.Command.executeUpdate(Command.java:199) at org.h2.jdbc.JdbcPreparedStatement.execute(JdbcPreparedStatement.java:179) at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI(ApiMgtDAO.java:6075) at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:391) at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.addAPI(UserAwareAPIProvider.java:46) at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.saveAPI(APIProviderHostObject.java:864) at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsFunction_createAPI(APIProviderHostObject.java:773) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386) at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) at org.jaggeryjs.rhino.publisher.modules.api.c3._c_anonymous_5(/publisher/modules/api/add.jag:99) at org.jaggeryjs.rhino.publisher.modules.api.c3.call(/publisher/modules/api/add.jag) at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430) at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269) at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97) at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42) at org.jaggeryjs.rhino.publisher.modules.api.c0._c_anonymous_30(/publisher/modules/api/module.jag:98) at org.jaggeryjs.rhino.publisher.modules.api.c0.call(/publisher/modules/api/module.jag) at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0._c_anonymous_2(/publisher/site/blocks/item-design/ajax/add.jag:67) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0.call(/publisher/site/blocks/item-design/ajax/add.jag) at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0._c_script_0(/publisher/site/blocks/item-design/ajax/add.jag:18) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0.call(/publisher/site/blocks/item-design/ajax/add.jag) at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394) at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0.call(/publisher/site/blocks/item-design/ajax/add.jag) at org.jaggeryjs.rhino.publisher.site.blocks.item_design.ajax.c0.exec(/publisher/site/blocks/item-design/ajax/add.jag) at org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:570) at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273) at org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:432) at org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29) at javax.servlet.http.HttpServlet.service(HttpServlet.java:755) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749) at
Re: [Dev] Authenticating with WSO2 Identity Server 5.0.0
Hello, I am checking to see if anyone has gotten IS 5.0.0 with the security patch working with a read-only connection to an LDAP server. It is possible that I am connecting to a VDS server, not an LDAP server. Any help would be greatly appreciated. Michael Eyre Integration SME, Solution Architecture and Integration [cid:2AD003B4-80B8-4759-B32C-8006E1FF0519] Work: 570-957-4698 Mobile: 610-462-5823 michael.e...@sanofi.commailto:michael.e...@sanofi.com From: Harsha Thirimanna [mailto:hars...@wso2.com] Sent: Thursday, April 02, 2015 9:15 PM To: Eyre, Michael (sanofi pasteur) Cc: dominique.debaill...@woana.net; Akila Ravihansa Perera; WSO2 Developers' List Subject: Re: [Dev] Authenticating with WSO2 Identity Server 5.0.0 What do you mean by applying patch to the Identity Server 5.0.0 ? Did you mean by Service Pack ? Harsha Thirimanna Senior Software Engineer; WSO2, Inc.; http://wso2.comhttp://wso2.com/ email: hars...@wso2.commailto:az...@wso2.com cell: +94 71 5186770 , +94 774617784 twitter: http://twitter.com/http://twitter.com/afkham_azeezharshathirimann linked-in: http:http://lk.linkedin.com/in/afkhamazeez//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 Lean . Enterprise . Middleware On Thu, Apr 2, 2015 at 6:48 PM, michael.e...@sanofipasteur.commailto:michael.e...@sanofipasteur.com wrote: I can try that, but the user I have does not have write access to the server. Michael Eyre From: Dominique Debailleux [mailto:dominique.debaill...@woana.netmailto:dominique.debaill...@woana.net] Sent: Thursday, April 02, 2015 8:40 AM To: Akila Ravihansa Perera Cc: Eyre, Michael (sanofi pasteur); WSO2 Developers' List Subject: Re: [Dev] Authenticating with WSO2 Identity Server 5.0.0 Hi Michael You should try the read and write user store manager not the read only one. Dominique 2015-04-01 22:20 GMT+02:00 Akila Ravihansa Perera raviha...@wso2.commailto:raviha...@wso2.com: Hi Michael, Would it be possible for you to share the configs and wso2carbon.log? It's not easy to guess the problem without looking at the logs. Do you have email addresses as usernames? In that case you need to enable EnableEmailUsers property in carbon.xml. Did you configure a DomainName for your LDAP userstore? You can try to authenticate with domain_name\username Thanks. On Wed, Apr 1, 2015 at 9:45 AM, michael.e...@sanofipasteur.commailto:michael.e...@sanofipasteur.com wrote: I am working at evaluating WSO2 Identity Server and API Manager. I am trying to connect the Identity Server with our VDS/LDAP server. I have created the UserStoreManager configuration in the user-mgt.xml file and set the AdminUser to the same user name (not the full connectionName), but I am not able to authenticate with this user. When I navigate to the local carbon instance, enter the username and password, I get an login failure message. The UserStoreManager is a read-only connection to the VDS server. I have also disabled the internal LDAP server. If I enable the internal LDAP server and configure the connection to the internal VDS server with a secondary user store, I can log in with the standard “admin” user and the Travelocity.com example works with that user, but even if I add one of the VDS user to the Travelocity internal group, I cannot authenticate with SAML SSO example. I am trying to do two things. 1.Log into the Identity Server Management console with an internal LDAP user 2. Authenticate with Travelocity SAML SSO example with an internal LDAP user, either as a secondary user store or when the internal LDAP server is the primary (and only) user store. Thanks for your help on this issue Michael Eyre ___ Dev mailing list Dev@wso2.orgmailto:Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Akila Ravihansa Perera Software Engineer, WSO2 Blog: http://ravihansa3000.blogspot.com ___ Dev mailing list Dev@wso2.orgmailto:Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dominique Debailleux WoAnA - small.but.robust [Accèder au profil LinkedIn de Dominique Debailleux]http://www.linkedin.com/in/dominiquedebailleux ___ Dev mailing list Dev@wso2.orgmailto:Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please review and merge PR for APPM-731
Hi, Please review and merge PR[1] for APPM-731[2] [1]. https://github.com/wso2/carbon-appmgt/pull/28 [2]. https://wso2.org/jira/browse/APPM-731 *Sajith Abeywardhana* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka. Mobile: +94772260485 Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the PR
Hi Johan, This is the fix PR [1] for the JIRA [2]. [1]. https://github.com/wso2/carbon-identity/pull/173 [2]. https://wso2.org/jira/browse/IDENTITY-3062 -- Lasitha Wattaladeniya Software Engineer WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94719397528 Blog : techreadme.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] What happens when we have multiple versions of same jar in plugins?
Hi all, If there are multiple versions of the same jar in the repository/components/plugins folder, which version is actually used at runtime? Is it higher version of the jar or a random one? Thank you. -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What happens when we have multiple versions of same jar in plugins?
Hi Lakshani, You can check the version in use from the bundles.info file. CARBON_HOME/repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/ bundles.info On Tue, Apr 7, 2015 at 11:06 PM, Lakshani Gamage laksh...@wso2.com wrote: Hi all, If there are multiple versions of the same jar in the repository/components/plugins folder, which version is actually used at runtime? Is it higher version of the jar or a random one? Thank you. -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Tharindu Edirisinghe Software Engineer | WSO2 Inc Identity Server Team mobile : +94 775 181586 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What happens when we have multiple versions of same jar in plugins?
Hi Tharindu Aruna, Thanks for the quick response. Regards, Lakshani. On Tue, Apr 7, 2015 at 11:16 PM, Aruna Karunarathna ar...@wso2.com wrote: Hi Lakshani, It depends, if the jar is listed in the bundles.info file, then that jar will be effective at the runtime. So in order to bundle inside the plugins folder to be used, it must be listed in the bundles.info file. If the jar is not in the bundles.info file, but in the plugins folder, that jar will be not effective in the runtime. So when in the runtime for effective bundles, according to the import versions, of the using bundle, the relevant export bundle will be used, if version is not defined, highest active version is used. Regards, Aruna On Tue, Apr 7, 2015 at 10:36 AM, Lakshani Gamage laksh...@wso2.com wrote: Hi all, If there are multiple versions of the same jar in the repository/components/plugins folder, which version is actually used at runtime? Is it higher version of the jar or a random one? Thank you. -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What happens when we have multiple versions of same jar in plugins?
Hi Lakshani, It depends, if the jar is listed in the bundles.info file, then that jar will be effective at the runtime. So in order to bundle inside the plugins folder to be used, it must be listed in the bundles.info file. If the jar is not in the bundles.info file, but in the plugins folder, that jar will be not effective in the runtime. So when in the runtime for effective bundles, according to the import versions, of the using bundle, the relevant export bundle will be used, if version is not defined, highest active version is used. Regards, Aruna On Tue, Apr 7, 2015 at 10:36 AM, Lakshani Gamage laksh...@wso2.com wrote: Hi all, If there are multiple versions of the same jar in the repository/components/plugins folder, which version is actually used at runtime? Is it higher version of the jar or a random one? Thank you. -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please review and merge PR for APPM-731
Thanks Sajith .. Usually custom mediators should go into repository/droppings directory .. But since this is a part of AppM functionality, it's good to include as feature and bundle into pack. So create a feature for this and include into appm aggregate feature. You may need to keep modified main sequence inside your feature. Regards, Dinusha. On Tue, Apr 7, 2015 at 9:10 PM, Sajith Abeywardhana saji...@wso2.com wrote: Hi, Please review and merge PR[1] for APPM-731[2] [1]. https://github.com/wso2/carbon-appmgt/pull/28 [2]. https://wso2.org/jira/browse/APPM-731 *Sajith Abeywardhana* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka. Mobile: +94772260485 Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] About boxcarring and set-cookie issue.
Hi Harsha,
Using DSS 3.2.2 it work fine but when I try with a java client I noted the
following:
1. Using the stub generated by the WSO2 Developer Studio with the
WSDL created by the DSS does not work. I´ve got an error making the call to
begin boxcarring, the java client expected some response data, as I can see in
the stub class, but nothing is returned.
2. To overcome the issue in point 1 I used the WSDL generated by WSO2
5.2.1 for the same service, then I generated the stub and my java client worked
fine, using the data service deployed in WSO2 DSS, of course.
3. When all my BE are fine and online it work just fine, If an error
occurs, because of an offline DB, I´ve got a DataServiceFault as I expected,
see [1], but with an error during the response processing, see [2].
[1] axis2ns20:DataServiceFault
xmlns:axis2ns20=http://ws.wso2.org/dataservice;axis2ns20:current_params{numerocell=53242123}/axis2ns20:current_paramsaxis2ns20:current_request_nameobtenerUsuarioSaldotest3/axis2ns20:current_request_nameaxis2ns20:nested_exceptionDS
Fault Message: Error in opening DBMS connection.
DS Code: UNKNOWN_ERROR
Nested Exception:-
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
Last packet sent to the server was 0 ms ago.
/axis2ns20:nested_exceptionaxis2ns20:source_data_serviceaxis2ns20:location\TransferenciaTest-1.0.0.dbs/axis2ns20:locationaxis2ns20:default_namespacehttp://jorgesoftdevelop.com/test/axis2ns20:default_namespaceaxis2ns20:description/axis2ns20:data_service_nameTransferenciaTest/axis2ns20:data_service_name/axis2ns20:source_data_serviceaxis2ns20:ds_codeDATABASE_ERROR/axis2ns20:ds_code/axis2ns20:DataServiceFault
[2] org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException: element
text content may not contain START_ELEMENT
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
com.jorgesoftdevelop.test.TransferenciaTestStub.fromOM(TransferenciaTestStub.java:7700)
at
com.jorgesoftdevelop.test.TransferenciaTestStub.obtenerUsuarioSaldotest3(TransferenciaTestStub.java:846)
at com.jorgesoftdevelop.test.ClienteWS.main(ClienteWS.java:52)
Caused by: java.lang.Exception: javax.xml.stream.XMLStreamException: element
text content may not contain START_ELEMENT
at
com.jorgesoftdevelop.test.TransferenciaTestStub$DataServiceFault$Factory.parse(TransferenciaTestStub.java:6013)
at
com.jorgesoftdevelop.test.TransferenciaTestStub.fromOM(TransferenciaTestStub.java:7638)
... 2 more
Caused by: javax.xml.stream.XMLStreamException: element text content may not
contain START_ELEMENT
at
org.apache.axiom.om.impl.SwitchingWrapper.getElementText(SwitchingWrapper.java:990)
at
javax.xml.stream.util.StreamReaderDelegate.getElementText(Unknown Source)
at
com.jorgesoftdevelop.test.TransferenciaTestStub$DataServiceFault$Factory.parse(TransferenciaTestStub.java:5992)
... 3 more
Any idea?
Jorge.
De: Harsha Kumara [mailto:hars...@wso2.com]
Enviado el: miércoles, 1 de abril de 2015 3:49
Para: Jorge
CC: WSO2 Developers' List
Asunto: Re: [Dev] About boxcarring and set-cookie issue.
Hi Jorge,
There was some fixes went for the the data services components which is
available in DSS 3.2.2 release to support box caring with ESB. AS 5.2.1 does
not contain those fixes. You may try this with the DSS 3.2.2. You can follow
the steps mentioned in [1].
[1] -
http://harshcreationz.blogspot.com/2015/02/boxcarring-sample-with-wso2-dss-and.html
http://harshcreationz.blogspot.com/2015/02/boxcarring-sample-with-wso2-dss-and.html
Thanks,
Harsha
On Wed, Apr 1, 2015 at 12:44 AM, Jorge mailto:isildur...@gmail.com
isildur...@gmail.com wrote:
In my dataservice the begin_boxcar has only only an input message, without and
output message.
porttype:
wsdl:operation name=begin_boxcarwsdl:documentationControl operation for
beginning a boxcarring session/wsdl:documentationwsdl:input
message=ns0:begin_boxcarRequest
wsaw:Action=urn:begin_boxcar//wsdl:operation
binding:
wsdl:operation name=begin_boxcarsoap:operation
soapAction=urn:begin_boxcar style=document/wsdl:inputsoap:body
use=literal//wsdl:input/wsdl:operation
Without the property name=OUT_ONLY value=true scope=default
type=STRING description=solo salida/ the proxy raise several error in
console.
Jorge.
2015-03-31 14:37 GMT-04:00 Harsha Kumara mailto:hars...@wso2.com
hars...@wso2.com:
Hi Jorge,
I'm not sure this is because you have call the begin_boxcar operation as out
only operation. Just remove it and try. Also you can find complete working
scenario in [1].
[1] -
http://harshcreationz.blogspot.com/2015/02/boxcarring-sample-with-wso2-dss-and.html
[Dev] [API-M] Can we create APIs via admin services in API Manager?
Hi Devs, I was able to create APIs using publisher rest API[1]. Just wanted to check whether I can do $Subject? There is an admin service RestApiAdmin in API Manager. This service has a method to add an API. When I tested it with SoapUI, the request looks like below; *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://org.apache.axis2/xsd http://org.apache.axis2/xsd xmlns:xsd1=http://api.rest.carbon.wso2.org/xsd http://api.rest.carbon.wso2.org/xsd soapenv:Header/ soapenv:Body xsd:addApi !--Optional:-- xsd:apiData!--Optional:-- xsd1:context?/xsd1:context!--Optional:-- xsd1:fileName?/xsd1:fileName!--Optional:-- xsd1:host?/xsd1:host!--Optional:-- xsd1:name?/xsd1:name!--Optional:-- xsd1:port?/xsd1:port!--Zero or more repetitions:--xsd1:resources !--Optional:-- xsd1:contentType?/xsd1:contentType !--Optional:-- xsd1:faultSeqXml?/xsd1:faultSeqXml !--Optional:-- xsd1:faultSequenceKey?/xsd1:faultSequenceKey !--Optional:-- xsd1:inSeqXml?/xsd1:inSeqXml !--Optional:-- xsd1:inSequenceKey?/xsd1:inSequenceKey !--Zero or more repetitions:-- xsd1:methods?/xsd1:methods !--Optional:-- xsd1:outSeqXml?/xsd1:outSeqXml !--Optional:-- xsd1:outSequenceKey?/xsd1:outSequenceKey !--Optional:-- xsd1:protocol?/xsd1:protocol !--Optional:-- xsd1:uriTemplate?/xsd1:uriTemplate !--Optional:-- xsd1:urlMapping?/xsd1:urlMapping !--Optional:-- xsd1:userAgent?/xsd1:userAgent/xsd1:resources /xsd:apiData /xsd:addApi /soapenv:Body/soapenv:Envelope* But seems some important parameters like version, visibility, tiers, end-points...etc are missing here. Please advice me whether it is possible to do $Subject. 1. https://docs.wso2.com/display/AM180/Publisher+APIs Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 IS 5.1.0 with Carbon Kernel 4.4.0
I got following error while building the product from the trunk... Can you please provide the steps to build...? [INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon.identity:org.wso2.carbon.identity.user.account.connector:[unknown-version] (/Users/prabath/git/wso2/carbon-identity/components/user-mgt/org.wso2.carbon.identity.user.account.connector/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.wso2.carbon.identity:identity:pom:4.3.4-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 22, column 13 - [Help 2] Thanks regards, -Prabath On Fri, Apr 3, 2015 at 9:30 AM, Malithi Edirisinghe malit...@wso2.com wrote: Hi All, Please find WSO2 IS 5.1.0 built with Carbon Kernel 4.4.0 supporting Java 7 and Java 8 at [1]. Your feedback is most welcome, and any issues can be reported on our JIRA at [2]. [1] https://svn.wso2.org/repos/wso2/people/isteam/ispacks/5.1.0-SNAPSHOT.build1/wso2is-5.1.0-SNAPSHOT.zip [2] https://wso2.org/jira/browse/IDENTITY WSO2 IS Team -- Malithi Edirisinghe Senior Software Engineer WSO2 Inc. Mobile : +94 (0) 718176807 malit...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +1 650 625 7950 http://blog.facilelogin.com http://blog.api-security.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Implementing HTML support for E-mail Notifications
Look like you are reinventing the notification as a separate component, please use the Event Publisher[1] inserted. Suho [1] https://github.com/wso2/carbon-event-processing/tree/master/components/event-publisher On Tue, Apr 7, 2015 at 4:42 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: I'll work with him Suho On Mon, Apr 6, 2015 at 5:23 PM, Kasun Bandara kas...@wso2.com wrote: Thank you for the prompt response @Sagara. I'll do. On Mon, Apr 6, 2015 at 5:18 PM, Sagara Gunathunga sag...@wso2.com wrote: AFAIR Suho showed some stuff related to this feature, please talk to him. Thanks ! On Mon, Apr 6, 2015 at 5:12 PM, Kasun Bandara kas...@wso2.com wrote: Hi Devs, Currently I'm in the middle of assessing the viability of implementing JIRA issue [1] as a sub task of my fast track training project. It's regarding *HTML template support for email notifications*. After carrying out a study on HTML Email developing, i have found that there *isn't* any proper standard (standardized and compatible way that can be rendered by all the email clients) when developing HTML enabled email messages [2] [3]. And i have also found that there are significant amount of constraints embedded with HTML Email such as Higher probability of spamming, End user display issues [Email client incompatibilities] , Development constraints etc . [3] [4]. I would like to know whether there are other viable options or standards i can refer to design and implement the above $subject. Thanks Regards. [1] https://wso2.org/jira/browse/IDENTITY-2989 [2] http://webdesign.tutsplus.com/tutorials/what-you-should-know-about-html-email--webdesign-12908 [3] http://emailmarketing.comm100.com/email-marketing-tutorial/what-is-html-email.aspx [4] http://www.activecampaign.com/email-design-guide/ https://wso2.org/jira/browse/IDENTITY-2989 -- Kasun Bandara *Software Engineer* Mobile : +94 (0) 718 338 360 %2B94%20%280%29%20773%20451194 kas...@wso2.com thili...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Kasun Bandara *Software Engineer* Mobile : +94 (0) 718 338 360 %2B94%20%280%29%20773%20451194 kas...@wso2.com thili...@wso2.com -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge PR for IDENTITY-3187
Hi Johan, $subject for [1] related to the [2] [1] https://github.com/wso2/carbon-identity/pull/174 [2] https://wso2.org/jira/browse/IDENTITY-3187 thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-in: **http: http://lk.linkedin.com/in/afkhamazeez**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Can we create APIs via admin services in API Manager?
Hi Rajkumar, There aren't any admin services available for adding APIs on the API Manager. What is available are the Jaggery REST APIs that you already found out. The RestAPIAdminService is used for adding APIs in the ESB. Hence the same is used internally within API Manager for creating the Synapse artifact corresponding to the API that is added through the API Publisher. Thanks, NuwanD. On Wed, Apr 8, 2015 at 7:15 AM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Hi Devs, I was able to create APIs using publisher rest API[1]. Just wanted to check whether I can do $Subject? There is an admin service RestApiAdmin in API Manager. This service has a method to add an API. When I tested it with SoapUI, the request looks like below; *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://org.apache.axis2/xsd http://org.apache.axis2/xsd xmlns:xsd1=http://api.rest.carbon.wso2.org/xsd http://api.rest.carbon.wso2.org/xsd soapenv:Header/ soapenv:Body xsd:addApi !--Optional:-- xsd:apiData!--Optional:-- xsd1:context?/xsd1:context!--Optional:-- xsd1:fileName?/xsd1:fileName!--Optional:-- xsd1:host?/xsd1:host!--Optional:-- xsd1:name?/xsd1:name!--Optional:-- xsd1:port?/xsd1:port!--Zero or more repetitions:--xsd1:resources !--Optional:-- xsd1:contentType?/xsd1:contentType !--Optional:-- xsd1:faultSeqXml?/xsd1:faultSeqXml !--Optional:-- xsd1:faultSequenceKey?/xsd1:faultSequenceKey !--Optional:-- xsd1:inSeqXml?/xsd1:inSeqXml !--Optional:-- xsd1:inSequenceKey?/xsd1:inSequenceKey !--Zero or more repetitions:-- xsd1:methods?/xsd1:methods !--Optional:-- xsd1:outSeqXml?/xsd1:outSeqXml !--Optional:-- xsd1:outSequenceKey?/xsd1:outSequenceKey !--Optional:-- xsd1:protocol?/xsd1:protocol !--Optional:-- xsd1:uriTemplate?/xsd1:uriTemplate !--Optional:-- xsd1:urlMapping?/xsd1:urlMapping !--Optional:-- xsd1:userAgent?/xsd1:userAgent/xsd1:resources /xsd:apiData /xsd:addApi /soapenv:Body/soapenv:Envelope* But seems some important parameters like version, visibility, tiers, end-points...etc are missing here. Please advice me whether it is possible to do $Subject. 1. https://docs.wso2.com/display/AM180/Publisher+APIs Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Can we create APIs via admin services in API Manager?
Got it. Thanks Nuwan for the quick response! Thanks. On Wed, Apr 8, 2015 at 9:14 AM, Nuwan Dias nuw...@wso2.com wrote: Hi Rajkumar, There aren't any admin services available for adding APIs on the API Manager. What is available are the Jaggery REST APIs that you already found out. The RestAPIAdminService is used for adding APIs in the ESB. Hence the same is used internally within API Manager for creating the Synapse artifact corresponding to the API that is added through the API Publisher. Thanks, NuwanD. On Wed, Apr 8, 2015 at 7:15 AM, Rajkumar Rajaratnam rajkum...@wso2.com wrote: Hi Devs, I was able to create APIs using publisher rest API[1]. Just wanted to check whether I can do $Subject? There is an admin service RestApiAdmin in API Manager. This service has a method to add an API. When I tested it with SoapUI, the request looks like below; *soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=http://org.apache.axis2/xsd http://org.apache.axis2/xsd xmlns:xsd1=http://api.rest.carbon.wso2.org/xsd http://api.rest.carbon.wso2.org/xsd soapenv:Header/ soapenv:Body xsd:addApi !--Optional:-- xsd:apiData!--Optional:-- xsd1:context?/xsd1:context!--Optional:-- xsd1:fileName?/xsd1:fileName!--Optional:-- xsd1:host?/xsd1:host!--Optional:-- xsd1:name?/xsd1:name!--Optional:-- xsd1:port?/xsd1:port!--Zero or more repetitions:--xsd1:resources !--Optional:-- xsd1:contentType?/xsd1:contentType !--Optional:-- xsd1:faultSeqXml?/xsd1:faultSeqXml !--Optional:-- xsd1:faultSequenceKey?/xsd1:faultSequenceKey !--Optional:-- xsd1:inSeqXml?/xsd1:inSeqXml !--Optional:-- xsd1:inSequenceKey?/xsd1:inSequenceKey !--Zero or more repetitions:-- xsd1:methods?/xsd1:methods !--Optional:-- xsd1:outSeqXml?/xsd1:outSeqXml !--Optional:-- xsd1:outSequenceKey?/xsd1:outSequenceKey !--Optional:-- xsd1:protocol?/xsd1:protocol !--Optional:-- xsd1:uriTemplate?/xsd1:uriTemplate !--Optional:-- xsd1:urlMapping?/xsd1:urlMapping !--Optional:-- xsd1:userAgent?/xsd1:userAgent/xsd1:resources /xsd:apiData /xsd:addApi /soapenv:Body/soapenv:Envelope* But seems some important parameters like version, visibility, tiers, end-points...etc are missing here. Please advice me whether it is possible to do $Subject. 1. https://docs.wso2.com/display/AM180/Publisher+APIs Thanks. -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Rajkumar Rajaratnam Committer PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
