[jira] [Resolved] (STRATOS-1277) Wrong HTTP status code returned for Conflict - adding a deployment/application policy

[ https://issues.apache.org/jira/browse/STRATOS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chamila de Alwis resolved STRATOS-1277. --- Resolution: Fixed Fix Version/s: 4.1.0 RC1 Fixed in 477c366bbdd3541b48a84ef72

[jira] [Resolved] (STRATOS-1280) Wrong HTTP status code returned - POST /cartridgeGroups

[ https://issues.apache.org/jira/browse/STRATOS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chamila de Alwis resolved STRATOS-1280. --- Resolution: Fixed Fix Version/s: 4.1.0 RC1 Fixed in b65ede05907559f25a359

[jira] [Resolved] (STRATOS-1275) Wrong HTTP status code returned - GET /cartridges/filter/{filter}

[ https://issues.apache.org/jira/browse/STRATOS-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chamila de Alwis resolved STRATOS-1275. --- Resolution: Fixed Fix Version/s: 4.1.0 RC1 Fixed in 2a822d99d8b2c68c667476f79

[jira] [Resolved] (STRATOS-1278) Wrong HTTP status code returned - GET /cartridgeGroups/{groupDefinitionName}

[ https://issues.apache.org/jira/browse/STRATOS-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chamila de Alwis resolved STRATOS-1278. --- Resolution: Fixed Fix Version/s: 4.1.0 RC1 Fixed in 2a822d99d8b2c68c667476f79

[Q][Issue] Error given when deploying sample - app-bursting-pattern

Hi Devs, When executing the command [1] to deploy the app-bursting-pattern application, I was given with an error [2] . Do you know what might be causing this error? According to the error i tried removing network partition 1 from the application policy and then tried adding and deploying the app

Re: [Q?] Questions on 4.1.0-Beta Testing Stratos with Kubernetes

Hi Devs, Please disregard this mail as I managed to get the required clarification offline. I have added the replies to my Q's inline FYI. Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. On Fri, Apr 17, 2015 at 11:16 AM, Mariangela H

[jira] [Resolved] (STRATOS-1270) Wrong HTTP output - DELETE /deploymentPolicies/{deploymentPolicyId}

[ https://issues.apache.org/jira/browse/STRATOS-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-1270. --- Resolution: Not A Problem Now as a status message is passed the 204 status code is n

Re: [Question] Is is correct for two different status codes appear when adding a tenant?

Has a final decision been reached regarding the response message format? Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Thu, Mar 19, 2015 at 6:11 PM, Vishanth Balasubr

[GitHub] stratos pull request: Beta improvments

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/286 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[jira] [Created] (STRATOS-1336) Rename sample folder - esb-php-nested-with-esb-php-nested-with-mysql-php-app

Shavindri Dissanayake created STRATOS-1336: -- Summary: Rename sample folder - esb-php-nested-with-esb-php-nested-with-mysql-php-app Key: STRATOS-1336 URL: https://issues.apache.org/jira/browse/STRATOS-1336

[Q?] Questions on 4.1.0-Beta Testing Stratos with Kubernetes

Hi Devs, I created [1] by merging the instructions that we mentioned in [4] and the instructions that we provided in [2]. I have the following questions with regard to the info on 4.1.0-Beta Testing Stratos with Kubernetes [1] wiki page. (1) In the mail thread [3] Imesh mentioned that it is incor

[Q] - Verifying sample name - esb-php-nested-with-esb-php-nested-with-mysql-php-app

Hi Devs, Need your help in clarifying a very minor detail ,as am documenting the samples. In the samples folder under the applications folder there is folder named " *esb-php-nested-with-esb-php-nested-with-mysql-php-app*". Is this a mistake or was this done intentionally to bring out some meani