September 2009 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPC-9) PortletRequestDispatcher does not execute 'forward' method during resource request.

by Thomas Heute (JIRA)

PortletRequestDispatcher does not execute 'forward' method during resource request. ----------------------------------------------------------------------------------- Key: GTNPC-9 URL: https://jira.jboss.org/jira/browse/GTNPC-9 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 1.2.0-Beta01 Reporter: Thomas Heute Assignee: Julien Viet See linked issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
12
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-17) Events seems to be triggered twice

by Thomas Heute (JIRA)

Events seems to be triggered twice ---------------------------------- Key: GTNPORTAL-17 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-17 Project: GateIn Portal Issue Type: Bug Components: PC integration Reporter: Thomas Heute Assignee: Matt Wringe Fix For: 3.0.0-Beta02 I've tried the Cart and Catalog portlets used in JBoss Portal 2.7 and realized that when you add an element to the cart it is added twice -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-18) Unable to resolve portlet tlds on JBoss AS

by Matt Wringe (JIRA)

Unable to resolve portlet tlds on JBoss AS ------------------------------------------ Key: GTNPORTAL-18 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-18 Project: GateIn Portal Issue Type: Bug Reporter: Matt Wringe When using the JBoss AS version of Gatein, portlets are unable to resolve the portlet tlds. This is caused by the server.jboss.patch module not correctly specify the file to fix (its trying to patch deploy/jboss-web.deploy instead of deployers/jboss-web.deployer) and the tld jar is specifying the old exo pc jar instead of the gatein one (it should be set to ../../deploy/exoplatform.ear/pc-portlet-2.1.0-SNAPSHOT.jar). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Commented: (GTNPORTAL-12) recently deployed portlets not appearing in list of available portlets

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-12?page=com.atlassian.jira.p... ] Thomas Heute commented on GTNPORTAL-12: --------------------------------------- I've just experienced it with the create new page wizard. Had to kill the session > recently deployed portlets not appearing in list of available portlets > ---------------------------------------------------------------------- > > Key: GTNPORTAL-12 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-12 > Project: GateIn Portal > Issue Type: Bug > Components: User Interface > Reporter: Matt Wringe > > Sometimes when editing a page or adding a new page, recently added portlets are not available on the list of available portlets to be deployed. This is usually resolved by closing and then reopening the browser. > Steps to reproduce > 1) add a portlet to the deploy directory > 2) register the portlet through the application registry (using autoimport if that matters) > 3) edit a page > 4) the new portlets added through the application registry do not appear in the list of portlets available for the page > Expected Results > all available portlets available on the page > Workaround > close browser, reopen browser and start to edit the page again. Now all the expected portlets will be available. > Environment: Linux, Chromium browser (4.0.203.0). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (GTNPORTAL-6) Portlet Container exception handling

by Matt Wringe (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-6?page=com.atlassian.jira.pl... ] Matt Wringe commented on GTNPORTAL-6: ------------------------------------- A fix has been committed into svn for the issue of trying to load a page that has contains a portlet that has been removed. > Portlet Container exception handling > ------------------------------------ > > Key: GTNPORTAL-6 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-6 > Project: GateIn Portal > Issue Type: Bug > Components: PC integration > Affects Versions: 3.0.0-Beta01 > Reporter: Matt Wringe > > When the portal receives an error from the portlet container, it doesn't handle this exception properly. > The portal should catch the error, log its results, and have the offending portlet's contents changed to an error message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (GTNPORTAL-10) Portal doesn't load in Firefox

by Matt Wringe (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-10?page=com.atlassian.jira.p... ] Matt Wringe closed GTNPORTAL-10. -------------------------------- Resolution: Done I am no longer seeing this issue after doing an update. > Portal doesn't load in Firefox > ------------------------------ > > Key: GTNPORTAL-10 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-10 > Project: GateIn Portal > Issue Type: Bug > Components: User Interface > Environment: Firefox 3.5.3, Fedora 11 > Reporter: Matt Wringe > Fix For: 3.0.0-Beta02 > > > The home page of the portal doesn't load in firefox 3.5 on linux. > When accessing localhost:8080/portal nothing gets displayed and is stuck on loading. > This used to work in the past, and if another browser is used it can access this page without issue. > Using GateIn head (eXo revision 37144). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (GTNPORTAL-12) recently deployed portlets not appearing in list of available portlets

by Matt Wringe (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-12?page=com.atlassian.jira.p... ] Matt Wringe commented on GTNPORTAL-12: -------------------------------------- This issue appears to be fixed using the latest svn head. > recently deployed portlets not appearing in list of available portlets > ---------------------------------------------------------------------- > > Key: GTNPORTAL-12 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-12 > Project: GateIn Portal > Issue Type: Bug > Components: User Interface > Reporter: Matt Wringe > > Sometimes when editing a page or adding a new page, recently added portlets are not available on the list of available portlets to be deployed. This is usually resolved by closing and then reopening the browser. > Steps to reproduce > 1) add a portlet to the deploy directory > 2) register the portlet through the application registry (using autoimport if that matters) > 3) edit a page > 4) the new portlets added through the application registry do not appear in the list of portlets available for the page > Expected Results > all available portlets available on the page > Workaround > close browser, reopen browser and start to edit the page again. Now all the expected portlets will be available. > Environment: Linux, Chromium browser (4.0.203.0). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (GTNPORTAL-10) Portal doesn't load in Firefox

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-10?page=com.atlassian.jira.p... ] Thomas Heute updated GTNPORTAL-10: ---------------------------------- Fix Version/s: 3.0.0-Beta02 > Portal doesn't load in Firefox > ------------------------------ > > Key: GTNPORTAL-10 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-10 > Project: GateIn Portal > Issue Type: Bug > Components: User Interface > Environment: Firefox 3.5.3, Fedora 11 > Reporter: Matt Wringe > Fix For: 3.0.0-Beta02 > > > The home page of the portal doesn't load in firefox 3.5 on linux. > When accessing localhost:8080/portal nothing gets displayed and is stuck on loading. > This used to work in the past, and if another browser is used it can access this page without issue. > Using GateIn head (eXo revision 37144). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNPC-8) ClassCastException

by Rafael Liu (JIRA)

ClassCastException ------------------ Key: GTNPC-8 URL: https://jira.jboss.org/jira/browse/GTNPC-8 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 1.2.0-Beta01 Reporter: Rafael Liu Priority: Minor There's a ClassCastException is the processing of an Exception. May have something to do with Exception handler not beign implemented yet, I don't know. It doesn't break anything (not that I've noticed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-16) org.gatein.pc.api.invocation.response.ErrorResponse cannot be cast to org.gatein.pc.api.invocation.response.UpdateNavigationalStateResponse

by Thomas Heute (JIRA)

org.gatein.pc.api.invocation.response.ErrorResponse cannot be cast to org.gatein.pc.api.invocation.response.UpdateNavigationalStateResponse ------------------------------------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-16 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-16 Project: GateIn Portal Issue Type: Bug Components: PC integration Affects Versions: 3.0.0-Beta01 Reporter: Thomas Heute Fix For: 3.0.0-Beta02 When the portlet container is throwing up an exception the portal integratio with PC is throwing up a ClassCastException. This can happen in several places in: org/exoplatform/portal/webui/application/UIPortletActionListener.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2009