July 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-368) escapeXml feature is ignored in wsrp.

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-368?page=com.atlassian.jira.plugi... ] Chris Laprun updated GTNWSRP-368: --------------------------------- Fix Version/s: 2.0.2-GA 2.2.11.Final (was: 2.2.10.Final) > escapeXml feature is ignored in wsrp. > ------------------------------------- > > Key: GTNWSRP-368 > URL: https://issues.jboss.org/browse/GTNWSRP-368 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Producer > Affects Versions: 2.2.9.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.0.2-GA, 2.2.11.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-369) Portlet sessions are not properly scoped on consumer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-369?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated GTNWSRP-369: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=981585, https://bugzilla.redhat.com/show_bug.cgi?id=983898 (was: https://bugzilla.redhat.com/show_bug.cgi?id=981585) > Portlet sessions are not properly scoped on consumer > ---------------------------------------------------- > > Key: GTNWSRP-369 > URL: https://issues.jboss.org/browse/GTNWSRP-369 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Consumer > Affects Versions: 2.2.9.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.10.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-369) Portlet sessions are not properly scoped on consumer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-369?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-369: ------------------------------------------------- Adam Kovari <akovari(a)redhat.com> made a comment on [bug 983898|https://bugzilla.redhat.com/show_bug.cgi?id=983898] +++ This bug was initially created as a clone of Bug #981585 +++ Description of problem: We have created a remote portlet (wsrp) which saves a value as session attribute: request.getPortletSession().setAttribute("inputValue", inputValue) and retrieves it again String inputValue = (String) request.getPortletSession().getAttribute("inputValue"); The problem is, that if we are placing the portlet twice one the same page, both portlets are showing the same inputValue. So the setAttribute() and getAttribute() method is not unique for the portlet instance. Version-Release number of selected component (if applicable): EPP 5.1.1 How reproducible: Always Steps to Reproduce: 1. See description Actual results: Portlet Session attributes shared accross same portlets on one page Expected results: Portlet Session attributes not shared accross same portlets on one page Additional info: > Portlet sessions are not properly scoped on consumer > ---------------------------------------------------- > > Key: GTNWSRP-369 > URL: https://issues.jboss.org/browse/GTNWSRP-369 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Consumer > Affects Versions: 2.2.9.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.10.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-108) BaseURLImpl.write implementation is incorrect

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPC-108?page=com.atlassian.jira.plugin.... ] Julien Viet resolved GTNPC-108. ------------------------------- Resolution: Done thanks for the fix! > BaseURLImpl.write implementation is incorrect > --------------------------------------------- > > Key: GTNPC-108 > URL: https://issues.jboss.org/browse/GTNPC-108 > Project: GateIn Portlet Container > Issue Type: Bug > Affects Versions: 2.4.1.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.4.2.Final > > > Context: JSR-286 specifies that portlet URLs are now XML encoded by default. BaseURL.write is thus supposed to be functionally equivalent to BaseURL.write(writer, true) but the current implementation is write(writer, false). > Moreover, URLFormat allows users to control how a Portlet URL is rendered, in particular with respect to XML escaping. However, BaseURLImpl uses an internal array (FORMATS) that uses null instead of false to that is passed along when portlets want to *not* XML-escape URLs. Since URLFormat uses a Boolean instead of a boolean and that the default value for escapeXML needs to be true per the spec, using null instead of Boolean.FALSE is confusing because null indicates absence of value which would indicate using whatever the default one is (in this case, true). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2899) The membership type "*" is not interpreted

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2899?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-2899: ---------------------------------- Fix Version/s: 3.7.0.Final > The membership type "*" is not interpreted > ------------------------------------------- > > Key: GTNPORTAL-2899 > URL: https://issues.jboss.org/browse/GTNPORTAL-2899 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.5.3.Final > Environment: eXo Platform 4.0.0-Beta2 > Reporter: Hela Zekri > Assignee: Trong Tran > Priority: Blocker > Labels: portal-s71, worked > Fix For: 3.7.0.Final > > > {color:red} > In eXo Platform, we have the membership type "*". If user has this membership type in a group, it means that he has all membership types in this group. > {color} > *Please try this scenario :* > Add a user that has the membership type "manager" in "/platform/administrators" group and the membership type "*" in "/platform/users" group. > When this user clicks "add page" in "Page Management", he has the possibility to choose the owner type "group" or "portal". If he chooses "group", the expected output is that he gets as "Owner Id", a selectbox that contains all groups in which he has the membership type "manager". > (!) The membership type "manager" is set in "portal-configuration.xml" as value-param to UserACL component : > {code:xml} > <value-param> > <name>navigation.creator.membership.type</name> > <description>specific membership type have full permission with group navigation</description> > <value>manager</value> > </value-param> > {code} > In this case, user should get as "Owner Id" a selectbox that contains "/platform/administrators" and "/platform/users" groups(The membership type "*" includes "manager" membership type). > But the current behavior is that the selectbox of "Owner Id" contains only the group "/platform/administator". This is due to the fact that the relationship "*" is considered as a String and not interpreted. > *There are two possible solutions to this problem :* > 1- Set the possibility to put many values for "navigation.creator.membership.type" value-param. So that we could do for example : > {code:xml} > <value-param> > <name>navigation.creator.membership.type</name> > <description>specific membership type have full permission with group navigation</description> > <value>*,manager</value> > </value-param> > {code} > 2- In "_findRoles_" method in "_org.picketlink.idm.impl.api.session.managers.RoleManagerImpl_" class : > In the code bellow, each relationship of a user is compared to roleType ("manager"). If it is equal, it will be added to the list that will be returned. So even "*" is compared to "manager", it is not equal, so it won't be added. > {code} > for (IdentityObjectRelationship relationship : relationships) > { > if (roleType != null) > { > if (roleType.getName().equals(relationship.getName())) > { > roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject()))); > } > } > else > { > roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject()))); > } > } > {code} > We created [https://issues.jboss.org/browse/PLIDM-40] in which we propose a patch that adds a test on "*" value. > In the patch, we changed : > {code} > if (roleType.getName().equals(relationship.getName())) > {code} > to : > {code} > if ((roleType.getName().equals(relationship.getName())) || relationship.getName().equals("*")) > {code} > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3176) Deleting a site used in redirects leads into NPE

