September 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1554) Remove portlet from appication registry after the web app has removed

by Khoi Nguyen (JIRA)

Remove portlet from appication registry after the web app has removed --------------------------------------------------------------------- Key: GTNPORTAL-1554 URL: https://jira.jboss.org/browse/GTNPORTAL-1554 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen After a web app has removed, application registry should also remove the related portlet and category from list -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (GTNPC-36) GateIn should support user attributes (Portlet Specification PLT.21)

by Joerg Harm (JIRA)

GateIn should support user attributes (Portlet Specification PLT.21) -------------------------------------------------------------------- Key: GTNPC-36 URL: https://jira.jboss.org/browse/GTNPC-36 Project: GateIn Portlet Container Issue Type: Feature Request Affects Versions: 2.2.0-GA Reporter: Joerg Harm Up to now there is no Java standard to access user information. Therefore, the recommendation of the PortletSpec should be supported by GateIn. -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1511) Include GateIn version in the log

by Thomas Heute (JIRA)

Include GateIn version in the log --------------------------------- Key: GTNPORTAL-1511 URL: https://jira.jboss.org/browse/GTNPORTAL-1511 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Heute When starting GateIn, it would be necessary to see in the logs which exact version of GateIn is running -- 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, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1553) link "Identifiant / mot de passe oublié ?" not found when acces in private mode

by houssem njah (JIRA)

link "Identifiant / mot de passe oublié ?" not found when acces in private mode ------------------------------------------------------------------------------- Key: GTNPORTAL-1553 URL: https://jira.jboss.org/browse/GTNPORTAL-1553 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.1.0-GA Reporter: houssem njah Attachments: 1.jpg, 2.jpg Hi, there was 2 sceen alllow user to be logged in: * the first is when we use this url: http://server:port/portal/private/site (see attach1) * the second is when we use this url: http://server:port/portal/public/site, on this page we click on a button wich will give us a screen to allows us to put our login/pwd (see attach2). the difference between this two screen, is the first one doesn't have a link to allow user inform that he is lost his login or password. so it must be added on the first screen -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (GTNWSRP-16) Visibility of remote portlets in App.registry

by Michal Vanco (JIRA)

Visibility of remote portlets in App.registry --------------------------------------------- Key: GTNWSRP-16 URL: https://jira.jboss.org/jira/browse/GTNWSRP-16 Project: GateIn WSRP Issue Type: Bug Components: Admin GUI Affects Versions: 1.0.0 Reporter: Michal Vanco Assignee: Chris Laprun When I create new consumer, I can see remote portlet in App.registry (Portlets/Remote), when I click Auto Import, category with remote portlet is created. When I deactivate consumer, I can't see the portlet in App.category (Portlets/Remote), but when I click Auto import, category with remote portlet is still there. Is it ok? Shouldn't it dissapper if it is not present? I am also able to add this remote portlet to page and it works. After I delete consumer, I can still see the caterory with portlet in App.registry, when click Auto import, in log is: ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample And when I add this portlet to page I can see "This portlet encountered an error and could not be displayed" and in log is: org.gatein.pc.api.NoSuchPortletException: No such portlet self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample I think that when I deactivate/delete consumer, I shouldn't be able to see its portlets anywhere. -- 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, 10 months

6
9
0 / 0

[JBoss JIRA] Created: (GTNWSRP-95) Navigational State not being update in a action url or through a form response

by Matt Wringe (JIRA)

Navigational State not being update in a action url or through a form response ------------------------------------------------------------------------------ Key: GTNWSRP-95 URL: https://jira.jboss.org/browse/GTNWSRP-95 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.0.0-Beta01 Reporter: Matt Wringe Assignee: Chris Laprun Fix For: 2.0.0-Beta02 There is something strange happening with navigational state not being sent back to a producer in a action url or through an action response from an html form. The navigational state does seem to get updated through a render url. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1525) User, Group names are case-sensitive, this doesn't feel right

by kien nguyen (JIRA)

User, Group names are case-sensitive, this doesn't feel right ------------------------------------------------------------- Key: GTNPORTAL-1525 URL: https://jira.jboss.org/browse/GTNPORTAL-1525 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: kien nguyen GateIn should not use User and Group names in case-sensitive, such as "john" and "JoHn" are known as two users but they have the same meaning. -- 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, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1528) parameterized users/groups/memberships permissions setting for EPP 5.

by Gary Hu (JIRA)

parameterized users/groups/memberships permissions setting for EPP 5. --------------------------------------------------------------------- Key: GTNPORTAL-1528 URL: https://jira.jboss.org/browse/GTNPORTAL-1528 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Hu In EPP 5, there are many places that need to specify the permission settings for different users, groups and memberships. For example, the admin group setting *:/platform/administrators is referenced by gatein and eXo WCM in many places. It would be a neater approach if we could use some parameterized setting so that if we need to make a change we just need to modify one place. It's much easier for the user to find/replace the settings. Here is the proposal. We can define some key/value type properties and add them to the $EPP5_HOME/server/$PROFILE/conf/gatein/configuration.properties file: gatein.user.owner=root gatein.group.admin=*:/platform/administrators gatein.group.user=*:/platform/users gatein.group.guest=*:/platform/guests gatein.group.webcontributor=*:/platform/web-contributors gatein.membership.author=author gatein.membership.publisher=publisher gatein.membership.manager=manager gatein.membership.member=member And the various gatein and sitepublisher files would then reference them doing something like this: ${gatein.group.admin} -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1492) implement paginated query support for the LDAP store.

by Gary Hu (JIRA)

implement paginated query support for the LDAP store. ------------------------------------------------------ Key: GTNPORTAL-1492 URL: https://jira.jboss.org/browse/GTNPORTAL-1492 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Gary Hu Current LDAP store implementation doesn't support paginated queries. The following is one scenario that is not covered by the current implementation: If a LDAP query returns too many entries that exceed the limitation of LDAP server the query should be broke down to multiple separate queries each returning entries that satisfy the LDAP server limitation. -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1522) Gadget haven't vertical scrollbar if gadget content is long

by Khoi Nguyen (JIRA)

Gadget haven't vertical scrollbar if gadget content is long ----------------------------------------------------------- Key: GTNPORTAL-1522 URL: https://jira.jboss.org/browse/GTNPORTAL-1522 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen Add a gadget having long content, and overflow its gadget (http://dirk.balfanz.googlepages.com/contacts.xml), we haven't a vertical scrollbar in this case -- 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, 10 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2011