March 2012 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-882) Smart handling of unconfigured MailService

by Patrice Lamarque (JIRA)

Smart handling of unconfigured MailService ------------------------------------------ Key: GTNPORTAL-882 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-882 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Patrice Lamarque Priority: Optional An implementation of org.exoplatform.services.mail.MailService that would be able to detect when no configuration is set. Then it would send an applicative exception that can be catched by the application layer to invite administrators to configure the mailservice with their own. For instance, it could warn the user : "We could not send the recovery email because your admin has not configured it properly" And give more directions in the logs for the admin : "The MailService was not configured. Please edit mail-configuration.xml and set your own settings." -- 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, 11 months

6
12
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-879) Provide a way to configure Login and Logout URL to integrate with SSO solutions

by Tugdual Grall (JIRA)

Provide a way to configure Login and Logout URL to integrate with SSO solutions ------------------------------------------------------------------------------- Key: GTNPORTAL-879 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-879 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tugdual Grall Some IS have developped custom SSO solution (or use product). To be able to login or logout the portal need to send a request to some specific pages. It will be interesting to provide a way to confgure the link to a login form (with some redirect option) and more important a way to direct to a logout URL. -- 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, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-889) Reduce the amount of information output as INFO on the console.

by Chris Laprun (JIRA)

Reduce the amount of information output as INFO on the console. --------------------------------------------------------------- Key: GTNPORTAL-889 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-889 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.0.0-GA Reporter: Chris Laprun Some of that information is slightly useful but most of it should really be either completely removed or at the very least sent to DEBUG or TRACE file logs. See for example IndexMerger, lifecycle (JSF?) output. -- 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, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1053) Add a complete Ajax call function in eXo JS library (current AjaxGet() function cannot be use for simple XHR calls)

by Tugdual Grall (JIRA)

Add a complete Ajax call function in eXo JS library (current AjaxGet() function cannot be use for simple XHR calls) ------------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1053 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1053 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.0.0-GA Reporter: Tugdual Grall It would be great to have a simple set of JS function in eXo JS to do Ajax calls where developer can manipulate response content and status. It looks like the ajaxGet() [and other related methods], are only made to manipulate the DOM and force the "waiting screen". The idea will be to have something as simple as: exoAjax.post( URL, { paramName : 'paramValue',paramName : 'paramValue' }, function (response) { // XHR response goes here // any callback } -- 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, 11 months

7
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1122) Portlet icons locations need to be skin independent [or dependent]

by Matt Wringe (JIRA)

Portlet icons locations need to be skin independent [or dependent] ------------------------------------------------------------------ Key: GTNPORTAL-1122 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1122 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe If a portlet wants to have a custom icon shown in the application registry or in the page editor, then they can place a png in a special location. Currently this location is: skin/DefaultSkin/portletIcons/PortletName.png But this icon is shown for all skins, regardless if its the DefaultSkin or not (see ApplicationRegistryServiceImpl.getApplicationIconURL for where its hardcoded to this) This location should be changed to a location which doesn't mention DefaultSkin, or it should be changed so that it is dependent on the current portal skin (for example skin/SimpleSkin/portleticons/PortletName.png would be the icon if the current portal skin is the SimpleSkin). -- 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, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1080) Chrome - Add gadget on dashboard with simple click, no need to DnD

by Michal Vanco (JIRA)

Chrome - Add gadget on dashboard with simple click, no need to DnD ------------------------------------------------------------------ Key: GTNPORTAL-1080 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1080 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.0.0-GA Environment: Google chrome on windows Reporter: Michal Vanco Chrome: Adding gadget on dashboard can be done by only click on Gadget in list. In other browsers dragAndDrop have to be done. (there is some ui test where is click and dragAndDrop -> gadget is added twice in chrome) -- 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, 11 months

7
12
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1250) There are useless messages printed by UIPortlet class.

by le thanh quang (JIRA)

There are useless messages printed by UIPortlet class. ------------------------------------------------------ Key: GTNPORTAL-1250 URL: https://jira.jboss.org/browse/GTNPORTAL-1250 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.0.0-GA Reporter: le thanh quang There are some useless messages at info level printed by org.exoplatform.portal.webui.application.UIPortlet class when load a portlet. The messages are as following log section: Apr 16, 2010 4:39:05 PM org.exoplatform.portal.webui.application.UIPortlet supportsPublishingEvent INFO: The portlet PortletContext[local./forum.ForumPortlet] doesn't support producing the event : QuickReplyEvent Apr 16, 2010 4:39:05 PM org.exoplatform.portal.webui.application.UIPortlet supportsPublishingEvent INFO: The portlet PortletContext[local./forum.ForumPortlet] doesn't support producing the event : ForumPollEvent Apr 16, 2010 4:39:05 PM org.exoplatform.portal.webui.application.UIPortlet supportsPublishingEvent In the contrast, if an event is configured as supported-publishing-event in portlet.xml file, another message is thrown as May 26, 2010 2:12:38 PM org.exoplatform.portal.webui.application.UIPortlet supportsPublishingEvent INFO: The Portlet PortletContext[local./forum.ForumPortlet] supports producing the event : QuickReplyEvent Therefore, It's better if the such messages are refined to be more concise and convenient. -- 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, 11 months

6
8
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1230) Inherited node ACL

by Thomas Heute (JIRA)

Inherited node ACL ------------------ Key: GTNPORTAL-1230 URL: https://jira.jboss.org/browse/GTNPORTAL-1230 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Reporter: Thomas Heute Fix For: 3.2.0-GA As of now it is difficult to maintain gazillion of nodes even in a hierarchy. when you have: A<-B<-C (B is a child of A, C is a child of B) and you want to restrict access to that tree, you need to define security rules on the 3 *pages*. (and modify the pages everytime you want to change a restriction) As of now we don't have security restrictions on the node itself, we would need to add this feature and make it inherited. the Picketlink Authz framework can do this effectively, but we would need an answer to this issue prior to the integration. We should be able to tell that A is restricted to admins, and on an access to C check for parent restrictions. It should also be possible to add a restriction on B. In some cases, one node may want to break the inheritance to define other rules. -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1262) Don't return to default portal after sign out from new portal which limit by number of access users to be public

by Hang Nguyen (JIRA)

Don't return to default portal after sign out from new portal which limit by number of access users to be public ---------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1262 URL: https://jira.jboss.org/browse/GTNPORTAL-1262 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Create new portal with limit by number of access users to be public - Choose new portal to use - Sign out ==> Escape private mode of new portal, but don't return to public mode of default portal -- 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, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1318) Provide a way to disable 'classic'

by Patrice Lamarque (JIRA)

Provide a way to disable 'classic' ---------------------------------- Key: GTNPORTAL-1318 URL: https://jira.jboss.org/browse/GTNPORTAL-1318 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0-CR01 Reporter: Patrice Lamarque Fix For: 3.2.0-GA The 'classic' portal is builtin in gatein. Extension writers will typically want to define their own portal different of 'classic'. They may want to make their own portal the default too. Today, the only way to to this is to edit the portal.war and modify the builtin configuration for classic (UserPortalConfigService). We need a way to indicate the portal to not attempt to load 'classic', but use another definition instead. -- 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, 11 months

8
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2012