From issues at jboss.org  Mon Sep  1 12:07:00 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 1 Sep 2014 12:07:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-378) WSRP Producer is missing
 distributable tag
In-Reply-To: <JIRA.12546193.1405085989000@Atlassian.JIRA>
References: <JIRA.12546193.1405085989000@Atlassian.JIRA>
	<JIRA.12546193.1405085989000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546193.1405085989000.21465.1409587620544@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997528#comment-12997528 ] 

RH Bugzilla Integration commented on GTNWSRP-378:
-------------------------------------------------

vramik at redhat.com changed the Status of [bug 1115512|https://bugzilla.redhat.com/show_bug.cgi?id=1115512] from ON_QA to VERIFIED

> WSRP Producer is missing distributable tag
> ------------------------------------------
>
>                 Key: GTNWSRP-378
>                 URL: https://issues.jboss.org/browse/GTNWSRP-378
>             Project: GateIn WSRP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Producer
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> See BZ#1115512 . The WSRP Producer WAR seems to be missing the <distributable/> tag on web.xml , causing session replication to not work for communication between consumer and producer. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep  1 12:07:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 1 Sep 2014 12:07:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3519) "Import applications"
 fails when remote portlet name clashes with local portlet
In-Reply-To: <JIRA.12546150.1405064271000@Atlassian.JIRA>
References: <JIRA.12546150.1405064271000@Atlassian.JIRA>
	<JIRA.12546150.1405064271000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546150.1405064271000.21468.1409587679873@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNPORTAL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997529#comment-12997529 ] 

RH Bugzilla Integration commented on GTNPORTAL-3519:
----------------------------------------------------

vramik at redhat.com changed the Status of [bug 1117813|https://bugzilla.redhat.com/show_bug.cgi?id=1117813] from ON_QA to VERIFIED

> "Import applications" fails when remote portlet name clashes with local portlet
> -------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3519
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3519
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.8.5.Final, 3.9.0.Final
>
>
> The "import applications" on the application registry fails when there's a remote portlet with the same name as a local portlet, due to "unknown error" on the user interface, and "Cannot create a content with a content id ... with an existing different content id" in the logs. 
> More details on BZ#1117813 . 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Tue Sep  2 07:26:01 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 2 Sep 2014 07:26:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3525) JTA -
 HibernateException: Unable to locate current JTA transaction
In-Reply-To: <JIRA.12547616.1406556636000@Atlassian.JIRA>
References: <JIRA.12547616.1406556636000@Atlassian.JIRA>
	<JIRA.12547616.1406556636000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12547616.1406556636000.22977.1409657161046@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNPORTAL-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997743#comment-12997743 ] 

RH Bugzilla Integration commented on GTNPORTAL-3525:
----------------------------------------------------

vramik at redhat.com changed the Status of [bug 1122138|https://bugzilla.redhat.com/show_bug.cgi?id=1122138] from ON_QA to VERIFIED

> JTA - HibernateException: Unable to locate current JTA transaction
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3525
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3525
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.2.Final
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.3.Final, 3.9.0.Final
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1122138 . Snipet from tacktrace:
> {code}
> 08:24:01,660 INFO  [org.exoplatform.services.organization.idm.UserDAOImpl] (http-vmg39.mw.lab.eng.bos.redhat.com/10.16.88.117:8080-5) Cannot obtain user: john; : org.picketlink.idm.common.exception.IdentityException: Cannot obtain Hibernate Session
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.getHibernateSession(HibernateIdentityStoreImpl.java:2798) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.getHibernateIdentityObjectType(HibernateIdentityStoreImpl.java:2850) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.getHibernateIdentityObject(HibernateIdentityStoreImpl.java:2896) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.safeGet(HibernateIdentityStoreImpl.java:2821) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.findIdentityObject(HibernateIdentityStoreImpl.java:684) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository.findIdentityObject(WrapperIdentityStoreRepository.java:171) [picketlink-idm-core-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.api.session.managers.PersistenceManagerImpl.findUser(PersistenceManagerImpl.java:426) [picketlink-idm-core-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.exoplatform.services.organization.idm.UserDAOImpl.getPopulatedUser(UserDAOImpl.java:727) [exo.portal.component.identity-3.8.4.Final-redhat-1.jar:3.8.4.Final-redhat-1]
> 	at org.exoplatform.services.organization.idm.UserDAOImpl.findUserByName(UserDAOImpl.java:294) [exo.portal.component.identity-3.8.4.Final-redhat-1.jar:3.8.4.Final-redhat-1]
> 	at org.exoplatform.web.login.FilterDisabledLoginModule.login(FilterDisabledLoginModule.java:72) [exo.portal.component.web.security-3.8.4.Final-redhat-1.jar:3.8.4.Final-redhat-1]
> ...
> Caused by: org.hibernate.HibernateException: Unable to locate current JTA transaction
> 	at org.hibernate.context.internal.JTASessionContext.currentSession(JTASessionContext.java:89)
> 	at org.hibernate.internal.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:993)
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreSessionImpl.getSessionContext(HibernateIdentityStoreSessionImpl.java:57) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.getHibernateSession(HibernateIdentityStoreImpl.java:2789) [picketlink-idm-hibernate-1.4.5.Final-redhat-1.jar:1.4.5.Final-redhat-1]
> 	... 89 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep  5 23:37:59 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Fri, 5 Sep 2014 23:37:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3538) Fix warnings during
	maven build
In-Reply-To: <JIRA.12551287.1409974622000@Atlassian.JIRA>
References: <JIRA.12551287.1409974622000@Atlassian.JIRA>
	<JIRA.12551287.1409974622454@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551287.1409974622000.35142.1409974679560@Atlassian.JIRA>

Tuyen Nguyen The created GTNPORTAL-3538:
-------------------------------------------

             Summary: Fix warnings during maven build
                 Key: GTNPORTAL-3538
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3538
             Project: GateIn Portal
          Issue Type: Bug
            Reporter: Tuyen Nguyen The
            Assignee: Tuyen Nguyen The
            Priority: Minor


We have got following warnings during maven build that could be fixed:
{code}
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for org.gatein.portal:exo.portal.packaging.tomcat.pkg:pom:3.9.0.Alpha01-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.httpcomponents:httpclient:jar -> duplicate declaration of version (?) @ line 406, column 17
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Sat Sep  6 01:11:59 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Sat, 6 Sep 2014 01:11:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3538) Fix warnings during
	maven build
In-Reply-To: <JIRA.12551287.1409974622000@Atlassian.JIRA>
References: <JIRA.12551287.1409974622000@Atlassian.JIRA>
	<JIRA.12551287.1409974622000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551287.1409974622000.35143.1409980319573@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tuyen Nguyen The updated GTNPORTAL-3538:
----------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/903


> Fix warnings during maven build
> -------------------------------
>
>                 Key: GTNPORTAL-3538
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3538
>             Project: GateIn Portal
>          Issue Type: Bug
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>
> We have got following warnings during maven build that could be fixed:
> {code}
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model for org.gatein.portal:exo.portal.packaging.tomcat.pkg:pom:3.9.0.Alpha01-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.httpcomponents:httpclient:jar -> duplicate declaration of version (?) @ line 406, column 17
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING] 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Sat Sep  6 02:40:00 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Sat, 6 Sep 2014 02:40:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3538) Fix warnings during
	maven build
