November 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2268) Allow WSRP configuration files to be picked up from gatein.conf.dir

by Chris Laprun (Created) (JIRA)

Allow WSRP configuration files to be picked up from gatein.conf.dir ------------------------------------------------------------------- Key: GTNPORTAL-2268 URL: https://issues.jboss.org/browse/GTNPORTAL-2268 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: WSRP integration Affects Versions: 3.2.0-M01 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 3.2.0-Beta01 -- 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-2280) Gadget preferences are broken

by Matt Wringe (Created) (JIRA)

Gadget preferences are broken ----------------------------- Key: GTNPORTAL-2280 URL: https://issues.jboss.org/browse/GTNPORTAL-2280 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe Gadget preferences don't work properly 1) it does not currently load the default values. This means if you go to edit a gadget, the preference values will be appear empty. So if you click save, it will overwrite all the values. This also applies to enum properties where the default value is not correctly set. 2) preferences appear to be displayed in a random order, and not the order specified in the gadget's xml file -- 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

8
8
0 / 0

[JBoss JIRA] (GTNPORTAL-2281) Can't maximize gadgets

by Matt Wringe (Created) (JIRA)

Can't maximize gadgets ---------------------- Key: GTNPORTAL-2281 URL: https://issues.jboss.org/browse/GTNPORTAL-2281 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe Can't maximize a gadget. For example, try with the following gadget: http://hosting.gmodules.com/ig/gadgets/file/112581010116074801021/turtle.xml Note that this gadget worked fine in GateIn 3.1.0.FINAL -- 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

10
17
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] (GTNPORTAL-2301) Exception when viewing Application registry portlet in view mode

by Hai Nguyen (Created) (JIRA)

Exception when viewing Application registry portlet in view mode ---------------------------------------------------------------- Key: GTNPORTAL-2301 URL: https://issues.jboss.org/browse/GTNPORTAL-2301 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hai Nguyen Go to desktop page Click edit layout Drag & drop application registry portlet Click Switch view mode -> Show exception and don't show application registry on page SEVERE: LocationAwareLogger had some issues on method 'log' invocation. Using location unaware metho ds. Error while rendering the porlet java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java: 39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorIm pl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.exoplatform.webui.Util.createObject(Util.java:63) at org.exoplatform.webui.application.WebuiApplication.createUIComponent(WebuiApplication.jav a:109) at org.exoplatform.portal.application.PortalStateManager.restoreUIRootComponent(PortalStateM anager.java:89) at org.exoplatform.webui.application.portlet.ParentAppStateManager.restoreUIRootComponent(Pa rentAppStateManager.java:37) at org.exoplatform.webui.application.portlet.PortletApplication.render(PortletApplication.ja va:294) ... -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2300) Can't logout in Standalone Application

by Hai Nguyen (Created) (JIRA)

Can't logout in Standalone Application -------------------------------------- Key: GTNPORTAL-2300 URL: https://issues.jboss.org/browse/GTNPORTAL-2300 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hai Nguyen Access to standalone application (that belongs to root) --> show login page --> login as demo Show error page that alert : no permission --> OK Click Logout link --> can't logout --> NOK -- 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

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-269) Problem with resourceId while rendering bookingMapPortlet over WSRP

by Michal Vanco (Created) (JIRA)

Problem with resourceId while rendering bookingMapPortlet over WSRP ------------------------------------------------------------------- Key: GTNWSRP-269 URL: https://issues.jboss.org/browse/GTNWSRP-269 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.1.0-GA Environment: EPP5.2.0 CR01 seamBooking demo from 2.2.0.GA.EPP520 Reporter: Michal Vanco Assignee: Chris Laprun Attachments: seamBookingMap.txt Problem while serving resource for the portlet: selfv2./portalBookingDemo.bookingMapPortlet java.lang.IllegalArgumentException: GetResource needs a valid resource id. WSRP and PBR version weren't changed at CR01, that can be potentially caused by other change (& or double & issues at resources). And this error wasn't present at 5.2.0 ER06 -- 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

5
5
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues November 2011