October 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1766) Adding a new portal template requires editing of the Groovy code for the template list

by Brian Ashburn (JIRA)

Adding a new portal template requires editing of the Groovy code for the template list -------------------------------------------------------------------------------------- Key: GTNPORTAL-1766 URL: https://issues.jboss.org/browse/GTNPORTAL-1766 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.1.0-GA Environment: Fedora Core, JBoss EPP 5.1 Reporter: Brian Ashburn In order to add a new template to use when creating new Portals, there is a Groovy file(gatein.ear/02portal.war/WEB-INF/conf/uiconf/portal/webui/portal/PortalTemplateConfigOption.groovy) that displays the list of those templates for selection. The templates are hardcoded into that list, so that when a new directory is added to gatein.ear/02portal.war/WEB-INF/conf/portal/portal/template and the entry is added to gatein.ear/02portal.war/WEB-INF/conf/portal/portal-configuration.xml the template will not show up unless added to the Groovy file. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

7
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1784) Remove WebOS related checking from UIPortlet.gtmpl

by Vu Viet Phuong (JIRA)

Remove WebOS related checking from UIPortlet.gtmpl -------------------------------------------------- Key: GTNPORTAL-1784 URL: https://issues.jboss.org/browse/GTNPORTAL-1784 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong Priority: Minor WebOS related code should be moved to WebOS project -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2241) WSRP prevents server from starting and requires a force quit

by Matt Wringe (Created) (JIRA)

WSRP prevents server from starting and requires a force quit ------------------------------------------------------------ Key: GTNPORTAL-2241 URL: https://issues.jboss.org/browse/GTNPORTAL-2241 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WSRP integration Reporter: Matt Wringe Assignee: Chris Laprun Priority: Blocker If the wsrp selfv2 consumer is refreshed and activated, then the server will not start when its next rebooted. 1) start server 2) refresh selfv2 consumer 3) stop server 4) restart server, the server will hang and requires the process to be forced closed last line from log: "14:25:09,698 INFO [WSRPServiceIntegration] WSRP Producer started" If you nuke the data directory (which will cause the consumer to be deactivated on the next startup), then the server will start again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2234) Improve configuration of JBoss cache and JGroups

by Marek Posolda (Created) (JIRA)

Improve configuration of JBoss cache and JGroups ------------------------------------------------ Key: GTNPORTAL-2234 URL: https://issues.jboss.org/browse/GTNPORTAL-2234 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Identity integration, JCR integration Affects Versions: 3.2.0-M01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 3.2.0-M02 This JIRA will cover various improvements we made for configuration of JBoss cache and JGroups in EPP. Some improvements are specific to EPP (JBoss) only, and so are not covered. Related EPP issues are linked from this JIRA. Namely what we made is: - Move JBoss cache and JGroups configuration files from JAR file component/common/conf... into WAR 02portal.war/WEB-INF/conf so that they are exploded and easily editable by customers - With cluster profile enabled are all JBoss cache instances using same JGroups channel (shared transport) which is preferred way over multiplexer (See http://community.jboss.org/wiki/MigrationFromMultiplexerToSharedTransport ) - Picketlink is using two separate JBoss cache instances (apiCache and storeCache) and not sharing same - eXo JCR is using shared transport instead of multiplexer with sharing JBoss cache instances among different workspaces -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2230) Unauthorized access to Site Editor raises an unexpected JS error alert

by Matt Wringe (Created) (JIRA)

Unauthorized access to Site Editor raises an unexpected JS error alert ---------------------------------------------------------------------- Key: GTNPORTAL-2230 URL: https://issues.jboss.org/browse/GTNPORTAL-2230 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe Assignee: Matt Wringe See JBEPP-1191 Basically what is happening here - we log out of the portal but still have a tab open where we can still click on links like 'edit page'. - id's for web ui components are different between a logged in user and an unauthenticated user - we click on 'edit page' - this causes an ajax request to be created, but the component id we get is for the unauthorized user (since the user already logged out). - when the page tries to update itself it can't find this component in the current document (the page we are on contains the authenticated user document) currently when this occurs, an alert is created (which isn't all that helpful to what the actual error is) and then it get stuck in an infinite loop. A timeout then occurs which reloads the page, bringing in the unauthenticated user document. Since we are now on the unauthenticated document, the component can be retrieved and the proper request can be completed. This error is a bit more broad than just what happens when a user logs in or out (for example, lets say a webui component is removed from the portal, the same result would occur). And it might not always be wise to just automatically reload the page if it can't find the component to update (its not good if someone fills out a form and are no longer authenticated when they click submit, causing the contents of the post to be lost). The best solution here is to probably throw an error message saying it can't find the contents the ajax request is trying to access and recommend refreshing the page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