In-Reply-To: <JIRA.12551287.1409974622000@Atlassian.JIRA>
References: <JIRA.12551287.1409974622000@Atlassian.JIRA>
	<JIRA.12551287.1409974622000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551287.1409974622000.35163.1409985599995@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3538:
----------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
       Resolution: Done


> Fix warnings during maven build
> -------------------------------
>
>                 Key: GTNPORTAL-3538
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3538
>             Project: GateIn Portal
>          Issue Type: Bug
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> We have got following warnings during maven build that could be fixed:
> {code}
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model for org.gatein.portal:exo.portal.packaging.tomcat.pkg:pom:3.9.0.Alpha01-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.httpcomponents:httpclient:jar -> duplicate declaration of version (?) @ line 406, column 17
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING] 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Sat Sep  6 04:13:59 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Sat, 6 Sep 2014 04:13:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3539) Do not recover IDM
 transaction if exception occurs during a search.
In-Reply-To: <JIRA.12551291.1409991197000@Atlassian.JIRA>
References: <JIRA.12551291.1409991197000@Atlassian.JIRA>
	<JIRA.12551291.1409991197620@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551291.1409991197000.35166.1409991239640@Atlassian.JIRA>

Tran Trung Thanh created GTNPORTAL-3539:
-------------------------------------------

             Summary: Do not recover IDM transaction if exception occurs during a search.
                 Key: GTNPORTAL-3539
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3539
             Project: GateIn Portal
          Issue Type: Task
    Affects Versions: 3.7.0.Final
            Reporter: Tran Trung Thanh
            Priority: Minor


If user meets an exception during a search, it is not neccessary to recover transaction.

Unit test
{code:java}
    @Test
    public void testFailDuringSearch() throws Exception {
      String USER = "test";
       createUser(USER);
       userHandler_.findUserByName(null);
       User user = userHandler_.findUserByName(USER);
       assertTrue("Found user instance ", user != null);
       userHandler_.removeUser(USER, true);
    }
{code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Sat Sep  6 04:16:59 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Sat, 6 Sep 2014 04:16:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3539) Do not recover IDM
 transaction if exception occurs during a search.
In-Reply-To: <JIRA.12551291.1409991197000@Atlassian.JIRA>
References: <JIRA.12551291.1409991197000@Atlassian.JIRA>
	<JIRA.12551291.1409991197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551291.1409991197000.35168.1409991419877@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3539:
----------------------------------
    Fix Version/s: 3.9.0.Final


> Do not recover IDM transaction if exception occurs during a search.
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3539
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3539
>             Project: GateIn Portal
>          Issue Type: Task
>    Affects Versions: 3.7.0.Final
>            Reporter: Tran Trung Thanh
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> If user meets an exception during a search, it is not neccessary to recover transaction.
> Unit test
> {code:java}
>     @Test
>     public void testFailDuringSearch() throws Exception {
>       String USER = "test";
>        createUser(USER);
>        userHandler_.findUserByName(null);
>        User user = userHandler_.findUserByName(USER);
>        assertTrue("Found user instance ", user != null);
>        userHandler_.removeUser(USER, true);
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep  8 01:06:00 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 8 Sep 2014 01:06:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3540) Number of items per
 page index is too short
In-Reply-To: <JIRA.12551308.1410152709000@Atlassian.JIRA>
References: <JIRA.12551308.1410152709000@Atlassian.JIRA>
	<JIRA.12551308.1410152709884@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551308.1410152709000.35414.1410152760044@Atlassian.JIRA>

Tuyen Nguyen The created GTNPORTAL-3540:
-------------------------------------------

             Summary: Number of items per page index is too short
                 Key: GTNPORTAL-3540
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3540
             Project: GateIn Portal
          Issue Type: Enhancement
            Reporter: Tuyen Nguyen The
            Priority: Minor
         Attachments: categories_page.png, listusers_in_group_page.png, list_membershiptype_page.png

No. items per page for category list, user list in group and membership list are 5 items per page now, It's too short.
We should display 10 item per page, it's better.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep  8 01:06:00 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 8 Sep 2014 01:06:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3540) Number of items per
 page index is too short
In-Reply-To: <JIRA.12551308.1410152709000@Atlassian.JIRA>
References: <JIRA.12551308.1410152709000@Atlassian.JIRA>
	<JIRA.12551308.1410152709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551308.1410152709000.35415.1410152760267@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tuyen Nguyen The updated GTNPORTAL-3540:
----------------------------------------
    Attachment: categories_page.png
                listusers_in_group_page.png
                list_membershiptype_page.png


> Number of items per page index is too short
> -------------------------------------------
>
>                 Key: GTNPORTAL-3540
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3540
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Tuyen Nguyen The
>            Priority: Minor
>         Attachments: categories_page.png, listusers_in_group_page.png, list_membershiptype_page.png
>
>
> No. items per page for category list, user list in group and membership list are 5 items per page now, It's too short.
> We should display 10 item per page, it's better.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep  8 01:06:00 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 8 Sep 2014 01:06:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3540) Number of items per
 page index is too short
In-Reply-To: <JIRA.12551308.1410152709000@Atlassian.JIRA>
References: <JIRA.12551308.1410152709000@Atlassian.JIRA>
	<JIRA.12551308.1410152709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551308.1410152709000.35416.1410152760326@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tuyen Nguyen The reassigned GTNPORTAL-3540:
-------------------------------------------

    Assignee: Tuyen Nguyen The


> Number of items per page index is too short
> -------------------------------------------
>
>                 Key: GTNPORTAL-3540
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3540
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>         Attachments: categories_page.png, listusers_in_group_page.png, list_membershiptype_page.png
>
>
> No. items per page for category list, user list in group and membership list are 5 items per page now, It's too short.
> We should display 10 item per page, it's better.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep  8 01:29:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 8 Sep 2014 01:29:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to
 customize login validation and accounts expiration
