September 2009 - gatein-issues - Jboss List Archives

[JBoss JIRA] Updated: (GTNPORTAL-5) Portlet import NPE

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-5?page=com.atlassian.jira.pl... ] Thomas Heute updated GTNPORTAL-5: --------------------------------- Fix Version/s: 3.0.0-Beta02 Affects Version/s: 3.0.0-Beta01 > Portlet import NPE > ------------------ > > Key: GTNPORTAL-5 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-5 > Project: GateIn Portal > Issue Type: Bug > Affects Versions: 3.0.0-Beta01 > Reporter: Matt Wringe > Fix For: 3.0.0-Beta02 > > > When trying to import a portlet that doesn't have a keyword defined in its portlet.xml a NPE will result preventing the portlet from being used. -- 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-11) Navigation bar not available from Application Registry page

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-11?page=com.atlassian.jira.p... ] Thomas Heute updated GTNPORTAL-11: ---------------------------------- Affects Version/s: 3.0.0-Beta01 > Navigation bar not available from Application Registry page > ----------------------------------------------------------- > > Key: GTNPORTAL-11 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-11 > Project: GateIn Portal > Issue Type: Bug > Components: User Interface > Affects Versions: 3.0.0-Beta01 > Environment: Chromium 4.0.203.0, Linux > Reporter: Matt Wringe > > When accessing the Application Registry page, the navigation bar/portlet is not displayed. -- 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-7) Tomcat version and wci setup

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-7?page=com.atlassian.jira.pl... ] Thomas Heute updated GTNPORTAL-7: --------------------------------- Component/s: WCI integration Affects Version/s: 3.0.0-Beta01 > Tomcat version and wci setup > ---------------------------- > > Key: GTNPORTAL-7 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-7 > Project: GateIn Portal > Issue Type: Bug > Components: WCI integration > Affects Versions: 3.0.0-Beta01 > Reporter: Matt Wringe > > The Tomcat version of GateIN uses the wci generic setup for integration. This means that portlets will need for their web.xml modified in order to have the portlets deployed properly. > We could use the integration war from the JBoss version of Gatein (with a few modifications) to switch the wci setup from generic to container specific. This would allow for the web.xml file of the portlets to remain unchanged. -- 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-6) Portlet Container exception handling

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-6?page=com.atlassian.jira.pl... ] Thomas Heute updated GTNPORTAL-6: --------------------------------- Component/s: PC integration Affects Version/s: 3.0.0-Beta01 > 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] Updated: (GTNPORTAL-13) Resource Handling Issues

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-13?page=com.atlassian.jira.p... ] Thomas Heute updated GTNPORTAL-13: ---------------------------------- Affects Version/s: 3.0.0-Beta01 > Resource Handling Issues > ------------------------ > > Key: GTNPORTAL-13 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-13 > Project: GateIn Portal > Issue Type: Bug > Affects Versions: 3.0.0-Beta01 > Reporter: Matt Wringe > > There are a few issues with resource handling which is causing problems with things like the remote portlet and the portlet bridge. > Portlet resource handling needs to be tested more and fixed. -- 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-9) Login page isn't fully internationalized

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-9?page=com.atlassian.jira.pl... ] Thomas Heute updated GTNPORTAL-9: --------------------------------- Component/s: Internationalization and Localization > Login page isn't fully internationalized > ---------------------------------------- > > Key: GTNPORTAL-9 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-9 > Project: GateIn Portal > Issue Type: Bug > Components: Internationalization and Localization > Affects Versions: 3.0.0-Beta01 > Reporter: Thomas Heute > > web/portal/src/main/webapp/login/jsp/login.jsp has some hardcoded text -- 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-1) Add option to 'manage portal/add portal' in menu bar

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-1?page=com.atlassian.jira.pl... ] Thomas Heute updated GTNPORTAL-1: --------------------------------- Affects Version/s: 3.0.0-Beta01 > Add option to 'manage portal/add portal' in menu bar > ---------------------------------------------------- > > Key: GTNPORTAL-1 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1 > Project: GateIn Portal > Issue Type: Feature Request > Components: User Interface > Affects Versions: 3.0.0-Beta01 > Environment: GateIn-3.0.0-Beta01 > Reporter: Joao Paulo Viragine > > Having to click in 'Site' option of menu bar to take 'add new portal' option isn't so intuitive. -- 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: -------------------------------------- Yes, and I have mentioned that in the steps to reproduce, that is not the problem. The problem is that when you add the new portlets, you need to close and reopen the browser before they are added to the list of portlets to be added to a page. They already appear in the application registry page, just not in the "Edit Inline Composer" until the browser is restarted. > 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 Rafael Liu (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-6?page=com.atlassian.jira.pl... ] Rafael Liu commented on GTNPORTAL-6: ------------------------------------ Another exception to handle is when Portlet Container doesn't find a used portlet: Caused by: org.gatein.pc.api.NoSuchPortletException: No such portlet /MY_PORTLET at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:82) at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker._getPortlet(ProducerPortletInvoker.java:183) at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker.getPortlet(ProducerPortletInvoker.java:123) Page blanks and I don't even get a chance to remove the problematic portlet.. > Portlet Container exception handling > ------------------------------------ > > Key: GTNPORTAL-6 > URL: https://jira.jboss.org/jira/browse/GTNPORTAL-6 > Project: GateIn Portal > Issue Type: Bug > 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] Commented: (GTNPORTAL-12) recently deployed portlets not appearing in list of available portlets

by Rafael Liu (JIRA)

[ https://jira.jboss.org/jira/browse/GTNPORTAL-12?page=com.atlassian.jira.p... ] Rafael Liu commented on GTNPORTAL-12: ------------------------------------- You have to click "Auto import" for GateIn to scan for new portlets. > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2009