April 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNWSRP-221) RequestProcessor locale matching logic is incorrect

by Chris Laprun (JIRA)

RequestProcessor locale matching logic is incorrect --------------------------------------------------- Key: GTNWSRP-221 URL: https://issues.jboss.org/browse/GTNWSRP-221 Project: GateIn WSRP Issue Type: Bug Components: Producer Affects Versions: 2.1.0-Beta01, 2.0.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.0.1-GA, 2.1.0-Beta02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1864) Fix org.exoplatform.portal.config.TestCache to make sure it doesn't affect other tests

by Vu Viet Phuong (JIRA)

Fix org.exoplatform.portal.config.TestCache to make sure it doesn't affect other tests -------------------------------------------------------------------------------------- Key: GTNPORTAL-1864 URL: https://issues.jboss.org/browse/GTNPORTAL-1864 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Vu Viet Phuong -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1861) Upgrade PicketLink IDM to 1.1.8.GA

by Boleslaw Dawidowicz (JIRA)

Upgrade PicketLink IDM to 1.1.8.GA ---------------------------------- Key: GTNPORTAL-1861 URL: https://issues.jboss.org/browse/GTNPORTAL-1861 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Upgrade PicketLink IDM to 1.1.8.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1856) Fix for some mis-translations in webui_ja.prpoperties

by Toshiya Kobayashi (JIRA)

Fix for some mis-translations in webui_ja.prpoperties ----------------------------------------------------- Key: GTNPORTAL-1856 URL: https://issues.jboss.org/browse/GTNPORTAL-1856 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Internationalization and Localization Affects Versions: 3.1.0-GA Reporter: Toshiya Kobayashi Priority: Minor Fix for some mis-translations in webui_ja.prpoperties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1858) XSS issue in dashboard new page creation

by Thomas Heute (JIRA)

XSS issue in dashboard new page creation ---------------------------------------- Key: GTNPORTAL-1858 URL: https://issues.jboss.org/browse/GTNPORTAL-1858 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Heute Assignee: Thomas Heute Fix For: 3.2.0-GA this issue has two subdivisions: 1. basic page add login click on dashboard, to the "on page editor" click on the "plus" button to add new page and set "<script>alert('hi');</script>" as its name the javascript is now invoked 2. advanced page add login, go to dashboard click dashboard editor -> add new page put "whatever" to node name and "<script>alert('hi');</script>" as node description click next, next the javascript is invoked -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1857) Incorrect versions of wsrp dependencies in extension-ear-as5 and extension-ear-as6

by Michal Vanco (JIRA)

Incorrect versions of wsrp dependencies in extension-ear-as5 and extension-ear-as6 ---------------------------------------------------------------------------------- Key: GTNPORTAL-1857 URL: https://issues.jboss.org/browse/GTNPORTAL-1857 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WSRP integration Environment: GateIn trunk (04/12) WSRP 2.1.0-Beta01 Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 3.2.0-GA There is a problem with application.xml files at wsrp-integration/extension-ear-as5/src/main/application/META-INF/application.xml wsrp-integration/extension-ear-as6/src/main/application/META-INF/application.xml I think these files can be removed because you have defined dependencies and content of ear archive at pom.xml using maven-ear-plugin (and application.xml is generated automatically based on this definiton) If removing is not a solution then version must be changed because for example now gatein is dependent on wsrp 2.1.0-Beta01, but application.xml files contain <web-uri>wsrp-admin-gui-2.1.0-Alpha02.war</web-uri> and wsrp-producer-2.1.0-Alpha02.war Btw. at default wsrp-integration/extension-ear module the application.xml isn't present and it's properly generated from maven-ear-plugin definition. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GTNPC-59) Provide a portlet request property that provides the name of the current portlet being filtered

by Julien Viet (JIRA)

Provide a portlet request property that provides the name of the current portlet being filtered ----------------------------------------------------------------------------------------------- Key: GTNPC-59 URL: https://issues.jboss.org/browse/GTNPC-59 Project: GateIn Portlet Container Issue Type: Enhancement Reporter: Julien Viet Assignee: Julien Viet Fix For: 2.3.0-GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (GTNPC-61) FederatingPortletInvokerService.getFederatedPortletInvokerFor makes wrong assumptions about PortletContext format

by Chris Laprun (JIRA)

FederatingPortletInvokerService.getFederatedPortletInvokerFor makes wrong assumptions about PortletContext format ----------------------------------------------------------------------------------------------------------------- Key: GTNPC-61 URL: https://issues.jboss.org/browse/GTNPC-61 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.3.0-Beta01, 2.2.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.3.0-Beta02 This results in local compound portlet contexts being interpreted as being federated when it's not the case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (GTNPORTAL-1855) The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)

by Thomas Heute (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1855?page=com.atlassian.jira.pl... ] Thomas Heute commented on GTNPORTAL-1855: ----------------------------------------- That Jira is for sample portal (and ecmdemo, which should be a Jira @ eXo WCM project), GTNPORTAL-1339 was for the default portal. > The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal) > ----------------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-1855 > URL: https://issues.jboss.org/browse/GTNPORTAL-1855 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common integration > Reporter: Martin Weiler > Fix For: 3.2.0-GA > > > The changes applied to 02portal.war/WEB-INF/web.xml as a result of the fix for JBEPP-486 also need to be applied to the web.xml files contained in the eppsp demo portal and sample portal. The filter mapping element for the GenericFilter has to be the last one in the list: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (GTNPORTAL-1855) The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1855?page=com.atlassian.jira.pl... ] Trong Tran commented on GTNPORTAL-1855: --------------------------------------- isn't this fixed in GTNPORTAL-1339 ? > The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal) > ----------------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-1855 > URL: https://issues.jboss.org/browse/GTNPORTAL-1855 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common integration > Reporter: Martin Weiler > Fix For: 3.2.0-GA > > > The changes applied to 02portal.war/WEB-INF/web.xml as a result of the fix for JBEPP-486 also need to be applied to the web.xml files contained in the eppsp demo portal and sample portal. The filter mapping element for the GenericFilter has to be the last one in the list: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2011