In-Reply-To: <JIRA.12533491.1393506528000@Atlassian.JIRA>
References: <JIRA.12533491.1393506528000@Atlassian.JIRA>
	<JIRA.12533491.1393506528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533491.1393506528000.35424.1410154199657@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999693#comment-12999693 ] 

RH Bugzilla Integration commented on GTNPORTAL-3402:
----------------------------------------------------

Jared MORGAN <jmorgan at redhat.com> changed the Status of [bug 1072150|https://bugzilla.redhat.com/show_bug.cgi?id=1072150] from ASSIGNED to MODIFIED

>  Allow customers to customize login validation and accounts expiration
> ----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3402
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3402
>             Project: GateIn Portal
>          Issue Type: Feature Request
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.8.0.Beta01
>
>
> Allow customers to add custom password rules to their GateIn installations.
> We've had a discussion about the possibilities, and it seems that the best for now would be something as follows:
> 1) Adapt/extend the current UserConfigurableValidator, which allows the usage of min/max/regex constraints for values based on values from a configuration file, for instance:
> gatein.validators.mycompanypasspolicy.length.min=5
> gatein.validators.mycompanypasspolicy.length.max=50
> gatein.validators.mycompanypasspolicy.regexp=...
> 2) Extend the User Interface to allow the administrator to enter the name of the configuration entry related to the password policy (mycompanypasspolicy , in this case). 
> (originally requested via Bugzilla #973835)



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep  8 03:38:00 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 8 Sep 2014 03:38:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3540) Number of items per
 page index is too short
In-Reply-To: <JIRA.12551308.1410152709000@Atlassian.JIRA>
References: <JIRA.12551308.1410152709000@Atlassian.JIRA>
	<JIRA.12551308.1410152709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551308.1410152709000.35622.1410161880207@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tuyen Nguyen The updated GTNPORTAL-3540:
----------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/904


> Number of items per page index is too short
> -------------------------------------------
>
>                 Key: GTNPORTAL-3540
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3540
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>         Attachments: categories_page.png, listusers_in_group_page.png, list_membershiptype_page.png
>
>
> No. items per page for category list, user list in group and membership list are 5 items per page now, It's too short.
> We should display 10 item per page, it's better.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Sep  9 05:55:59 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 9 Sep 2014 05:55:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3541) JGroups and
 Infinispan adjusments for performance
In-Reply-To: <JIRA.12551445.1410256554000@Atlassian.JIRA>
References: <JIRA.12551445.1410256554000@Atlassian.JIRA>
	<JIRA.12551445.1410256554411@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551445.1410256554000.39010.1410256559601@Atlassian.JIRA>

Lucas Ponce created GTNPORTAL-3541:
--------------------------------------

             Summary: JGroups and Infinispan adjusments for performance
                 Key: GTNPORTAL-3541
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3541
             Project: GateIn Portal
          Issue Type: Enhancement
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Sep  9 05:56:59 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 9 Sep 2014 05:56:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3541) JGroups and
 Infinispan adjustments for performance
In-Reply-To: <JIRA.12551445.1410256554000@Atlassian.JIRA>
References: <JIRA.12551445.1410256554000@Atlassian.JIRA>
	<JIRA.12551445.1410256554000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551445.1410256554000.39011.1410256619558@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Ponce updated GTNPORTAL-3541:
-----------------------------------
    Summary: JGroups and Infinispan adjustments for performance  (was: JGroups and Infinispan adjusments for performance)


> JGroups and Infinispan adjustments for performance
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3541
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3541
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Sep  9 23:45:19 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Tue, 9 Sep 2014 23:45:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3535) Can not upload
 filename containe special character
In-Reply-To: <JIRA.12549990.1408697828000@Atlassian.JIRA>
References: <JIRA.12549990.1408697828000@Atlassian.JIRA>
	<JIRA.12549990.1408697828000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12549990.1408697828000.230.1410320719973@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3535:
----------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
       Resolution: Done


> Can not upload filename containe special character
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3535
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3535
>             Project: GateIn Portal
>          Issue Type: Bug
>         Environment: Window
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>         Attachments: exception.txt
>
>
> Step to reproduce:
>     - Deploy [webuibasedsamples|https://github.com/gatein/gatein-portal/tree/master/testsuite/webuibasedsamples] and run gatein on window environment
>     - Use FF on ubuntu environment to access gatein
>     - Login with root
>     - Add webUISample and try to upload a file with filename contain special charater (for example :$$%:$%^$:)
>     => It will show an empty file and there is exception in console (see attachment). The upload is failure.
>   We should validate filename before really store upload file.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Sep 10 00:22:19 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 10 Sep 2014 00:22:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3540) Number of items per
 page index is too short
In-Reply-To: <JIRA.12551308.1410152709000@Atlassian.JIRA>
References: <JIRA.12551308.1410152709000@Atlassian.JIRA>
	<JIRA.12551308.1410152709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551308.1410152709000.232.1410322939252@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3540:
----------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
       Resolution: Done


> Number of items per page index is too short
> -------------------------------------------
>
>                 Key: GTNPORTAL-3540
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3540
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>         Attachments: categories_page.png, listusers_in_group_page.png, list_membershiptype_page.png
>
>
> No. items per page for category list, user list in group and membership list are 5 items per page now, It's too short.
> We should display 10 item per page, it's better.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Sep 10 02:34:19 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 10 Sep 2014 02:34:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3259) Configurable default
 view mode in page editor
In-Reply-To: <JIRA.12500019.1378366720000@Atlassian.JIRA>
References: <JIRA.12500019.1378366720000@Atlassian.JIRA>
	<JIRA.12500019.1378366720000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500019.1378366720000.303.1410330859113@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNPORTAL-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000652#comment-13000652 ] 

RH Bugzilla Integration commented on GTNPORTAL-3259:
----------------------------------------------------

Aakanksha <aasingh at redhat.com> changed the Status of [bug 1072177|https://bugzilla.redhat.com/show_bug.cgi?id=1072177] from NEW to ASSIGNED

> Configurable default view mode in page editor
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3259
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3259
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.7.0.Final
>
>
> Add new configuration options in configuration.properties:
> gatein.portal.pageeditor.defaultview=block (default) | preview
> gatein.portal.layouteditor.defaultview=block (default) | preview
> When the option is set to "block" it should behave as of today.
> When the option is set to "preview" the page or layout editor should directly show the editor as if the user clicked on the "Switch View Mode" button.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Sep 10 04:10:19 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 10 Sep 2014 04:10:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3530) User with special
 UTF-8 character in display name appears not correctly in GateIn using MS
 SQL Server 2008
