January 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPC-100) PortalContext.VERSION needs to be updated for each release

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-100: ---------------------------------- Summary: PortalContext.VERSION needs to be updated for each release Key: GTNPC-100 URL: https://issues.jboss.org/browse/GTNPC-100 Project: GateIn Portlet Container Issue Type: Task Affects Versions: 2.4.1.CR01, 2.4.0.Final Reporter: Chris Laprun Fix For: 2.4.1.CR02 It's currently still stuck at version 2.2.0-GA. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-99) Artifacts that used to be published are not anymore

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-99: --------------------------------- Summary: Artifacts that used to be published are not anymore Key: GTNPC-99 URL: https://issues.jboss.org/browse/GTNPC-99 Project: GateIn Portlet Container Issue Type: Feature Request Affects Versions: 2.4.1.CR01, 2.4.0.Final Reporter: Chris Laprun Priority: Minor Fix For: 2.4.1.CR02 In particular, WSRP relies on the org.gatein.pc/pc-samples/war/google-portlet artifact that used to be published up to version 2.3.2-GA but is not anymore. -- 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

12 years, 9 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] Hi, I just verified clustering scenario with <wsdl-host>jbossws.undefined.host</wsdl-host> on producer nodes and it worked perfect. Now it's possible to refresh consumer or directly display remote portlet after failover - these two main scenarios were expected! WSDL was properly rewritten and it included loadbalancer host instead of specific producer node! I also tried <wsdl-host>jbossws.undefined.host</wsdl-host> at standalone.xml for singlenode testing of wsrp and it worked as expeceted -> it seems to be safe to use above wsdl-host as default. This have to be done for CR01 build (who is gonna do it? Honza/Chris?). > 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

12 years, 9 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: ------------------------------------------------- claprun(a)redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] I think it's safe to use in non-clustered environment as well, yes. However, this should be confirmed by QA. > 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

12 years, 9 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: ------------------------------------------------- claprun(a)redhat.com changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ASSIGNED to MODIFIED > 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

12 years, 9 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: ------------------------------------------------- theute(a)redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Is it safe to put as default, or does it work only with a loadbalancer ? > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation

by Thu Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ] Thu Nguyen updated GTNPORTAL-2807: ---------------------------------- Description: Here are steps to reproduce 1. Signin as root 2. Go to Application Registry 3. Create a page by winzard, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Actual result: Don't show DashBoard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. 13. click on "Edit page" 14. Actual result: Don't show Dashboard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. was: Here are steps to reproduce 1. Signin as root 2. Go to Application Registry 3. Create a page by winzard, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Actual result: Don't show DashBoard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. 13. click on "Edit page" 14. Don't show Dashboard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. > The page is not saved when edit node's page in group navigation > --------------------------------------------------------------- > > Key: GTNPORTAL-2807 > URL: https://issues.jboss.org/browse/GTNPORTAL-2807 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Environment: jboss-jpp-6.0.0.ER05 > GateIn 3.5 > FF 16 > Reporter: Thu Nguyen > Priority: Minor > > Here are steps to reproduce > 1. Signin as root > 2. Go to Application Registry > 3. Create a page by winzard, called "Test" > 4. Drag and drop "Application registry" portlet to this page > 5. Save and close > 6. Go to Group site, click on "edit navigation" of Administrators group > 7. Click on Edit Node'page of "Test" node > 8. Drag and drop "Dashboard" portlet to this page > 9. Save and close > 10.Click on Save on "Navigation management" popup > 11. Open the page "Test" > 12. Actual result: Don't show DashBoard portlet => NOK > Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. > 13. click on "Edit page" > 14. Actual result: Don't show Dashboard portlet => NOK > Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation

