April 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2892) Update to the footer portlet to use 2013 instead of 2012 for the copyright

by Matt Wringe (JIRA)

Matt Wringe created GTNPORTAL-2892: -------------------------------------- Summary: Update to the footer portlet to use 2013 instead of 2012 for the copyright Key: GTNPORTAL-2892 URL: https://issues.jboss.org/browse/GTNPORTAL-2892 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe The footer portlet's copyright date should be updated to 2013 from 2012. -- 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] (GTNPC-13) Several classes in org.gatein.pc.portlet.impl.spi should be renamed as they're not abstract

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-13?page=com.atlassian.jira.plugin.s... ] Julien Viet resolved GTNPC-13. ------------------------------ Resolution: Rejected Non issue. > Several classes in org.gatein.pc.portlet.impl.spi should be renamed as they're not abstract > ------------------------------------------------------------------------------------------- > > Key: GTNPC-13 > URL: https://issues.jboss.org/browse/GTNPC-13 > Project: GateIn Portlet Container > Issue Type: Bug > Affects Versions: 2.1.0-Beta02 > Reporter: Chris Laprun > Priority: Optional > Fix For: 2.4.1.CR03 > > > Pretty much all the *Context classes in that package should be renamed as they're not abstract. -- 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] (GTNPC-9) PortletRequestDispatcher does not execute 'forward' method during resource request.

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-9?page=com.atlassian.jira.plugin.sy... ] Julien Viet resolved GTNPC-9. ----------------------------- Resolution: Cannot Reproduce Bug Never got a way to reproduce it properly. > PortletRequestDispatcher does not execute 'forward' method during resource request. > ----------------------------------------------------------------------------------- > > Key: GTNPC-9 > URL: https://issues.jboss.org/browse/GTNPC-9 > Project: GateIn Portlet Container > Issue Type: Bug > Affects Versions: 2.1.0-Beta01, 2.1.0-Beta02 > Reporter: Thomas Heute > Assignee: Julien Viet > Fix For: 2.4.1.CR03 > > > See linked issue -- 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] (GTNPC-82) Potential concurrency issues in FederatingPortletInvokerService and ContainerPortletInvoker

by Nicolas Filotto (JIRA)

[ https://issues.jboss.org/browse/GTNPC-82?page=com.atlassian.jira.plugin.s... ] Nicolas Filotto updated GTNPC-82: --------------------------------- Summary: Potential concurrency issues in FederatingPortletInvokerService and ContainerPortletInvoker (was: Potential concurency issues in FederatingPortletInvokerService and ContainerPortletInvoker) > Potential concurrency issues in FederatingPortletInvokerService and ContainerPortletInvoker > ------------------------------------------------------------------------------------------- > > Key: GTNPC-82 > URL: https://issues.jboss.org/browse/GTNPC-82 > Project: GateIn Portlet Container > Issue Type: Quality Risk > Affects Versions: 2.3.0-GA > Reporter: Nicolas Filotto > Assignee: Julien Viet > Fix For: 2.4.1.CR03 > > Attachments: GTNPC-82.patch > > > While debugging to undestand why the PC could not find my portlets, I found the next potential concurrency issues : > # In FederatingPortletInvokerService.getOrResolveFederatedInvoker() the invokerCache is directly modified instead of being recreated from scratch and reassigned which could cause HashMap corruptions under heavy load > # In ContainerPortletInvoker: The methods addPortletContainer and removePortletContainer should be synchronized to prevent any modification loss in case of concurrent modifications. Moreover the variable portlets should be volatile for the same reason > This must be seen as a feedback based on my experience, you are free to resolve it as won't fix if you don't find it relevant. -- 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] (GTNPC-82) Potential concurency issues in FederatingPortletInvokerService and ContainerPortletInvoker

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-82?page=com.atlassian.jira.plugin.s... ] Julien Viet resolved GTNPC-82. ------------------------------ Assignee: Julien Viet Fix Version/s: 2.4.1.CR03 Resolution: Done Applied the patch from Nicolas. > Potential concurency issues in FederatingPortletInvokerService and ContainerPortletInvoker > ------------------------------------------------------------------------------------------ > > Key: GTNPC-82 > URL: https://issues.jboss.org/browse/GTNPC-82 > Project: GateIn Portlet Container > Issue Type: Quality Risk > Affects Versions: 2.3.0-GA > Reporter: Nicolas Filotto > Assignee: Julien Viet > Fix For: 2.4.1.CR03 > > Attachments: GTNPC-82.patch > > > While debugging to undestand why the PC could not find my portlets, I found the next potential concurrency issues : > # In FederatingPortletInvokerService.getOrResolveFederatedInvoker() the invokerCache is directly modified instead of being recreated from scratch and reassigned which could cause HashMap corruptions under heavy load > # In ContainerPortletInvoker: The methods addPortletContainer and removePortletContainer should be synchronized to prevent any modification loss in case of concurrent modifications. Moreover the variable portlets should be volatile for the same reason > This must be seen as a feedback based on my experience, you are free to resolve it as won't fix if you don't find it relevant. -- 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-354) gatein-producer-config.xml uses an outdated namespace