In-Reply-To: <JIRA.12548550.1407222610000@Atlassian.JIRA>
References: <JIRA.12548550.1407222610000@Atlassian.JIRA>
	<JIRA.12548550.1407222610000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12548550.1407222610000.559.1410336619418@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3530:
----------------------------------
    Fix Version/s: 3.9.0.Final


> User with special UTF-8 character in display name appears not correctly in GateIn using MS SQL Server 2008
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3530
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3530
>             Project: GateIn Portal
>          Issue Type: Bug
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.9.0.Final
>
>         Attachments: displayname_nok.png, displayname_ok.png
>
>
> Steps to reproduce:
> - start GateIn using MS SQL Server 2008, instead of HSQL.
> - login as root
> - Click on display name to open user profile dialog
> - Change user info with first name is "Nguy?n", last name is "Th? Tuy?n", and display name is "Nguy?n Th? Tuy?n"
> - Click save and now "Nguy?n Th? Tuy?n" is appeared correctly in display name field on the top-right (See [^displayname_ok.png])
> - Restart Gatein and login with root again
> Problem: Display name appears not correctly. (see [^displayname_nok.png])



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Wed Sep 10 04:42:19 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 10 Sep 2014 04:42:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3536) Localization of
 tooltip and confirmation button when enable/disable user is not correct
In-Reply-To: <JIRA.12550307.1409106325000@Atlassian.JIRA>
References: <JIRA.12550307.1409106325000@Atlassian.JIRA>
	<JIRA.12550307.1409106325000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550307.1409106325000.642.1410338539261@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3536:
----------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
       Resolution: Done


> Localization of tooltip and confirmation button when enable/disable user is not correct
> ---------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3536
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3536
>             Project: GateIn Portal
>          Issue Type: Bug
>    Affects Versions: 3.7.0.Final
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.9.0.Final
>
>         Attachments: confirmation_in_english.png, confirmation_in_french.png, enable_disable_tooltip.png
>
>
> Case to reproduce:
> - Start gatein then login with user root
> - Switch language to French
> - Goto User and Group management portlet
> - Hover on icon enable/disable
> ==> Tooltip message is always in English => NOK
> - Click to disable user root
> - Confirmation popup is show in French => OK
> - Change language to English
> - Click to disable user root
> - Confirmation popup is show, the message is in English but button is still in French => NOK



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Sep 10 06:05:20 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 10 Sep 2014 06:05:20 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3534) GateIn build is
 broken because of test failures
In-Reply-To: <JIRA.12549486.1408350254000@Atlassian.JIRA>
References: <JIRA.12549486.1408350254000@Atlassian.JIRA>
	<JIRA.12549486.1408350254000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12549486.1408350254000.985.1410343520233@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trong Tran updated GTNPORTAL-3534:
----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> GateIn build is broken because of test failures
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3534
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3534
>             Project: GateIn Portal
>          Issue Type: Bug
>            Reporter: Trong Tran
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> It's weird that tests are passed in my local build BUT it failed on Jenkins build https://ci.exoplatform.org/job/gatein-portal-master-ci/3351/testReport/
> {code}
> Test Result (2 failures / +2) :
> org.exoplatform.portal.resource.TestSkinService.testInitializing
> org.exoplatform.portal.resource.TestSkinServiceInDevelopingMode.testInitializing
> {code}
> Maybe the problem is related to the order of testcases execution.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Sep 10 11:55:19 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Wed, 10 Sep 2014 11:55:19 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3541) JGroups and
 Infinispan adjustments for performance
In-Reply-To: <JIRA.12551445.1410256554000@Atlassian.JIRA>
References: <JIRA.12551445.1410256554000@Atlassian.JIRA>
	<JIRA.12551445.1410256554000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551445.1410256554000.2531.1410364519519@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Ponce updated GTNPORTAL-3541:
-----------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/905


> JGroups and Infinispan adjustments for performance
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3541
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3541
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep 15 08:27:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 15 Sep 2014 08:27:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-372) Exception appears in log
 while using WSRP portlets with PortletBridge
In-Reply-To: <JIRA.12533248.1393339019000@Atlassian.JIRA>
References: <JIRA.12533248.1393339019000@Atlassian.JIRA>
	<JIRA.12533248.1393339019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533248.1393339019000.1563.1410784022827@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002332#comment-13002332 ] 

RH Bugzilla Integration commented on GTNWSRP-372:
-------------------------------------------------

Petr Mensik <pmensik at redhat.com> changed the Status of [bug 1063918|https://bugzilla.redhat.com/show_bug.cgi?id=1063918] from ASSIGNED to VERIFIED

>  Exception appears in log while using WSRP portlets with PortletBridge
> ----------------------------------------------------------------------
>
>                 Key: GTNWSRP-372
>                 URL: https://issues.jboss.org/browse/GTNWSRP-372
>             Project: GateIn WSRP
>          Issue Type: Feature Request
>    Affects Versions: 2.2.11.Final
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 2.2.12.Final
>
>
> From Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1063918 : 
> The following exception will appear in server log after portlet initialization on the page. It has no affect on functionality, everything is working just fine and this exception is thrown only once. 
> How to reproduce
> 1. Enable WSRP
> 2. Deploy RichFaces Showcase portlet
> 3. Add it to page as remote portlet
> 4. See the exception at first access to Showcase
> I enclose the Showcase portlet and .txt with exception log.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 03:43:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:43:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-369) Portlet sessions are not
 properly scoped on consumer
In-Reply-To: <JIRA.12495932.1373296490000@Atlassian.JIRA>
References: <JIRA.12495932.1373296490000@Atlassian.JIRA>
	<JIRA.12495932.1373296490000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12495932.1373296490000.31058.1411717382344@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006341#comment-13006341 ] 

RH Bugzilla Integration commented on GTNWSRP-369:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 981585|https://bugzilla.redhat.com/show_bug.cgi?id=981585] from NEW to CLOSED

> 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
>          Components: Consumer
>    Affects Versions: 2.0.1-GA, 2.2.9.Final
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 2.0.2-GA, 2.2.11.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:49:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:49:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-353) Reading properties for a
 portlet that contains non-portlet.xml declared properties leads to NPE
In-Reply-To: <JIRA.12488331.1364642918000@Atlassian.JIRA>
References: <JIRA.12488331.1364642918000@Atlassian.JIRA>
	<JIRA.12488331.1364642918000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12488331.1364642918000.31076.1411717742534@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006345#comment-13006345 ] 

RH Bugzilla Integration commented on GTNWSRP-353:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 947367|https://bugzilla.redhat.com/show_bug.cgi?id=947367] from NEW to CLOSED

