February 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNMGMT-55) Add newline for error responses in REST

by Nick Scavelli (JIRA)

Nick Scavelli created GTNMGMT-55: ------------------------------------ Summary: Add newline for error responses in REST Key: GTNMGMT-55 URL: https://issues.jboss.org/browse/GTNMGMT-55 Project: GateIn Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: rest Reporter: Nick Scavelli Assignee: Nick Scavelli Priority: Minor Fix For: 2.0.0-Beta01 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2820) Unable to clone page (PageService) in a different destination

by Gregory SEBERT (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2820?page=com.atlassian.jira.pl... ] Gregory SEBERT updated GTNPORTAL-2820: -------------------------------------- Description: In the PageManagement service, when I clone a page to a different destination, I received an exception : "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName()); I have a look at the implementation, I find a typo mistake on line 273: org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage(); It should be : org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage(); Best regards, Grégory was: In the PageManagement service, when I clone a page to a different destination, I received an exception : "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName()); I have a look at the implementation, I find a typo mistake on line 273: org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage(); It should be : org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage(); Best regards; Grégory > Unable to clone page (PageService) in a different destination > ------------------------------------------------------------- > > Key: GTNPORTAL-2820 > URL: https://issues.jboss.org/browse/GTNPORTAL-2820 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java API > Affects Versions: 3.5.0.Final > Environment: Gatein 3.5.2 Final > Reporter: Gregory SEBERT > > In the PageManagement service, when I clone a page to a different destination, I received an exception : > "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName()); > I have a look at the implementation, I find a typo mistake on line 273: > org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage(); > It should be : > org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage(); > Best regards, > Grégory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2820) Unable to clone page (PageService) in a different destination

by Gregory SEBERT (JIRA)

Gregory SEBERT created GTNPORTAL-2820: ----------------------------------------- Summary: Unable to clone page (PageService) in a different destination Key: GTNPORTAL-2820 URL: https://issues.jboss.org/browse/GTNPORTAL-2820 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Java API Affects Versions: 3.5.0.Final Environment: Gatein 3.5.2 Final Reporter: Gregory SEBERT In the PageManagement service, when I clone a page to a different destination, I received an exception : "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName()); I have a look at the implementation, I find a typo mistake on line 273: org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage(); It should be : org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage(); Best regards; Grégory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2816) Fix authorization for pages resource in REST API

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2816?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-2816: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/329 > Fix authorization for pages resource in REST API > ------------------------------------------------ > > Key: GTNPORTAL-2816 > URL: https://issues.jboss.org/browse/GTNPORTAL-2816 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Reporter: Nick Scavelli > Assignee: Nick Scavelli > > When someone doesn't have access to a site, they are returned a 200 with a null response body when accessing the pages resource of that site, i.e. /api/spaces/platform/administrators/pages -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2815) Support update for page in REST API

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2815?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-2815: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/329 > Support update for page in REST API > ----------------------------------- > > Key: GTNPORTAL-2815 > URL: https://issues.jboss.org/browse/GTNPORTAL-2815 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST API > Reporter: Nick Scavelli > Assignee: Nick Scavelli > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2819) Fix locale parsing in REST API

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2819?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-2819: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/329 > Fix locale parsing in REST API > ------------------------------ > > Key: GTNPORTAL-2819 > URL: https://issues.jboss.org/browse/GTNPORTAL-2819 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Reporter: Nick Scavelli > Assignee: Nick Scavelli > > REST API should accept both "en_US" and "en-US" to specify a locale; however, it will use "en-US" to display the locale in the response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2819) Fix locale parsing in REST API

by Nick Scavelli (JIRA)

Nick Scavelli created GTNPORTAL-2819: ---------------------------------------- Summary: Fix locale parsing in REST API Key: GTNPORTAL-2819 URL: https://issues.jboss.org/browse/GTNPORTAL-2819 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: REST API Reporter: Nick Scavelli Assignee: Nick Scavelli REST API should accept both "en_US" and "en-US" to specify a locale; however, it will use "en-US" to display the locale in the response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- Michal Vanco <mvanco(a)redhat.com> made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Verified with CR01.1 and works as expected > WS ports link to individual nodes' URL instead of loadbalancer > -------------------------------------------------------------- > > Key: GTNWSRP-340 > URL: https://issues.jboss.org/browse/GTNWSRP-340 > Project: GateIn WSRP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Consumer, Producer > Affects Versions: 2.2.0.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.1.Final > > > This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- Michal Vanco <mvanco(a)redhat.com> changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ON_QA to VERIFIED > WS ports link to individual nodes' URL instead of loadbalancer > -------------------------------------------------------------- > > Key: GTNWSRP-340 > URL: https://issues.jboss.org/browse/GTNWSRP-340 > Project: GateIn WSRP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Consumer, Producer > Affects Versions: 2.2.0.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.1.Final > > > This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2560) Validation of new user - first/last name

by Vlastislav Ramik (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2560?page=com.atlassian.jira.pl... ] Vlastislav Ramik reopened GTNPORTAL-2560: ----------------------------------------- Hi, I've just tried the scenario on gatein-master on tomcat7 and it fails. Jboss AS 7 works fine. > Validation of new user - first/last name > ---------------------------------------- > > Key: GTNPORTAL-2560 > URL: https://issues.jboss.org/browse/GTNPORTAL-2560 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: GateIn master - 3.4.0/ AS7.1.2 > Reporter: Michal Vanco > Assignee: Viliam Rockai > Labels: EPP6.0-Test-Dev > Fix For: 3.5.0.Beta02 > > > There is a change at validation of users's first/last name. > It says: "Only letters or spaces are allowed for the field "First Name"", but there is a problem with names including "-", "'" etc. (Jean-Claude) > This shouldn't be too strict. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues February 2013