7
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2033) "Visible" and "Publication date" is effective only for Navigation, not for Page

by Toshiya Kobayashi (JIRA)

"Visible" and "Publication date" is effective only for Navigation, not for Page ------------------------------------------------------------------------------- Key: GTNPORTAL-2033 URL: https://issues.jboss.org/browse/GTNPORTAL-2033 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 3.1.0-GA Reporter: Toshiya Kobayashi - go http://localhost:8080/portal - login as root - click [Site] in menu bar - click [Edit Navigation] - right click "SiteMap" and select [Edit this Node] - uncheck "Visible" (it would be the same if you check "Visible" and set "Publication date" to the future) - click [Save] in "ADD/EDIT PAGE NODE" - click [Save] in "Namvigation Management" You will see "SiteMap" disappear in navigation bar. But you can still see the page by direct access http://localhost:8080/portal/private/classic/sitemap So "Visible" and "Publication date" is effective only for Navigation, not for Page itself. It doesn't match what the documentation says: http://docs.jboss.org/gatein/portal/3.2.0-M01/user-guide/en-US/html_single/ ============== 5.3.1. Add a new node \--- Visible This check box allow to hide (and show) the page and its node at the navigation bar, the page navigation and the site map 5.4.1.1. Adding a new Page using Page Creation Wizard \--- Visible This checkbox toggles the global visibility of this page. If checked the page or the page node appears on on the navigation bar, the page navigation and the site map. If "visible" is checked the visibility depends on the "publication date & time" attribute. If unchecked the page is not shown under any circumstances, even if the publication period valid. =============== -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
0 / 0

[JBoss JIRA] (GTNMGMT-25) NoSuchDataException when trying to edit navigation after import of classic portal

by Tomas Kyjovsky (Created) (JIRA)

NoSuchDataException when trying to edit navigation after import of classic portal --------------------------------------------------------------------------------- Key: GTNMGMT-25 URL: https://issues.jboss.org/browse/GTNMGMT-25 Project: GateIn Management Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.0.0-Beta04 Reporter: Tomas Kyjovsky Assignee: Nick Scavelli Attachments: error-rendering-portlets-1.png, error-rendering-portlets-2.png, no-such-data-exception.txt NoSuchDataException appears when rendering Navigation, Breadcrumbs, Footer portlets. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (GTNWSRP-231) Update documentation on where the producer configuration file is located and how to change its location

by Chris Laprun (JIRA)

Update documentation on where the producer configuration file is located and how to change its location ------------------------------------------------------------------------------------------------------- Key: GTNWSRP-231 URL: https://issues.jboss.org/browse/GTNWSRP-231 Project: GateIn WSRP Issue Type: Bug Components: Documentation Affects Versions: 2.0.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.0.1-GA, 2.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNWSRP-233) Update documentation to provide details on new packaging.

by Chris Laprun (JIRA)

Update documentation to provide details on new packaging. --------------------------------------------------------- Key: GTNWSRP-233 URL: https://issues.jboss.org/browse/GTNWSRP-233 Project: GateIn WSRP Issue Type: Feature Request Components: Documentation Affects Versions: 2.1.0-Beta04 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2191) Update gatein-management to 1.0.0-Beta05

by Nick Scavelli (Created) (JIRA)

Update gatein-management to 1.0.0-Beta05 ---------------------------------------- Key: GTNPORTAL-2191 URL: https://issues.jboss.org/browse/GTNPORTAL-2191 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Management Reporter: Nick Scavelli Assignee: Nick Scavelli -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues October 2011