> Reading properties for a portlet that contains non-portlet.xml declared properties leads to NPE
> -----------------------------------------------------------------------------------------------
>
>                 Key: GTNWSRP-353
>                 URL: https://issues.jboss.org/browse/GTNWSRP-353
>             Project: GateIn WSRP
>          Issue Type: Bug
>          Components: Producer
>    Affects Versions: 2.1.7-GA, 2.2.2.Final
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 2.1.8-GA, 2.2.3.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:51:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:51:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-368) escapeXml feature is
	ignored in wsrp.
In-Reply-To: <JIRA.12495824.1373046113000@Atlassian.JIRA>
References: <JIRA.12495824.1373046113000@Atlassian.JIRA>
	<JIRA.12495824.1373046113000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12495824.1373046113000.31082.1411717862254@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006347#comment-13006347 ] 

RH Bugzilla Integration commented on GTNWSRP-368:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 981746|https://bugzilla.redhat.com/show_bug.cgi?id=981746] from ASSIGNED to CLOSED

> escapeXml feature is ignored in wsrp.
> -------------------------------------
>
>                 Key: GTNWSRP-368
>                 URL: https://issues.jboss.org/browse/GTNWSRP-368
>             Project: GateIn WSRP
>          Issue Type: Bug
>          Components: Producer
>    Affects Versions: 2.0.1-GA, 2.2.9.Final
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 2.0.2-GA, 2.2.11.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:52:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:52:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-286) Add support for
 extensions and associated hooks to process them
In-Reply-To: <JIRA.12467249.1337852800000@Atlassian.JIRA>
References: <JIRA.12467249.1337852800000@Atlassian.JIRA>
	<JIRA.12467249.1337852800000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12467249.1337852800000.31092.1411717923584@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006349#comment-13006349 ] 

RH Bugzilla Integration commented on GTNWSRP-286:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 794108|https://bugzilla.redhat.com/show_bug.cgi?id=794108] from ASSIGNED to CLOSED

> Add support for extensions and associated hooks to process them
> ---------------------------------------------------------------
>
>                 Key: GTNWSRP-286
>                 URL: https://issues.jboss.org/browse/GTNWSRP-286
>             Project: GateIn WSRP
>          Issue Type: Feature Request
>          Components: Consumer, Producer
>    Affects Versions: 2.1.5-GA
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 2.2.0-Beta03, 2.2.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:54:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:54:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-302) Replication of producer
 configuration doesn't happen after failover
In-Reply-To: <JIRA.12472934.1345707737000@Atlassian.JIRA>
References: <JIRA.12472934.1345707737000@Atlassian.JIRA>
	<JIRA.12472934.1345707737000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12472934.1345707737000.31114.1411718042733@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006353#comment-13006353 ] 

RH Bugzilla Integration commented on GTNWSRP-302:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 851060|https://bugzilla.redhat.com/show_bug.cgi?id=851060] from MODIFIED to CLOSED

> Replication of producer configuration doesn't happen after failover
> -------------------------------------------------------------------
>
>                 Key: GTNWSRP-302
>                 URL: https://issues.jboss.org/browse/GTNWSRP-302
>             Project: GateIn WSRP
>          Issue Type: Sub-task
>          Components: Admin GUI, Producer
>         Environment: EPP 5.2.2 CR01 (2 nodes), loadbalancer with mod_jk
>            Reporter: Michal Vanco
>            Assignee: Chris Laprun
>             Fix For: 2.2.0.CR03
>
>
> Scenario:
>  - 2 EPP nodes access through loadbalancer
>  - go to loadbalancer url (verify which node is used - from sessionID suffix)
>  - go to wsrp admin - producer config tab
>  - uncheck some checkbox
>  - stop active node
>  - go to wsrp admin again -> producer configuration settings wasn't replicated



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:54:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:54:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-298)
 NotSerializableException: org.oasis.wsrp.v2.SessionContext when using bea
 portal
In-Reply-To: <JIRA.12472579.1345064208000@Atlassian.JIRA>
References: <JIRA.12472579.1345064208000@Atlassian.JIRA>
	<JIRA.12472579.1345064208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12472579.1345064208000.31117.1411718042960@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006354#comment-13006354 ] 

RH Bugzilla Integration commented on GTNWSRP-298:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 848550|https://bugzilla.redhat.com/show_bug.cgi?id=848550] from MODIFIED to CLOSED

> NotSerializableException: org.oasis.wsrp.v2.SessionContext when using bea portal
> --------------------------------------------------------------------------------
>
>                 Key: GTNWSRP-298
>                 URL: https://issues.jboss.org/browse/GTNWSRP-298
>             Project: GateIn WSRP
>          Issue Type: Sub-task
>    Affects Versions: 2.1.6-GA
>         Environment: EPP 5.2.1 GA, EPP 5.2.2 CR01, "all" configuration
>            Reporter: Michal Vanco
>            Assignee: Chris Laprun
>             Fix For: 2.1.8-GA, 2.2.1.CR01
>
>         Attachments: wsrp-bea-nse.txt
>
>
> There is a NSE error at interoperability with bea portal.
> I have simplest portlet deployed on bea portal and error is thrown when remote portlet is rendered on page.
> It happens only at cluster configuration, running portal with "-c all" parameter is enough to reproduce.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:55:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:55:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-258) WSRP producer as 2-node
 cluster with loadbalancer - registration issue
In-Reply-To: <JIRA.12450884.1320073262000@Atlassian.JIRA>
References: <JIRA.12450884.1320073262000@Atlassian.JIRA>
	<JIRA.12450884.1320073262000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12450884.1320073262000.31121.1411718103030@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006355#comment-13006355 ] 

RH Bugzilla Integration commented on GTNWSRP-258:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 845535|https://bugzilla.redhat.com/show_bug.cgi?id=845535] from MODIFIED to CLOSED