by Chris Laprun (JIRA)

Chris Laprun created GTNWSRP-354: ------------------------------------ Summary: gatein-producer-config.xml uses an outdated namespace Key: GTNWSRP-354 URL: https://issues.jboss.org/browse/GTNWSRP-354 Project: GateIn WSRP Issue Type: Bug Security Level: Public (Everyone can see) Components: Producer Affects Versions: 2.2.3.Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.2.4.Final This leads to WSRP not deploying properly on EAP 6.1 Alpha -- 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] (GTNPC-4) Fix admin portet in simple-portal

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-4?page=com.atlassian.jira.plugin.sy... ] Julien Viet resolved GTNPC-4. ----------------------------- Resolution: Out of Date > Fix admin portet in simple-portal > --------------------------------- > > Key: GTNPC-4 > URL: https://issues.jboss.org/browse/GTNPC-4 > Project: GateIn Portlet Container > Issue Type: Bug > Components: Simple Portal > Reporter: Thomas Heute > -- 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] (GTNPC-18) Portlet content not shown when using RenderResponse.getPortletOutputStream()

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-18?page=com.atlassian.jira.plugin.s... ] Julien Viet resolved GTNPC-18. ------------------------------ Resolution: Out of Date > Portlet content not shown when using RenderResponse.getPortletOutputStream() > ---------------------------------------------------------------------------- > > Key: GTNPC-18 > URL: https://issues.jboss.org/browse/GTNPC-18 > Project: GateIn Portlet Container > Issue Type: Bug > Components: Simple Portal > Affects Versions: 2.1.0-CR02 > Reporter: Henri Sara > > When using RenderRequest.getPortletOutputStream() instead of RenderResponse.getWriter() to write the portlet contents, only a memory reference (like "[B@1234abcd") is shown as the portlet content. > This is caused by the use of byte[].toString() in org.gatein.pc.portal.jsp.taglib.PortletMarkupTag.doTag(), line "frag = fragment.getBytes().toString();". -- 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] (GTNPC-84) Link not working http://www.jboss.org/gatein/portletcontainer/

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-84?page=com.atlassian.jira.plugin.s... ] Julien Viet resolved GTNPC-84. ------------------------------ Resolution: Won't Fix Works for me, please try to avoid to use JIRA for non issues like this. > Link not working http://www.jboss.org/gatein/portletcontainer/ > -------------------------------------------------------------- > > Key: GTNPC-84 > URL: https://issues.jboss.org/browse/GTNPC-84 > Project: GateIn Portlet Container > Issue Type: Bug > Reporter: Ravindra Maurya > Priority: Blocker > > http://www.jboss.org/gatein/portletcontainer/ > Not working -- 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] (GTNPC-80) ContentResponse doesn't properly encode the content from a byte array

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-80?page=com.atlassian.jira.plugin.s... ] Julien Viet resolved GTNPC-80. ------------------------------ Assignee: Julien Viet Fix Version/s: 2.4.1.CR03 Resolution: Done This was fixed during the dev of the embedded PC, I was not aware of existence of this issue. > ContentResponse doesn't properly encode the content from a byte array > --------------------------------------------------------------------- > > Key: GTNPC-80 > URL: https://issues.jboss.org/browse/GTNPC-80 > Project: GateIn Portlet Container > Issue Type: Bug > Reporter: Matt Wringe > Assignee: Julien Viet > Fix For: 2.4.1.CR03 > > > ContentResponse.getContent uses "new String(bytes)" but should use 'new String(bytes, charset)' where the charset is retrieved from the contentType. -- 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 April 2013