by Alexandre Mendonça (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3176?page=com.atlassian.jira.pl... ] Alexandre Mendonça updated GTNPORTAL-3176: ------------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/572 > Deleting a site used in redirects leads into NPE > ------------------------------------------------ > > Key: GTNPORTAL-3176 > URL: https://issues.jboss.org/browse/GTNPORTAL-3176 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Viliam Rockai > Assignee: Alexandre Mendonça > > When you delete a site, which is used in portal redirects, it causes several bugs. For instance, try to delete "mobile" site (delete in site management menu). You can still see a link to mobile site in the redirect portlet at the bottom of the page and after accessing it's redirect configuration you'll see a NPE: > 16:09:32,840 ERROR [stderr] (http-/127.0.0.1:8080-5) java.lang.NullPointerException > 16:09:32,841 ERROR [stderr] (http-/127.0.0.1:8080-5) at org.gatein.ui.admin.redirect.beans.EditRedirectBean.loadRedirectNodes(EditRedirectBean.java:639) > 16:09:32,841 ERROR [stderr] (http-/127.0.0.1:8080-5) at org.gatein.ui.admin.redirect.beans.EditRedirectBean.load(EditRedirectBean.java:605) > 16:09:32,841 ERROR [stderr] (http-/127.0.0.1:8080-5) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3180) portal-redirects element not in gatein_objects XSD

by Nick Scavelli (JIRA)

Nick Scavelli created GTNPORTAL-3180: ---------------------------------------- Summary: portal-redirects element not in gatein_objects XSD Key: GTNPORTAL-3180 URL: https://issues.jboss.org/browse/GTNPORTAL-3180 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Nick Scavelli Assignee: Matt Wringe portal-redirects element and it's children are not present in gatein_objects XSD. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3178) Disabled Alternative sites should not be displayed

by Matt Wringe (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3178?page=com.atlassian.jira.pl... ] Matt Wringe updated GTNPORTAL-3178: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/571 > Disabled Alternative sites should not be displayed > -------------------------------------------------- > > Key: GTNPORTAL-3178 > URL: https://issues.jboss.org/browse/GTNPORTAL-3178 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Mobile > Reporter: Matt Wringe > Assignee: Matt Wringe > > if alternative sites are disabled, they should not be displayed in the redirect portlet lists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3175) Newly created space not showing in the spaces list in redirect admin portlet

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3175?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-3175: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Newly created space not showing in the spaces list in redirect admin portlet > ---------------------------------------------------------------------------- > > Key: GTNPORTAL-3175 > URL: https://issues.jboss.org/browse/GTNPORTAL-3175 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Viliam Rockai > Assignee: Nick Scavelli > > When creating a new space upon a newly created group, this space is not listed in the spaces list in the redirect admin portlet. > 1. create a new group in the org management, i.e. "Test" > 2. create a new space in the group "manage groups" by "add navigation" > 3. add some node with page into that space navigation > this is not listed in the spaces list in the redirect admin portlet but it's listed in the group menu. this is related to the default value of the limit filter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3166) portal-redirects rules are not exported during Site export

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3166?page=com.atlassian.jira.pl... ] Nick Scavelli reassigned GTNPORTAL-3166: ---------------------------------------- Assignee: Nick Scavelli (was: Alexandre Mendonça) > portal-redirects rules are not exported during Site export > ---------------------------------------------------------- > > Key: GTNPORTAL-3166 > URL: https://issues.jboss.org/browse/GTNPORTAL-3166 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Nick Scavelli > Fix For: 3.7.0.Final > > > Steps to reproduce: > - Login as root and go to http://localhost:8080/portal/g/:platform:administrators/administration/si... > - Export "classic" site > - In portal_classic_...zip/portal/classic/portal.xml I am not seeing redirect rules exported in <portal-redirects> element. By default, there should be one redirect rule for redirect from "classic" to "mobile" site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues July 2013