> WSRP producer as 2-node cluster with loadbalancer - registration issue
> ----------------------------------------------------------------------
>
>                 Key: GTNWSRP-258
>                 URL: https://issues.jboss.org/browse/GTNWSRP-258
>             Project: GateIn WSRP
>          Issue Type: Sub-task
>          Components: Producer
>    Affects Versions: 2.1.0-Beta08
>         Environment: EPP5.2.0 ER05
>            Reporter: Michal Vanco
>            Assignee: Chris Laprun
>             Fix For: 2.1.8-GA
>
>
> Imagine/configure the environment: producer as 2-node cluster with loadbalancer + 1 consumer.
> You register new consumer at consumer node with WSDL from loadbalancer. Loadbalancer points to one of nodes (let's wait node1) and registration is done with node1.
> btw. WSDL on loadbalancer directly points to one of nodes (there is node1 or node2 at all URLs)
> You put some remote portlet on page (communication is between consumer+node1 through loadbalancer), do failover - stop node1.
> At this moment you would expect that remote portlet is still available, but it's not because consumer is registered with node1.
> It means that after refresh of page with remote portlet -> portlet is not displayed.
> You have to go to WSRP admin and refresh consumer (with WSDL of loadbalancer), now the question:
>  - what is expected at this moment? Registration on second node? (this should be somehow distributed from killed node)
>  - when you have 2 cluster nodes started on one machine - you can't continue and refresh won't be successfull (Could not transmit message, Can not connect http client invoker after 1 attempt(s)) - this should be related to unique consumer name registration on producer
>  - when you have 2 nodes started on different machines - you should be able to refresh, what happens with registration? Is there new registration with second node? What happens when node1 is back? (2 different registrations for same consumer?)
> At this moment I've tested 2 nodes at same machine - at this scenario you can't continue using remote portlet and refresh consumer after failover.
> I can provide some more details based on reply of expected behavior.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 03:55:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 26 Sep 2014 03:55:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-346) Multipart requests are
 not handeled if there is no attached file
In-Reply-To: <JIRA.12482529.1358149825000@Atlassian.JIRA>
References: <JIRA.12482529.1358149825000@Atlassian.JIRA>
	<JIRA.12482529.1358149825000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12482529.1358149825000.31124.1411718103329@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/GTNWSRP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006356#comment-13006356 ] 

RH Bugzilla Integration commented on GTNWSRP-346:
-------------------------------------------------

Thomas Heute <theute at redhat.com> changed the Status of [bug 894975|https://bugzilla.redhat.com/show_bug.cgi?id=894975] from MODIFIED to CLOSED

> Multipart requests are not handeled if there is no attached file
> ----------------------------------------------------------------
>
>                 Key: GTNWSRP-346
>                 URL: https://issues.jboss.org/browse/GTNWSRP-346
>             Project: GateIn WSRP
>          Issue Type: Bug
>    Affects Versions: 2.1.7-GA, 2.2.2.Final
>            Reporter: Martin Weiler
>            Assignee: Chris Laprun
>             Fix For: 2.1.8-GA, 2.2.3.Final
>
>
> We have html multipart form in a wsrp portlet:
> {code:xml}
> <form enctype="multipart/form-data" method="post" ...
> {code}
> with an optional input field for an attachment:
> {code:xml}
> <input type="file" value="org.springframework.web.multipart.commons.CommonsMultipartFile at f3af1" name="attachement">
> {code}
> The "org.gatein.wsrp.consumer.handlers.ActionHandler" handles the request correctly and tries to create a UploadContext with the help of the WSRPTypeFactory:
> {code}
>  UploadContext uploadContext = WSRPTypeFactory.createUploadContext(contentType, baos.toByteArray());
> {code}
> The problem is, that the createUploadContext throws an exception if the byte array has a content lenght of 0 and so the rest of the parameteres are not handled correctly:
> {code}
>    public static UploadContext createUploadContext(String mimeType, byte[] uploadData)
>    {
>       ParameterValidation.throwIllegalArgExceptionIfNullOrEmpty(mimeType, "MIME Type", "UploadContext");
>       if (uploadData == null || uploadData.length == 0)
>       {
>          throw new IllegalArgumentException("Must pass non-null, non-empty upload data");
>       }
>  
>       UploadContext uploadContext = new UploadContext();
>       uploadContext.setMimeType(mimeType);
>       uploadContext.setUploadData(uploadData);
>       return uploadContext;
>    }
> {code}
> So currently the post request with WSRP works only if really a file is attached. Without WSRP it runs with and without an attached file.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Sep 26 06:47:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:47:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3542) Update to PicketLink
	2.5.3
In-Reply-To: <JIRA.12553432.1411728401000@Atlassian.JIRA>
References: <JIRA.12553432.1411728401000@Atlassian.JIRA>
	<JIRA.12553432.1411728401169@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553432.1411728401000.31552.1411728422281@Atlassian.JIRA>

Juraci Paix?o Kr?hling created GTNPORTAL-3542:
-------------------------------------------------

             Summary: Update to PicketLink 2.5.3
                 Key: GTNPORTAL-3542
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3542
             Project: GateIn Portal
          Issue Type: Task
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling


Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 06:48:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:48:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3542) Update to PicketLink
	2.5.3
In-Reply-To: <JIRA.12553432.1411728401000@Atlassian.JIRA>
References: <JIRA.12553432.1411728401000@Atlassian.JIRA>
	<JIRA.12553432.1411728401000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553432.1411728401000.31554.1411728482258@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3542:
----------------------------------------------
    Component/s: SSO


> Update to PicketLink 2.5.3
> --------------------------
>
>                 Key: GTNPORTAL-3542
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3542
>             Project: GateIn Portal
>          Issue Type: Task
>          Components: SSO
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 06:49:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:49:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3542) Update gatein-sso to
	PicketLink 2.5.3
In-Reply-To: <JIRA.12553432.1411728401000@Atlassian.JIRA>
References: <JIRA.12553432.1411728401000@Atlassian.JIRA>
	<JIRA.12553432.1411728401000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553432.1411728401000.31556.1411728542488@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3542:
----------------------------------------------
    Summary: Update gatein-sso to PicketLink 2.5.3  (was: Update to PicketLink 2.5.3)


> Update gatein-sso to PicketLink 2.5.3
> -------------------------------------
>
>                 Key: GTNPORTAL-3542
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3542
>             Project: GateIn Portal
>          Issue Type: Task
>          Components: SSO
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 06:49:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:49:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal
 to PicketLink 2.5.3
In-Reply-To: <JIRA.12553433.1411728508000@Atlassian.JIRA>
References: <JIRA.12553433.1411728508000@Atlassian.JIRA>
	<JIRA.12553433.1411728508896@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553433.1411728508000.31558.1411728542591@Atlassian.JIRA>

Juraci Paix?o Kr?hling created GTNPORTAL-3543:
-------------------------------------------------

             Summary: Update gatein-portal to PicketLink 2.5.3
                 Key: GTNPORTAL-3543
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3543
             Project: GateIn Portal
          Issue Type: Task
          Components: SSO
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling


Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 06:49:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:49:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal
 to PicketLink 2.5.3
In-Reply-To: <JIRA.12553433.1411728508000@Atlassian.JIRA>
References: <JIRA.12553433.1411728508000@Atlassian.JIRA>
	<JIRA.12553433.1411728508000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553433.1411728508000.31560.1411728542705@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3543:
----------------------------------------------
    Component/s:     (was: SSO)


> Update gatein-portal to PicketLink 2.5.3
> ----------------------------------------
>
>                 Key: GTNPORTAL-3543
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3543
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 06:50:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 06:50:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal
 to PicketLink 2.5.3
In-Reply-To: <JIRA.12553433.1411728508000@Atlassian.JIRA>
References: <JIRA.12553433.1411728508000@Atlassian.JIRA>
	<JIRA.12553433.1411728508000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553433.1411728508000.31562.1411728602274@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3543:
----------------------------------------------
    Description: Update the dependency on PicketLink to version 2.5.3, consuming the new version of gatein-sso.   (was: Update the dependency on PicketLink to version 2.5.3. )


> Update gatein-portal to PicketLink 2.5.3
> ----------------------------------------
>
>                 Key: GTNPORTAL-3543
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3543
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3, consuming the new version of gatein-sso. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 08:35:02 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 08:35:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3542) Update gatein-sso to
	PicketLink 2.5.3
In-Reply-To: <JIRA.12553432.1411728401000@Atlassian.JIRA>
References: <JIRA.12553432.1411728401000@Atlassian.JIRA>
	<JIRA.12553432.1411728401000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553432.1411728401000.31843.1411734902701@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling resolved GTNPORTAL-3542.
-----------------------------------------------
    Resolution: Done


> Update gatein-sso to PicketLink 2.5.3
> -------------------------------------
>
>                 Key: GTNPORTAL-3542
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3542
>             Project: GateIn Portal
>          Issue Type: Task
>          Components: SSO
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Fri Sep 26 08:57:03 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Fri, 26 Sep 2014 08:57:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal
 to PicketLink 2.5.3
In-Reply-To: <JIRA.12553433.1411728508000@Atlassian.JIRA>
References: <JIRA.12553433.1411728508000@Atlassian.JIRA>
	<JIRA.12553433.1411728508000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553433.1411728508000.31909.1411736223282@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3543:
----------------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/906


> Update gatein-portal to PicketLink 2.5.3
> ----------------------------------------
>
>                 Key: GTNPORTAL-3543
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3543
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> Update the dependency on PicketLink to version 2.5.3, consuming the new version of gatein-sso. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep 29 05:00:02 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 05:00:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3541) JGroups and
 Infinispan adjustments for performance
In-Reply-To: <JIRA.12551445.1410256554000@Atlassian.JIRA>
References: <JIRA.12551445.1410256554000@Atlassian.JIRA>
	<JIRA.12551445.1410256554000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12551445.1410256554000.34396.1411981202811@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3541:
------------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.7.Final
       Resolution: Done


> JGroups and Infinispan adjustments for performance
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3541
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3541
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.7.Final
>
>
> There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep 29 05:00:03 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 05:00:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3544) JGroups and
 Infinispan adjustments for performance in GateIn 3.9
In-Reply-To: <JIRA.12553554.1411981187000@Atlassian.JIRA>
References: <JIRA.12553554.1411981187000@Atlassian.JIRA>
	<JIRA.12553554.1411981187392@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553554.1411981187000.34399.1411981203100@Atlassian.JIRA>

Peter Palaga created GTNPORTAL-3544:
---------------------------------------

             Summary: JGroups and Infinispan adjustments for performance in GateIn 3.9
                 Key: GTNPORTAL-3544
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3544
             Project: GateIn Portal
          Issue Type: Enhancement
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce
             Fix For: 3.8.7.Final


There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep 29 05:02:02 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 05:02:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3544) JGroups and
 Infinispan adjustments for performance in GateIn 3.9
In-Reply-To: <JIRA.12553554.1411981187000@Atlassian.JIRA>
References: <JIRA.12553554.1411981187000@Atlassian.JIRA>
	<JIRA.12553554.1411981187000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553554.1411981187000.34413.1411981322553@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3544:
------------------------------------
    Description: 
GTNPORTAL-3541 solved the issue in GateIn 3.8.x. This one is there for the present master, a.k.a. GateIn 3.9.x.

There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.

  was:There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



> JGroups and Infinispan adjustments for performance in GateIn 3.9
> ----------------------------------------------------------------
>
>                 Key: GTNPORTAL-3544
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3544
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.7.Final
>
>
> GTNPORTAL-3541 solved the issue in GateIn 3.8.x. This one is there for the present master, a.k.a. GateIn 3.9.x.
> There are some areas in ISPN and JGroups where configuration can be improved for a better performance in large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Sep 29 06:08:02 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 06:08:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3524) Custom portals cannot
 use remote portlets
In-Reply-To: <JIRA.12547342.1406189982000@Atlassian.JIRA>
References: <JIRA.12547342.1406189982000@Atlassian.JIRA>
	<JIRA.12547342.1406189982000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12547342.1406189982000.34495.1411985282882@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3524:
------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/891


> Custom portals cannot use remote portlets
> -----------------------------------------
>
>                 Key: GTNPORTAL-3524
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3524
>             Project: GateIn Portal
>          Issue Type: Bug
>          Components: WSRP integration
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.9.0.Final
>
>
> Before GTNPORTAL-3291, the FederatingPortletInvoker was shared among all contexts, meaning that a PortletInvoker responsible for local portlets was the same on "portal" and on "sample-portal". Similarly, a WSRP PortletInvoker was also shared.
> This caused the problems described in 3291 and 2700 and a fix was issued in that each context would have it's own FederatingPortletInvoker .
> With local portlets, each context having its own FederatingPortletInvoker is not a big issue, because the query is made at the JCR level for which portlets are available. 
> With remote portlets, it's a problem, as WSRP registers the consumers only once, for the "portal" context. This means that the consumer invokers are not available for non-"portal" contexts. With this, a call from the context "sample-portal" to the FederatingPortletInvoker, requesting portlet "selfv2.bla" would fail, as there's no way to find this portlet on this particular invoker tree. 
> While the producers are also started for the "portal" context, the fact that producers have their own servlet context makes it immune from this bug, as all HTTP calls to the producers reaches a context whose invoker *knows* about the requested portlet. In other words: producers are not affected by this bug.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep 29 06:08:03 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 06:08:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3524) Custom portals cannot
 use remote portlets
In-Reply-To: <JIRA.12547342.1406189982000@Atlassian.JIRA>
References: <JIRA.12547342.1406189982000@Atlassian.JIRA>
	<JIRA.12547342.1406189982000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12547342.1406189982000.34497.1411985283009@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3524:
------------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
       Resolution: Done