by Thu Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ] Thu Nguyen updated GTNPORTAL-2807: ---------------------------------- Description: Here are steps to reproduce 1. Signin as root 2. Go to Application Registry 3. Create a page by winzard, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Don't show DashBoard portlet => NOK 13. click on "Edit page" 14. Don't show Dashboard portlet => NOK Expect: Show Dashbord portlet => It must be saved when edit Node's page on Navigation group. was: 1. Signin as root 2. Go to Application Registry 3. Create a page, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Don't show DashBoard portlet => NOK 13. click on "Edit page" 14. Don't show Dashboard portlet => NOK Expect: Show Dashbord portlet => It must be saved when edit Node's page on Navigation group. > The page is not saved when edit node's page in group navigation > --------------------------------------------------------------- > > Key: GTNPORTAL-2807 > URL: https://issues.jboss.org/browse/GTNPORTAL-2807 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Environment: jboss-jpp-6.0.0.ER05 > GateIn 3.5 > FF 16 > Reporter: Thu Nguyen > Priority: Minor > > Here are steps to reproduce > 1. Signin as root > 2. Go to Application Registry > 3. Create a page by winzard, called "Test" > 4. Drag and drop "Application registry" portlet to this page > 5. Save and close > 6. Go to Group site, click on "edit navigation" of Administrators group > 7. Click on Edit Node'page of "Test" node > 8. Drag and drop "Dashboard" portlet to this page > 9. Save and close > 10.Click on Save on "Navigation management" popup > 11. Open the page "Test" > 12. Don't show DashBoard portlet => NOK > 13. click on "Edit page" > 14. Don't show Dashboard portlet => NOK > Expect: Show Dashbord portlet => It must be saved when edit Node's page on Navigation group. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation

by Thu Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ] Thu Nguyen updated GTNPORTAL-2807: ---------------------------------- Description: Here are steps to reproduce 1. Signin as root 2. Go to Application Registry 3. Create a page by winzard, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Actual result: Don't show DashBoard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. 13. click on "Edit page" 14. Don't show Dashboard portlet => NOK Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. was: Here are steps to reproduce 1. Signin as root 2. Go to Application Registry 3. Create a page by winzard, called "Test" 4. Drag and drop "Application registry" portlet to this page 5. Save and close 6. Go to Group site, click on "edit navigation" of Administrators group 7. Click on Edit Node'page of "Test" node 8. Drag and drop "Dashboard" portlet to this page 9. Save and close 10.Click on Save on "Navigation management" popup 11. Open the page "Test" 12. Don't show DashBoard portlet => NOK 13. click on "Edit page" 14. Don't show Dashboard portlet => NOK Expect: Show Dashbord portlet => It must be saved when edit Node's page on Navigation group. > The page is not saved when edit node's page in group navigation > --------------------------------------------------------------- > > Key: GTNPORTAL-2807 > URL: https://issues.jboss.org/browse/GTNPORTAL-2807 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Environment: jboss-jpp-6.0.0.ER05 > GateIn 3.5 > FF 16 > Reporter: Thu Nguyen > Priority: Minor > > Here are steps to reproduce > 1. Signin as root > 2. Go to Application Registry > 3. Create a page by winzard, called "Test" > 4. Drag and drop "Application registry" portlet to this page > 5. Save and close > 6. Go to Group site, click on "edit navigation" of Administrators group > 7. Click on Edit Node'page of "Test" node > 8. Drag and drop "Dashboard" portlet to this page > 9. Save and close > 10.Click on Save on "Navigation management" popup > 11. Open the page "Test" > 12. Actual result: Don't show DashBoard portlet => NOK > Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. > 13. click on "Edit page" > 14. Don't show Dashboard portlet => NOK > Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation

by Thu Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ] Thu Nguyen updated GTNPORTAL-2807: ---------------------------------- Summary: The page is not saved when edit node's page in group navigation (was: Cannot save when edit node's page in group navigation) > The page is not saved when edit node's page in group navigation > --------------------------------------------------------------- > > Key: GTNPORTAL-2807 > URL: https://issues.jboss.org/browse/GTNPORTAL-2807 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Environment: jboss-jpp-6.0.0.ER05 > GateIn 3.5 > FF 16 > Reporter: Thu Nguyen > Priority: Minor > > 1. Signin as root > 2. Go to Application Registry > 3. Create a page, called "Test" > 4. Drag and drop "Application registry" portlet to this page > 5. Save and close > 6. Go to Group site, click on "edit navigation" of Administrators group > 7. Click on Edit Node'page of "Test" node > 8. Drag and drop "Dashboard" portlet to this page > 9. Save and close > 10.Click on Save on "Navigation management" popup > 11. Open the page "Test" > 12. Don't show DashBoard portlet => NOK > 13. click on "Edit page" > 14. Don't show Dashboard portlet => NOK > Expect: Show Dashbord portlet => It must be saved when edit Node's page on Navigation group. -- 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

12 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues January 2013