March 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1761) UserImpl toString() wrong return value : only the @organizationId info, no userName info nor other values.

by Antoine Herzog (JIRA)

UserImpl toString() wrong return value : only the @organizationId info, no userName info nor other values. ----------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1761 URL: https://issues.jboss.org/browse/GTNPORTAL-1761 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.1.0-GA Reporter: Antoine Herzog See the bug in exo-core : http://jira.exoplatform.org/browse/COR-224 This bug in GateIn depends on the bug fix in exo-core. GateIn 3.1.0-GA uses org.exoplatform.core.version : 2.3.2-GA exo-core is now in version 2.3.5-GA, going to 2.3.6. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1646) during shutdown, the PortalContainer throws a PicoIntrospectionException

by Matt Wringe (JIRA)

during shutdown, the PortalContainer throws a PicoIntrospectionException ------------------------------------------------------------------------ Key: GTNPORTAL-1646 URL: https://jira.jboss.org/browse/GTNPORTAL-1646 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe When stopping the server (JBoss version of GateIn), I am sometimes running into the following error: 18:45:06,686 ERROR [STDERR] Exception in thread "Thread-17" 18:45:06,689 ERROR [STDERR] org.picocontainer.PicoIntrospectionException: Failed when calling stop on org.exoplatform.container.PortalContainer@170cd3b6 18:45:06,689 ERROR [STDERR] at org.picocontainer.defaults.LifecycleVisitor.traverse(LifecycleVisitor.java:81) 18:45:06,689 ERROR [STDERR] at org.picocontainer.defaults.LifecycleVisitor.stop(LifecycleVisitor.java:121) 18:45:06,689 ERROR [STDERR] at org.exoplatform.container.ConcurrentPicoContainer.stop(ConcurrentPicoContainer.java:468) 18:45:06,689 ERROR [STDERR] at org.exoplatform.container.ExoContainer.stop(ExoContainer.java:194) 18:45:06,689 ERROR [STDERR] at org.exoplatform.container.RootContainer.stop(RootContainer.java:655) 18:45:06,689 ERROR [STDERR] at org.exoplatform.container.RootContainer$ShutdownThread.run(RootContainer.java:649) 18:45:06,689 ERROR [STDERR] Caused by: org.picocontainer.PicoIntrospectionException: Failed when calling stop on org.gatein.portal.wsrp.WSRPServiceIntegration@37b96ed 18:45:06,689 ERROR [STDERR] at org.picocontainer.defaults.LifecycleVisitor.traverse(LifecycleVisitor.java:81) 18:45:06,689 ERROR [STDERR] at org.picocontainer.defaults.LifecycleVisitor.stop(LifecycleVisitor.java:121) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1412) Don't show node(page) after created on navigation portlet

by Hang Nguyen (JIRA)

Don't show node(page) after created on navigation portlet --------------------------------------------------------- Key: GTNPORTAL-1412 URL: https://jira.jboss.org/browse/GTNPORTAL-1412 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Login by root - Create new portal ( have right to access, don't have right to edit) - Change to new portal - Click Site - Click Edit Navigation of Classic portal - Add new node for this Navigation ( ex: test) - Click Save - Return to Classic portal => On Navigation portlet don't show new node which created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1513) Gadgets become unavailable from JCR after multiple edits.

by Jon Kranes (JIRA)

Gadgets become unavailable from JCR after multiple edits. --------------------------------------------------------- Key: GTNPORTAL-1513 URL: https://jira.jboss.org/browse/GTNPORTAL-1513 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: JCR integration Affects Versions: 3.1.0-GA Environment: Windows XP, JBoss AS 5.1. Reporter: Jon Kranes After editing a gadget's XML multiple times, the gadget becomes unavailable. The gadget still appears in the Application Registry, but any page where the gadget is embedded shows a 404 error. If you try to delete or edit the gadget, the system responds with an error dialog with the message 'Unknown error'. If you paste the gadget's 'View URL' into a browser, the response indicates a java.io.FileNotFoundException. The number of edits allowed before the error occurs is not consistent but seems to generally be in the range of 10 - 20. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1727) Overriding configuration unit in AbstractKernelTest

by Minh Hoang TO (JIRA)

