May 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-363) WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-363?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated GTNWSRP-363: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=961242 > WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster > ----------------------------------------------------------------------------------------------- > > Key: GTNWSRP-363 > URL: https://issues.jboss.org/browse/GTNWSRP-363 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Producer, Specification Support > Environment: - JBoss EPP > - 5 > - 6 > Reporter: Adam Kovari > Assignee: Chris Laprun > Priority: Minor > > This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd. > The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue. > It should work like this: > {code} > <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000"> >  > <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <registration-data/> > </wsrp-producer> > {code} > So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-364) RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-364?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-364: ------------------------------------------------- Adam Kovari <akovari(a)redhat.com> made a comment on [bug 961242|https://bugzilla.redhat.com/show_bug.cgi?id=961242] Description of problem: This is an RFE for https://issues.jboss.org/browse/GTNWSRP-364 > RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster > ----------------------------------------------------------------------------------------------------- > > Key: GTNWSRP-364 > URL: https://issues.jboss.org/browse/GTNWSRP-364 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Producer, Specification Support > Environment: - JBoss EPP > - 5 > - 6 > Reporter: Adam Kovari > Assignee: Chris Laprun > Priority: Minor > > This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd. > The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue. > It should work like this: > {code} > <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000"> >  > <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <registration-data/> > </wsrp-producer> > {code} > So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-364) RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-364?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated GTNWSRP-364: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=961242 > RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster > ----------------------------------------------------------------------------------------------------- > > Key: GTNWSRP-364 > URL: https://issues.jboss.org/browse/GTNWSRP-364 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Producer, Specification Support > Environment: - JBoss EPP > - 5 > - 6 > Reporter: Adam Kovari > Assignee: Chris Laprun > Priority: Minor > > This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd. > The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue. > It should work like this: > {code} > <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000"> >  > <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> > <registration-data/> > </wsrp-producer> > {code} > So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-364) RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

by Adam Kovari (JIRA)

Adam Kovari created GTNWSRP-364: ----------------------------------- Summary: RFE - WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster Key: GTNWSRP-364 URL: https://issues.jboss.org/browse/GTNWSRP-364 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Producer, Specification Support Environment: - JBoss EPP - 5 - 6 Reporter: Adam Kovari Assignee: Chris Laprun Priority: Minor This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd. The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue. It should work like this: {code} <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000">  <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> <registration-data/> </wsrp-producer> {code} So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-363) WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

by Adam Kovari (JIRA)

Adam Kovari created GTNWSRP-363: ----------------------------------- Summary: WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster Key: GTNWSRP-363 URL: https://issues.jboss.org/browse/GTNWSRP-363 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Producer, Specification Support Environment: - JBoss EPP - 5 - 6 Reporter: Adam Kovari Assignee: Chris Laprun Priority: Minor This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd. The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue. It should work like this: {code} <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000">  <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> <registration-data/> </wsrp-producer> {code} So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2983) Provision a text equivalent for every non-text element shall be provided

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2983?page=com.atlassian.jira.pl... ] Lucas Ponce commented on GTNPORTAL-2983: ---------------------------------------- Done for UIHomePagePortlet.gtmpl > Provision a text equivalent for every non-text element shall be provided > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2983 > URL: https://issues.jboss.org/browse/GTNPORTAL-2983 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2983) Provision a text equivalent for every non-text element shall be provided

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2983?page=com.atlassian.jira.pl... ] Lucas Ponce commented on GTNPORTAL-2983: ---------------------------------------- UILogoPortlet.gtmpl > Provision a text equivalent for every non-text element shall be provided > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2983 > URL: https://issues.jboss.org/browse/GTNPORTAL-2983 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2983) Provision a text equivalent for every non-text element shall be provided

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2983?page=com.atlassian.jira.pl... ] Lucas Ponce commented on GTNPORTAL-2983: ---------------------------------------- Done for UIRepeater.gtmpl > Provision a text equivalent for every non-text element shall be provided > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2983 > URL: https://issues.jboss.org/browse/GTNPORTAL-2983 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2983) Provision a text equivalent for every non-text element shall be provided

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2983?page=com.atlassian.jira.pl... ] Lucas Ponce commented on GTNPORTAL-2983: ---------------------------------------- Done for UIGrid.gtmpl > Provision a text equivalent for every non-text element shall be provided > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2983 > URL: https://issues.jboss.org/browse/GTNPORTAL-2983 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2988) Translation of navigation title doesn't work for language with country variant

by H. Trang Vu (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2988?page=com.atlassian.jira.pl... ] H. Trang Vu updated GTNPORTAL-2988: ----------------------------------- Attachment: GateIn-3.6.0-beta2-20130507-GroupNavigation-pt-BR-NOK.png > Translation of navigation title doesn't work for language with country variant > ------------------------------------------------------------------------------ > > Key: GTNPORTAL-2988 > URL: https://issues.jboss.org/browse/GTNPORTAL-2988 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.4.Final, 3.6.0.Beta01 > Reporter: H. Trang Vu > Attachments: GateIn-3.6.0-beta2-20130507-GroupNavigation-pt-BR-NOK.png > > > When language code contains country variant such as pt_BR, zh_CN, zh_TW, the translation of navigation node using key defined in resource bundle doesn't take effect. > This problem doesn't exist either in extended label mode or for language code without country variant. -- 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, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues May 2013