> Custom portals cannot use remote portlets
> -----------------------------------------
>
>                 Key: GTNPORTAL-3524
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3524
>             Project: GateIn Portal
>          Issue Type: Bug
>          Components: WSRP integration
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.9.0.Final
>
>
> Before GTNPORTAL-3291, the FederatingPortletInvoker was shared among all contexts, meaning that a PortletInvoker responsible for local portlets was the same on "portal" and on "sample-portal". Similarly, a WSRP PortletInvoker was also shared.
> This caused the problems described in 3291 and 2700 and a fix was issued in that each context would have it's own FederatingPortletInvoker .
> With local portlets, each context having its own FederatingPortletInvoker is not a big issue, because the query is made at the JCR level for which portlets are available. 
> With remote portlets, it's a problem, as WSRP registers the consumers only once, for the "portal" context. This means that the consumer invokers are not available for non-"portal" contexts. With this, a call from the context "sample-portal" to the FederatingPortletInvoker, requesting portlet "selfv2.bla" would fail, as there's no way to find this portlet on this particular invoker tree. 
> While the producers are also started for the "portal" context, the fact that producers have their own servlet context makes it immune from this bug, as all HTTP calls to the producers reaches a context whose invoker *knows* about the requested portlet. In other words: producers are not affected by this bug.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep 29 06:10:02 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 06:10:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal
 to PicketLink 2.5.3
In-Reply-To: <JIRA.12553433.1411728508000@Atlassian.JIRA>
References: <JIRA.12553433.1411728508000@Atlassian.JIRA>
	<JIRA.12553433.1411728508000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553433.1411728508000.34499.1411985402267@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3543:
------------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.9.0.Final
                   3.8.8.Final
       Resolution: Done


> Update gatein-portal to PicketLink 2.5.3
> ----------------------------------------
>
>                 Key: GTNPORTAL-3543
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3543
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.9.0.Final, 3.8.8.Final
>
>
> Update the dependency on PicketLink to version 2.5.3, consuming the new version of gatein-sso. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Mon Sep 29 06:27:02 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 29 Sep 2014 06:27:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to
	version 3.10.1
In-Reply-To: <JIRA.12553559.1411986370000@Atlassian.JIRA>
References: <JIRA.12553559.1411986370000@Atlassian.JIRA>
	<JIRA.12553559.1411986370045@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553559.1411986370000.34508.1411986422271@Atlassian.JIRA>

Peter Palaga created GTNPORTAL-3545:
---------------------------------------

             Summary: Upgrade Apache POI to version 3.10.1
                 Key: GTNPORTAL-3545
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3545
             Project: GateIn Portal
          Issue Type: Task
            Reporter: Peter Palaga
            Assignee: Peter Palaga


CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Sep 30 06:11:03 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Tue, 30 Sep 2014 06:11:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3546) Update
	cas-client-core on gatein-sso
In-Reply-To: <JIRA.12553655.1412071828000@Atlassian.JIRA>
References: <JIRA.12553655.1412071828000@Atlassian.JIRA>
	<JIRA.12553655.1412071828883@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553655.1412071828000.37112.1412071863049@Atlassian.JIRA>

Juraci Paix?o Kr?hling created GTNPORTAL-3546:
-------------------------------------------------

             Summary: Update cas-client-core on gatein-sso
                 Key: GTNPORTAL-3546
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3546
             Project: GateIn Portal
          Issue Type: Enhancement
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling






--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Tue Sep 30 06:11:03 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Tue, 30 Sep 2014 06:11:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3547) Update
 cas-client-core on gatein-portal
In-Reply-To: <JIRA.12553656.1412071846000@Atlassian.JIRA>
References: <JIRA.12553656.1412071846000@Atlassian.JIRA>
	<JIRA.12553656.1412071846299@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553656.1412071846000.37114.1412071863262@Atlassian.JIRA>

Juraci Paix?o Kr?hling created GTNPORTAL-3547:
-------------------------------------------------

             Summary: Update cas-client-core on gatein-portal
                 Key: GTNPORTAL-3547
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3547
             Project: GateIn Portal
          Issue Type: Enhancement
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling






--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Tue Sep 30 06:59:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 30 Sep 2014 06:59:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3547) Update
 cas-client-core on gatein-portal
In-Reply-To: <JIRA.12553656.1412071846000@Atlassian.JIRA>
References: <JIRA.12553656.1412071846000@Atlassian.JIRA>
	<JIRA.12553656.1412071846000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553656.1412071846000.37248.1412074743246@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated GTNPORTAL-3547:
-----------------------------------------------
        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131355


> Update cas-client-core on gatein-portal
> ---------------------------------------
>
>                 Key: GTNPORTAL-3547
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3547
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Tue Sep 30 07:00:06 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Tue, 30 Sep 2014 07:00:06 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3547) Update
 cas-client-core on gatein-portal
In-Reply-To: <JIRA.12553656.1412071846000@Atlassian.JIRA>
References: <JIRA.12553656.1412071846000@Atlassian.JIRA>
	<JIRA.12553656.1412071846000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553656.1412071846000.37259.1412074806500@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraci Paix?o Kr?hling updated GTNPORTAL-3547:
----------------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/907


> Update cas-client-core on gatein-portal
> ---------------------------------------
>
>                 Key: GTNPORTAL-3547
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3547
>             Project: GateIn Portal
>          Issue Type: Enhancement
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


From issues at jboss.org  Tue Sep 30 09:10:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 30 Sep 2014 09:10:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to
	version 3.10.1
In-Reply-To: <JIRA.12553559.1411986370000@Atlassian.JIRA>
References: <JIRA.12553559.1411986370000@Atlassian.JIRA>
	<JIRA.12553559.1411986370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553559.1411986370000.37920.1412082603323@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated GTNPORTAL-3545:
-----------------------------------------------
        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1138168


> Upgrade Apache POI to version 3.10.1
> ------------------------------------
>
>                 Key: GTNPORTAL-3545
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3545
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Sep 30 09:10:04 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Tue, 30 Sep 2014 09:10:04 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to
	version 3.10.1
In-Reply-To: <JIRA.12553559.1411986370000@Atlassian.JIRA>
References: <JIRA.12553559.1411986370000@Atlassian.JIRA>
	<JIRA.12553559.1411986370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12553559.1411986370000.37926.1412082604159@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/GTNPORTAL-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga updated GTNPORTAL-3545:
------------------------------------
    Description: CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138168  (was: CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166)


> Upgrade Apache POI to version 3.10.1
> ------------------------------------
>
>                 Key: GTNPORTAL-3545
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3545
>             Project: GateIn Portal
>          Issue Type: Task
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138168



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)