Overriding configuration unit in AbstractKernelTest --------------------------------------------------- Key: GTNPORTAL-1727 URL: https://issues.jboss.org/browse/GTNPORTAL-1727 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Minh Hoang TO Assignee: Minh Hoang TO Creating JUnit test in GateIn from scratch is very complex due to numbers of service component configurations. That 's why the project test.core provides AbstractKernelTest, the class overriding services configuration loading ( custom class loader GateinTestClassLoader is set as context class loader of thread running test, service configuration is retrieved from paths defined in annotation @ConfigurationUnit) As the annotation @ConfiguredBy is also @Inherited, that makes default service configuration appears in all test unit, even when unnecessary. That slows down test running for sure. It might be better to define @OverridingConfigurationUnit annotation, processed by AbstractKernelTest to remove service component configuration when it is not used for JUnit test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1728) Define fine-grained test configuration in test.core

by Minh Hoang TO (JIRA)

Define fine-grained test configuration in test.core --------------------------------------------------- Key: GTNPORTAL-1728 URL: https://issues.jboss.org/browse/GTNPORTAL-1728 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Minh Hoang TO Assignee: Minh Hoang TO The project test.core does provide default configuration of GateIn services. Anyway, the configuration of independent services are not declared in seperated .xml files, so to create a new JUnit test extending AbstractKernelTest, developer has only two choices: 1. Reuse the existing configuration, which means having all GateIn service components for the test 2. Reconfigure from scratch, which is error-prone and time consuming -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1052) configuration of oauth for signed request

by jerem j (JIRA)

configuration of oauth for signed request ----------------------------------------- Key: GTNPORTAL-1052 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1052 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0-GA Reporter: jerem j In gadget, you can do request to an oAuth endpoint. In some case, the distant server want to make sure who is the server (or developer) doing the request. To do so, they provide a oauth consumer key and a oauth consumer secret. You need to associate this with your gadget. So everytime your gadget is going to do request to their server, it will use this keys. For example, google is using such a mechanism to protect their analytics APIs. You need to register a domain on https://www.google.com/accounts/ManageDomains and google will give you the OAuth Consumer Key and OAuth Consumer Secret. The problem is that to configure this now, you need to modify the file oauth.json that is located in jar. It's something similar to what has been done for http://jira.exoplatform.org/browse/SOC-650 but the properties are different: * Gadget URL * oAuth endpoint name (used in the gadget to reference this endpoint) * consumer_key * consumer_secret * key_type Also a UI to configure this would be awesome. -- 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

11 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1708) Create an UI form for managing the OAuth Consumer information

by Khoi Nguyen (JIRA)

Create an UI form for managing the OAuth Consumer information ------------------------------------------------------------- Key: GTNPORTAL-1708 URL: https://jira.jboss.org/browse/GTNPORTAL-1708 Project: GateIn Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Khoi Nguyen Some functions must have: - Add a Consumer information - Edit a consumer - Remove a consumer - List all of consumer and paging them A consumer information consist of service name, gadgetURL, consumer key, consumer secret, type -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1725) Make flexible for displaying GateIn Toolbar

by kien nguyen (JIRA)

Make flexible for displaying GateIn Toolbar ------------------------------------------- Key: GTNPORTAL-1725 URL: https://issues.jboss.org/browse/GTNPORTAL-1725 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: kien nguyen We always have a Toolbar on top screen of GateIn when user logged in by an account. Sometimes, Users want to hide it because they don't have any important tasks on this toolbar (as normal users, demo users, etc). We should make this toolbar more flexibilitier, support hiding it on UI. Looks bottom toolbar of javabeat site (http://www.javabeat.net/) to have an example -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1709) Screen refreshes and resource handling when using the richfaces demo over wsrp

by Matt Wringe (JIRA)

Screen refreshes and resource handling when using the richfaces demo over wsrp ------------------------------------------------------------------------------ Key: GTNPORTAL-1709 URL: https://jira.jboss.org/browse/GTNPORTAL-1709 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WSRP integration Reporter: Matt Wringe Assignee: Chris Laprun When using the richfaces demo over wsrp, the page will sometimes refresh instead of updating the ajax content. This can be seen in the calender example when trying to click on a date in the organizer creation tab. This is due to the portal not properly receiving a resource request and it default to a render request. The base of this problem seems to be with how we deal with urls and in particular urls with & in them instead of just &. For the page refresh, what is happening here is that the QueryStringParser from the common module expects query strings to contain & and not & It uses this token to break apart the properties and in this case it does not receive the correct property to do a resource fetch and instead defaults to a render request. If we replace the & with & before calling the QueryStringParser then we can get the page to do a resource request, but we run into a similar problem, we now receive amp;portal-resourceId instead of portal-resourceId and we can't properly decode the resource url. Note that this does not happen all the time, many other wsrp resource requests (even through the bridge) work properly, there is something occurring in some situations where this occurs. I am not sure if we are just not encoding the url properly at some point, or if the bridge is manipulating the url in a manner which is causing this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2011