From issues at jboss.org  Thu May  1 02:51:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Thu, 1 May 2014 02:51:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3465) Update version in
	"Try GateIn 3.7..."
In-Reply-To: <JIRA.12539601.1398927038686@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539601.1398927038686@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539601.1398927038686.1265.1398927116203@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3465:
---------------------------------------

             Summary: Update version in "Try GateIn 3.7..."
                 Key: GTNPORTAL-3465
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3465
             Project: GateIn Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


"Try GateIn 3.7 with one of these user accounts:" in HomePagePortlet shoudl say "Try GateIn 3.8 with one of these user accounts:"



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 02:59:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Thu, 1 May 2014 02:59:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3465) Update version in
	"Try GateIn 3.7..."
In-Reply-To: <JIRA.12539601.1398927038000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539601.1398927038000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539601.1398927038000.1268.1398927596222@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3465.
-------------------------------------

    Fix Version/s: 3.8.0.Final
       Resolution: Done


This was fixed by the fix for GTNPORTAL-3456 https://github.com/gatein/gatein-portal/commit/ac0cba0bcd6170d7029c8e9ceba054f14d7add8e#diff-e05ee18a12da7577e4d259c896875ca4R21

> Update version in "Try GateIn 3.7..."
> -------------------------------------
>
>                 Key: GTNPORTAL-3465
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3465
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> "Try GateIn 3.7 with one of these user accounts:" in HomePagePortlet shoudl say "Try GateIn 3.8 with one of these user accounts:"



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 10:11:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Thu, 1 May 2014 10:11:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3466) label
 for="publicMode" in UIListPermissionSelector.gtmpl not unique
In-Reply-To: <JIRA.12539614.1398953510984@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539614.1398953510984@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539614.1398953510984.1457.1398953516599@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3466:
---------------------------------------

             Summary: label for="publicMode" in UIListPermissionSelector.gtmpl not unique
                 Key: GTNPORTAL-3466
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3466
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga


{{publicMode}} used as {{label for}} and chekbox {{id}}  in UIListPermissionSelector.gtmpl is not unique. There are situations where several UIListPermissionSelector are rendered on a single page. An unwanted consequence of that is that clicking on a non-first {{<label>}} on a page changes the value of the first checkbox with {{id="publicMode"}} rather than the one that is visually next to the clicked {{<label>}}.

Steps to reproduce:

(1) login as root
(2) toolbox > Sites > Manage Sites
(3) Edit any portal's config > Permissions
(4) Ensure Access is set to Everyone
(5) Switch to Move Apps tab
(6) Click on "Everyone" text (do not click on the checkbox itself)
Not OK: the checkbox in Move Apps tab stayed unchanged
Not OK: the checkbox in Access tab got inactive
Expected: the checkbox in Move Apps changes and checkbox in Access tab stays unchanged.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 05:43:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 2 May 2014 05:43:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3467) Add navigation node
 properties to gatein_objects XSD
In-Reply-To: <JIRA.12539683.1399023727567@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539683.1399023727567@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539683.1399023727567.2286.1399023836276@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3467:
---------------------------------------

             Summary: Add navigation node properties to gatein_objects XSD
                 Key: GTNPORTAL-3467
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3467
             Project: GateIn Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


Properties like the following should be possible on navigation nodes:
{code:xml}
<properties>
         <entry key="externalURI">http://google.com</entry>
         <entry key="openInNewWindow">true</entry>
</properties>
{code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 07:59:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 2 May 2014 07:59:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951278@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951278@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951278.2706.1399031996337@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3468:
---------------------------------------

             Summary: Node's external link values are not persisted after exporting site
                 Key: GTNPORTAL-3468
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


Description of problem:
According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
When you create external link for a node in navigation.xml, after import/export it is not persisted. 

Steps to Reproduce:
1. Export site
2. Enter some property values into navigation.xml inside <node> element:
{code:xml}
<properties> 
    <entry key="externalURI">http://google.com</entry> 
    <entry key="openInNewWindow">true</entry> 
</properties> 
{code}
3. Import site into portal
4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 08:03:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 2 May 2014 08:03:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951000.2762.1399032237097@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3468:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1091403


> Node's external link values are not persisted after exporting site
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3468
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Description of problem:
> According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
> When you create external link for a node in navigation.xml, after import/export it is not persisted. 
> Steps to Reproduce:
> 1. Export site
> 2. Enter some property values into navigation.xml inside <node> element:
> {code:xml}
> <properties> 
>     <entry key="externalURI">http://google.com</entry> 
>     <entry key="openInNewWindow">true</entry> 
> </properties> 
> {code}
> 3. Import site into portal
> 4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 08:03:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 2 May 2014 08:03:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3459) Permissions Move Apps,
 Move Containers are not inherited to a newly created page
In-Reply-To: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538979.1398343067000.2778.1399032238922@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3459:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1090875


> Permissions Move Apps, Move Containers are not inherited to a newly created page 
> ---------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3459
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3459
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1090875
> When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. 
> Steps to reproduce:
> 1. Create new portal site, set some permissions
> 2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 12:13:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 2 May 2014 12:13:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211690@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211690@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211690.3523.1399047236607@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3469:
---------------------------------------

             Summary: PortalSetupCommand does not ensure that initialpassword is written on a new line
                 Key: GTNPORTAL-3469
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


Steps to reproduce:
(1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
(2) Ensure that the last key value pair is not terminated with a new line character
(3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
Not OK: The {{configuration.properties}} file ends with 
{code:plain}
# Logged user keep alive
gatein.webui.keepalive.enabled=true
gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
{code}

Expected: 
{code:plain}
# Logged user keep alive
gatein.webui.keepalive.enabled=true
gatein.webui.keepalive.interval=60000
gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
{code}




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sat May  3 07:41:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Sat, 3 May 2014 07:41:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226724@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226724@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226724.3999.1399117316245@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3470:
---------------------------------------

             Summary: Make permission defaults in page creation forms consistent
                 Key: GTNPORTAL-3470
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.

The page creation forms for which this applies:
I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page

For each of them, the defaults should be set as follows: 

(1) For portal pages the access and edit permissions should be taken from the parent site.

(2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.

(3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.

In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sat May  3 08:47:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Sat, 3 May 2014 08:47:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226000.4001.1399121276223@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3470:
------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/850


> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sat May  3 15:03:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Sat, 3 May 2014 15:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-33) Localize aux tags for WCM
	Editor portlet
In-Reply-To: <JIRA.12537508.1396944656000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537508.1396944656000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537508.1396944656000.4055.1399143836216@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce closed GTNWCM-33.
-----------------------------

    Fix Version/s: 2.x
       Resolution: Done


Support for english and spanish.
Also code is prepared to add new languages adding new *.properties files.

> Localize aux tags for WCM Editor portlet
> ----------------------------------------
>
>                 Key: GTNWCM-33
>                 URL: https://issues.jboss.org/browse/GTNWCM-33
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 2.x
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sat May  3 18:37:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Sat, 3 May 2014 18:37:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3459) Permissions Move Apps,
 Move Containers are not inherited to a newly created page
In-Reply-To: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538979.1398343067000.4077.1399156676241@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3459:
------------------------------------

        Status: Resolved  (was: Pull Request Sent)
    Resolution: Won't Fix


This cannot be fixed as suggested in the description because there already are defaults applied from the selected page template. I have created GTNPORTAL-3470 to fix some small inconsistencies in all page creation forms.

> Permissions Move Apps, Move Containers are not inherited to a newly created page 
> ---------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3459
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3459
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1090875
> When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. 
> Steps to reproduce:
> 1. Create new portal site, set some permissions
> 2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 03:56:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 03:56:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226000.4566.1399276617214@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3470:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094154


> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 03:58:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 03:58:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3459) Permissions Move Apps,
 Move Containers are not inherited to a newly created page
In-Reply-To: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538979.1398343067000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538979.1398343067000.4568.1399276736253@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1090875|https://bugzilla.redhat.com/show_bug.cgi?id=1090875] from ASSIGNED to CLOSED

> Permissions Move Apps, Move Containers are not inherited to a newly created page 
> ---------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3459
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3459
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1090875
> When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. 
> Steps to reproduce:
> 1. Create new portal site, set some permissions
> 2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:00:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:00:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3456) Update copyright text
 to use 2014 year
In-Reply-To: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538928.1398272542000.4578.1399276857469@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1089944|https://bugzilla.redhat.com/show_bug.cgi?id=1089944] from POST to MODIFIED

> Update copyright text to use 2014 year
> --------------------------------------
>
>                 Key: GTNPORTAL-3456
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3456
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:04:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:04:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3467) Add navigation node
 properties to gatein_objects XSD
In-Reply-To: <JIRA.12539683.1399023727000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539683.1399023727000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539683.1399023727000.4584.1399277096764@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3467.
-------------------------------------

    Fix Version/s: 3.8.0.Final
       Resolution: Done


Merged to master https://github.com/gatein/gatein-portal/commit/d5d3e47147e1d70b68e13d6a4f5652e938d84289 and the new XSD was published http://www.gatein.org/xml/ns/gatein_objects_1_7

> Add navigation node properties to gatein_objects XSD
> ----------------------------------------------------
>
>                 Key: GTNPORTAL-3467
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3467
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Properties like the following should be possible on navigation nodes:
> {code:xml}
> <properties>
>          <entry key="externalURI">http://google.com</entry>
>          <entry key="openInNewWindow">true</entry>
> </properties>
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:04:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:04:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951000.4590.1399277097184@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3468.
-------------------------------------

    Fix Version/s: 3.8.0.Final
       Resolution: Done


Merged to master 
https://github.com/gatein/gatein-portal/commit/86687984fb2c92b2adc3eebf171ca6a46e79e134

> Node's external link values are not persisted after exporting site
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3468
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Description of problem:
> According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
> When you create external link for a node in navigation.xml, after import/export it is not persisted. 
> Steps to Reproduce:
> 1. Export site
> 2. Enter some property values into navigation.xml inside <node> element:
> {code:xml}
> <properties> 
>     <entry key="externalURI">http://google.com</entry> 
>     <entry key="openInNewWindow">true</entry> 
> </properties> 
> {code}
> 3. Import site into portal
> 4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:06:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:06:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951000.4592.1399277216430@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1091403|https://bugzilla.redhat.com/show_bug.cgi?id=1091403] from ASSIGNED to MODIFIED

> Node's external link values are not persisted after exporting site
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3468
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Description of problem:
> According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
> When you create external link for a node in navigation.xml, after import/export it is not persisted. 
> Steps to Reproduce:
> 1. Export site
> 2. Enter some property values into navigation.xml inside <node> element:
> {code:xml}
> <properties> 
>     <entry key="externalURI">http://google.com</entry> 
>     <entry key="openInNewWindow">true</entry> 
> </properties> 
> {code}
> 3. Import site into portal
> 4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:06:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:06:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211000.4598.1399277216807@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3469.
-------------------------------------

    Fix Version/s: 3.8.0.Final
       Resolution: Done


The fix was merged in master https://github.com/gatein/gatein-portal/commit/1c722a1ee8c9bb8e12a62e9ca8fd434184a5bc57

> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3469
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
> Not OK: The {{configuration.properties}} file ends with 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected: 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:10:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:10:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211000.4606.1399277459252@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3469:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094163


> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3469
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
> Not OK: The {{configuration.properties}} file ends with 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected: 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:10:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:10:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211000.4608.1399277459358@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1094163|https://bugzilla.redhat.com/show_bug.cgi?id=1094163] from NEW to MODIFIED

> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3469
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
> Not OK: The {{configuration.properties}} file ends with 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected: 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:12:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:12:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3460) Move Containers
 permission is not shown when using different languages
In-Reply-To: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539213.1398680460000.4614.1399277576685@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3460:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.0.Final
       Resolution: Done


The fix was merged to master after minor reformulations in Czech, German an Russian languages.

> Move Containers permission is not shown when using different languages
> ----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3460
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3460
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Some i18n languages have long texts makes overflow some UI components in fixed layout.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:14:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:14:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3460) Move Containers
 permission is not shown when using different languages
In-Reply-To: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539213.1398680460000.4623.1399277696542@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1091319|https://bugzilla.redhat.com/show_bug.cgi?id=1091319] from POST to MODIFIED

> Move Containers permission is not shown when using different languages
> ----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3460
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3460
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Some i18n languages have long texts makes overflow some UI components in fixed layout.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:16:58 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:16:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3461) Update SSO dependency
	to 1.4.1.Final
In-Reply-To: <JIRA.12539227.1398689791000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539227.1398689791000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539227.1398689791000.4629.1399277818212@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3461:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.0.Final
                       (was: 3.8.1.Final)
       Resolution: Done


> Update SSO dependency to 1.4.1.Final
> ------------------------------------
>
>                 Key: GTNPORTAL-3461
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3461
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.0.Final
>
>
> gatein-sso 1.4.1.Final has fix for https://bugzilla.redhat.com/show_bug.cgi?id=1088042



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:18:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:18:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3462) Missing
 javax.servlet.api dependency in org.jasig.cas.client module
In-Reply-To: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539228.1398689872000.4644.1399277937671@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1062155|https://bugzilla.redhat.com/show_bug.cgi?id=1062155] from ASSIGNED to MODIFIED

> Missing javax.servlet.api dependency in org.jasig.cas.client module
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3462
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3462
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.0.Final
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1062155



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:18:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:18:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3462) Missing
 javax.servlet.api dependency in org.jasig.cas.client module
In-Reply-To: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539228.1398689872000.4647.1399277937903@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3462:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.0.Final
                       (was: 3.8.1.Final)
       Resolution: Done


> Missing javax.servlet.api dependency in org.jasig.cas.client module
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3462
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3462
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.0.Final
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1062155



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:18:58 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:18:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3463) Update GateIn to WSRP
	2.3.1.Final
In-Reply-To: <JIRA.12539401.1398847217000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539401.1398847217000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539401.1398847217000.4649.1399277938119@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3463:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.0.Final
       Resolution: Done


> Update GateIn to WSRP 2.3.1.Final
> ---------------------------------
>
>                 Key: GTNPORTAL-3463
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3463
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.8.0.Final
>
>
> A new release for WSRP was made, thus requiring a change in GateIn Portal to consume this new version. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May  5 04:20:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:20:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons
	look like inverse
In-Reply-To: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534579.1394465062000.4652.1399278056816@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1076175|https://bugzilla.redhat.com/show_bug.cgi?id=1076175] from POST to MODIFIED

> Disable users icons look like inverse
> -------------------------------------
>
>                 Key: GTNPORTAL-3417
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3417
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: 3.8.0.Beta01-SNAPSHOT
>            Reporter: Vlastislav Ramik
>            Assignee: Lucas Ponce
>              Labels: RHJP62
>             Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:20:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:20:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons
	look like inverse
In-Reply-To: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534579.1394465062000.4659.1399278057450@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3417:
------------------------------------

        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Disable users icons look like inverse
> -------------------------------------
>
>                 Key: GTNPORTAL-3417
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3417
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: 3.8.0.Beta01-SNAPSHOT
>            Reporter: Vlastislav Ramik
>            Assignee: Lucas Ponce
>              Labels: RHJP62
>             Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:20:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 5 May 2014 04:20:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226000.4663.1399278057781@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3470:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.0.Final
       Resolution: Done


> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:20:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:20:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226000.4661.1399278057627@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1094154|https://bugzilla.redhat.com/show_bug.cgi?id=1094154] from NEW to MODIFIED

> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:48:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 04:48:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3454) Remove native AMD
 modules from requireJs config
In-Reply-To: <JIRA.12538878.1398255088000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538878.1398255088000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538878.1398255088000.4826.1399279737901@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1090470|https://bugzilla.redhat.com/show_bug.cgi?id=1090470] from POST to MODIFIED

> Remove native AMD modules from requireJs config
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3454
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3454
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> RequireJs config is a json structure renderead inline in the HTML markup of every page returned by the portal. The recent "Native AMD Support" feature has brought the possibility to work with large third-party javascript frameworks such as Dojo containing thousands of JavaScript modules. The present implementation adds an entry for every native AMD module into RequireJs config. With a dojo portlet deployed, this causes an overhead of more than 400KB per page.
> Steps to Reproduce:
> 1. Compile and deploy the dojo portlet application from https://github.com/ppalaga/dojo-portlet
> 2. Import applications
> 3. Inspect the source of any portal page, e.g. /portal/classic/home
> 4. Locate the line starting with
>   var require =
> Actual results: All dojo resources are there in the json structure assigned to the require variable.
> Expected results: No resources coming from Dojo should be there.
> Additional info: Not having the resources coming from Dojo in requireJS config is technically possible as the native AMD modules are implicitly SHARED and the baseUrl is set properly in the config.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:08:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3451) Infinispan transport
 clusterName property not properly defined
In-Reply-To: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538760.1398172565000.4880.1399280936750@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1085927|https://bugzilla.redhat.com/show_bug.cgi?id=1085927] from POST to MODIFIED

> Infinispan transport clusterName property not properly defined
> --------------------------------------------------------------
>
>                 Key: GTNPORTAL-3451
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3451
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> clusterName attribute is not well defined for infinispan transport defined in HA configurations.
> This bug shows followings warnings:
> [...]
> 14:47:59,283 WARN  [org.infinispan.util.StringPropertyReplacer] (MSC service thread 1-2) ISPN000003: Property infinispan-cluster-name could not be replaced as intended!
> [...]
> And this bug is root cause for other cascading errors in cluster setup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:08:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3449) Adding new node in
 group navigation doesn't work
In-Reply-To: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538736.1398157303000.4882.1399280936872@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1089460|https://bugzilla.redhat.com/show_bug.cgi?id=1089460] from POST to MODIFIED

> Adding new node in group navigation doesn't work
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3449
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3449
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:08:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:08:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3452) Changing permissions
 in ApplicationRegistry causes error
In-Reply-To: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538778.1398181740000.4884.1399280937010@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1089965|https://bugzilla.redhat.com/show_bug.cgi?id=1089965] from POST to MODIFIED

> Changing permissions in ApplicationRegistry causes error
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-3452
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3452
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Changing permission of any portlet in Application Registry will cause "java.lang.Exception: Invalid Application Id: [web_slash_IFramePortlet]". 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:08:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:08:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3453) domain.xml demo with
 default and full profiles
In-Reply-To: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538873.1398251581000.4886.1399280937145@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1090419|https://bugzilla.redhat.com/show_bug.cgi?id=1090419] from POST to MODIFIED

> domain.xml demo with default and full profiles
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3453
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3453
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> demo-domain-setup.sh is a demo script to run gatein in domain mode.
> server-groups defined in domain.xml use full and full-ha profiles.
> For a better demo, these profiles should be default and full, to avoid to run a separate process with a tcp H2 database.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:10:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:10:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3455) Select page layout
 doesn't select default item.
In-Reply-To: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538926.1398271160000.4896.1399281056512@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1090491|https://bugzilla.redhat.com/show_bug.cgi?id=1090491] from POST to MODIFIED

> Select page layout doesn't select default item.
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3455
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3455
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> In step 2 of UIPageCreationWizard select page layout wizard doesn't select by default first element of each sublist.
> For example, if we change to row templates and we go to step 3, page layout is empty template instead two rows template.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 07:08:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Mon, 5 May 2014 07:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3471) impossible to edit a
	disable user
In-Reply-To: <JIRA.12539827.1399288129249@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539827.1399288129249@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539827.1399288129249.5109.1399288136352@jira02.app.mwc.hst.phx2.redhat.com>

Vu Viet Phuong created GTNPORTAL-3471:
-----------------------------------------

             Summary: impossible to edit a disable user
                 Key: GTNPORTAL-3471
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3471
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.8.0.Beta01, 3.7.0.Final
            Reporter: Vu Viet Phuong
            Assignee: Vu Viet Phuong


1- Login as root
2- Go to user management page
3- Choose the tab "User Management"

-> A disabled user is displayed
4- click on the button "Edit"

Actual Result:
A warning pop up is displayed "This user is disabled. You have to enable this user for editing. "

Expected Result:
User should be able to edit disabled user



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 07:20:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Mon, 5 May 2014 07:20:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3471) impossible to edit a
	disable user
In-Reply-To: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539827.1399288129000.5114.1399288856382@jira02.app.mwc.hst.phx2.redhat.com>


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

Vu Viet Phuong updated GTNPORTAL-3471:
--------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/851


> impossible to edit a disable user
> ---------------------------------
>
>                 Key: GTNPORTAL-3471
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3471
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>
> 1- Login as root
> 2- Go to user management page
> 3- Choose the tab "User Management"
> -> A disabled user is displayed
> 4- click on the button "Edit"
> Actual Result:
> A warning pop up is displayed "This user is disabled. You have to enable this user for editing. "
> Expected Result:
> User should be able to edit disabled user



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 10:02:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 10:02:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3389) URL query parameters
 are not propagated when going through the authentication process
In-Reply-To: <JIRA.12530575.1390986646000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530575.1390986646000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530575.1390986646000.5558.1399298576829@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from ON_QA to VERIFIED

> URL query parameters are not propagated when going through the authentication process
> -------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3389
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3389
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.8.Final
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.5.9.Final, 3.7.0.Final
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Steps to reproduce
> - Goto url http://localhost:8080/portal/g/:platform:administrators/administration/registry?test=abcd
> --> it redirect to login page, login as root --> Query parameters are lost.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 10:02:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 10:02:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters
 are lost in the authentication process with LegacyRequestHandler
In-Reply-To: <JIRA.12534241.1394090177000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534241.1394090177000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534241.1394090177000.5561.1399298577048@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from ON_QA to VERIFIED

> URL query parameters are lost in the authentication process with LegacyRequestHandler
> -------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3415
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3415
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.8.Final
>            Reporter: Martin Weiler
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Beta01
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Steps to reproduce
> - Goto url http://localhost:8080/portal/private/classic/home/restricted?myparameter=LEGACY
> --> it redirect to login page, login as root --> Query parameters are lost.
> Note: Without the LegacyRequestHandler - http://localhost:8080/portal/classic/home/restricted?myparameter=TEST - the parameters are preserved with the fix for GTNPORTAL-3389



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 23:06:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Mon, 5 May 2014 23:06:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3471) impossible to edit a
	disable user
In-Reply-To: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539827.1399288129000.6691.1399345616444@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3471:
----------------------------------

    Fix Version/s: 3.7.1.Final


> impossible to edit a disable user
> ---------------------------------
>
>                 Key: GTNPORTAL-3471
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3471
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.7.1.Final
>
>
> 1- Login as root
> 2- Go to user management page
> 3- Choose the tab "User Management"
> -> A disabled user is displayed
> 4- click on the button "Edit"
> Actual Result:
> A warning pop up is displayed "This user is disabled. You have to enable this user for editing. "
> Expected Result:
> User should be able to edit disabled user



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 23:10:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Mon, 5 May 2014 23:10:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3471) impossible to edit a
	disable user
In-Reply-To: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539827.1399288129000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539827.1399288129000.6693.1399345856414@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3471:
----------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.1.Final
       Resolution: Done


> impossible to edit a disable user
> ---------------------------------
>
>                 Key: GTNPORTAL-3471
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3471
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.7.1.Final, 3.8.1.Final
>
>
> 1- Login as root
> 2- Go to user management page
> 3- Choose the tab "User Management"
> -> A disabled user is displayed
> 4- click on the button "Edit"
> Actual Result:
> A warning pop up is displayed "This user is disabled. You have to enable this user for editing. "
> Expected Result:
> User should be able to edit disabled user



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 03:46:57 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Tue, 6 May 2014 03:46:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3458) Use infinite TTL for
 TemplateService caching by default
In-Reply-To: <JIRA.12538974.1398338631000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538974.1398338631000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538974.1398338631000.6820.1399362417979@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3458:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.8.0.Final)


> Use infinite TTL for TemplateService caching by default
> -------------------------------------------------------
>
>                 Key: GTNPORTAL-3458
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3458
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> I think it makes sense to use infinite TTL for default TemplateService caching config as the number of templates are fixed and they never change in production ideally



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 03:46:58 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Tue, 6 May 2014 03:46:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3458) Use infinite TTL for
 TemplateService caching by default
In-Reply-To: <JIRA.12538974.1398338631000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538974.1398338631000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538974.1398338631000.6822.1399362418093@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3458:
----------------------------------

        Status: Resolved  (was: Pull Request Sent)
      Assignee: Trong Tran
    Resolution: Done


> Use infinite TTL for TemplateService caching by default
> -------------------------------------------------------
>
>                 Key: GTNPORTAL-3458
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3458
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>            Assignee: Trong Tran
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> I think it makes sense to use infinite TTL for default TemplateService caching config as the number of templates are fixed and they never change in production ideally



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 08:41:58 2014
From: issues at jboss.org (Anurag Debnath (JIRA))
Date: Tue, 6 May 2014 08:41:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-376) Different Portlet
 preference for remote portlets added on the same page
In-Reply-To: <JIRA.12539955.1399380095648@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539955.1399380095648@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539955.1399380095648.7812.1399380118140@jira02.app.mwc.hst.phx2.redhat.com>

Anurag Debnath created GTNWSRP-376:
--------------------------------------

             Summary: Different Portlet preference for remote portlets added on the same page
                 Key: GTNWSRP-376
                 URL: https://issues.jboss.org/browse/GTNWSRP-376
             Project: GateIn WSRP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.11.Final
         Environment: Tested with :

JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5)  and 
GateIn-3.8.0.Beta01
            Reporter: Anurag Debnath
            Assignee: Juraci Paix?o Kr?hling


When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well.

Ideally, portlets should get their own preference/s.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May  6 08:45:59 2014
From: issues at jboss.org (Anurag Debnath (JIRA))
Date: Tue, 6 May 2014 08:45:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-376) Different Portlet
 preference for remote portlets added on the same page
In-Reply-To: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539955.1399380095000.7818.1399380359043@jira02.app.mwc.hst.phx2.redhat.com>


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

Anurag Debnath updated GTNWSRP-376:
-----------------------------------

    Attachment: PortletPreferencesPortlet.war.zip


One can use the attached portlet example to replicate the issue following the steps mentioned in the "Steps to Reproduce" section
(Restricted to jira-users group)
> Different Portlet preference for remote portlets added on the same page
> -----------------------------------------------------------------------
>
>                 Key: GTNWSRP-376
>                 URL: https://issues.jboss.org/browse/GTNWSRP-376
>             Project: GateIn WSRP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.11.Final
>         Environment: Tested with :
> JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5)  and 
> GateIn-3.8.0.Beta01
>            Reporter: Anurag Debnath
>            Assignee: Juraci Paix?o Kr?hling
>         Attachments: PortletPreferencesPortlet.war.zip
>
>
> When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well.
> Ideally, portlets should get their own preference/s.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May  6 09:11:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 6 May 2014 09:11:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-376) Different Portlet
 preference for remote portlets added on the same page
In-Reply-To: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539955.1399380095000.7910.1399381916746@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNWSRP-376:
--------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094772


> Different Portlet preference for remote portlets added on the same page
> -----------------------------------------------------------------------
>
>                 Key: GTNWSRP-376
>                 URL: https://issues.jboss.org/browse/GTNWSRP-376
>             Project: GateIn WSRP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.11.Final
>         Environment: Tested with :
> JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5)  and 
> GateIn-3.8.0.Beta01
>            Reporter: Anurag Debnath
>            Assignee: Juraci Paix?o Kr?hling
>         Attachments: PortletPreferencesPortlet.war.zip
>
>
> When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well.
> Ideally, portlets should get their own preference/s.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May  7 00:42:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 00:42:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704765@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704765@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704765.9582.1399437776459@jira02.app.mwc.hst.phx2.redhat.com>

Trong Tran created GTNPORTAL-3472:
-------------------------------------

             Summary: NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
                 Key: GTNPORTAL-3472
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Trong Tran


We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:

{code}
[jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
java.lang.NullPointerException
	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)
{code}

*MBeans which seem to cause this problem :*
- exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=*,service=SessionRegistry
- exo:portal=portal,repository=\*,workspace=\*,service=Cache
- exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
- exo:portal=portal,service=cache,name=*

*How to reproduce :*
- unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
- copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
- start your portal and watch the starup logs




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 00:42:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 00:42:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.9584.1399437776601@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3472:
----------------------------------

    Affects Version/s: 3.7.0.Final


> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>
> We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
> - copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 00:42:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 00:42:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.9586.1399437776740@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3472:
----------------------------------

    Fix Version/s: 3.9.0.Final


> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>             Fix For: 3.9.0.Final
>
>
> We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
> - copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 00:54:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 00:54:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.9590.1399438496420@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3472:
----------------------------------

    Attachment: jmxtrans-addon.war


> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>             Fix For: 3.9.0.Final
>
>         Attachments: jmxtrans-addon.war
>
>
> We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
> - copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 04:48:57 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Wed, 7 May 2014 04:48:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3473) Warning message for
 disable user with autologin option is not displayed
In-Reply-To: <JIRA.12540063.1399452520698@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540063.1399452520698@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540063.1399452520698.9925.1399452537124@jira02.app.mwc.hst.phx2.redhat.com>

Vu Viet Phuong created GTNPORTAL-3473:
-----------------------------------------

             Summary: Warning message for disable user with autologin option is not displayed
                 Key: GTNPORTAL-3473
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3473
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.8.0.Beta01, 3.7.0.Final
            Reporter: Vu Viet Phuong
            Assignee: Vu Viet Phuong


1- Login to GateIn with enable user A
2- Check the "Remember My login"
-> The user is logged in
3- Login as an admin
4- Disable the user A
-> The user A is disabled
5- Refresh the User A session

Actual Result
- The Login screen is displayed-> OK
- The user is not able to login-> OK
- No error message is displayed-> NOK

Expected Result:
- The error message on the login page should be displayed



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 04:54:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Wed, 7 May 2014 04:54:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3473) Warning message for
 disable user with autologin option is not displayed
In-Reply-To: <JIRA.12540063.1399452520000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540063.1399452520000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540063.1399452520000.9952.1399452896430@jira02.app.mwc.hst.phx2.redhat.com>


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

Vu Viet Phuong updated GTNPORTAL-3473:
--------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/852


> Warning message for disable user with autologin option is not displayed
> -----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3473
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3473
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>
> 1- Login to GateIn with enable user A
> 2- Check the "Remember My login"
> -> The user is logged in
> 3- Login as an admin
> 4- Disable the user A
> -> The user A is disabled
> 5- Refresh the User A session
> Actual Result
> - The Login screen is displayed-> OK
> - The user is not able to login-> OK
> - No error message is displayed-> NOK
> Expected Result:
> - The error message on the login page should be displayed



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:04:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Wed, 7 May 2014 05:04:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3473) Warning message for
 disable user with autologin option is not displayed
In-Reply-To: <JIRA.12540063.1399452520000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540063.1399452520000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540063.1399452520000.10009.1399453496428@jira02.app.mwc.hst.phx2.redhat.com>


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

Vu Viet Phuong commented on GTNPORTAL-3473:
-------------------------------------------

We need to wait for this issue https://jira.exoplatform.org/browse/KER-286
There is an issue in eXo Kernel: the PortalContainerContext#getRequestDispatcher method doesn't handle query string in the path, this should be improved

> Warning message for disable user with autologin option is not displayed
> -----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3473
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3473
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>
> 1- Login to GateIn with enable user A
> 2- Check the "Remember My login"
> -> The user is logged in
> 3- Login as an admin
> 4- Disable the user A
> -> The user A is disabled
> 5- Refresh the User A session
> Actual Result
> - The Login screen is displayed-> OK
> - The user is not able to login-> OK
> - No error message is displayed-> NOK
> Expected Result:
> - The error message on the login page should be displayed



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:56:58 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:56:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3366) [IE8,
 IE9] Can not rename Dashboard tab if name contains accent chars
In-Reply-To: <JIRA.12529443.1389757902000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529443.1389757902000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529443.1389757902000.10175.1399456618627@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3366:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> [IE8, IE9] Can not rename Dashboard tab if name contains accent chars
> ---------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3366
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3366
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.8.Final
>            Reporter: Tran Trung Thanh
>             Fix For: 3.5.10.Final, 3.9.0.Final
>
>
> Steps to reproduce:
> - Login
> - Create a Dashboard page
> - Go to that page, create a new tab of which name contains accent chars (i.e. s? m?i kh?o d?i)
> - Edit name of that tab by deleting some chars in the name (i.e.: s? m?i)
> - Hit Enter
> >>> Result: can not rename



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May  7 05:56:59 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:56:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3365) Exception swallow in
 UserDaoImpl.persistUserInfo()
In-Reply-To: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529293.1389667726000.10181.1399456619231@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3365:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3365
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3365
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.6.3.Final
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.6.4.Final, 3.9.0.Final
>
>   Original Estimate: 4 hours
>          Time Spent: 6 hours
>  Remaining Estimate: 0 minutes
>
> Under "{{org.exoplatform.services.organization.idm}}, 
> focus on : 
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
>    {
>       orgService.flush();
>       AttributesManager am = session.getAttributesManager();
>       ArrayList attributes = new ArrayList();
>       /* ... */
>       if (user.getPassword() != null)
>       {
>          if (orgService.getConfiguration().isPasswordAsAttribute())
>          {
>             attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
>          }
>          else
>          {
>             try
>             {
>                am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
>             }
>             catch (IdentityException e)
>             {
>                log.info("Cannot update password: " + user.getUserName() + "; ", e);
>             }
>          }
>       }
>       Attribute[] attrs = new Attribute[attributes.size()];
>       attrs = (Attribute[])attributes.toArray(attrs);
>       try
>       {
>          am.updateAttributes(user.getUserName(), attrs);
>       }
>       catch (IdentityException e)
>       {
>          log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
>       }
>    } 
> {code} 
>  
> The method {{saveUser(User, boolean) _throws Exception_}} 
> calls 
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}. 
>  
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}: 
> * first time in the password level
> * second time when updating all of the attributes. 
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:56:59 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:56:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3297) Finish and publish
	gatein_objects_1_6
In-Reply-To: <JIRA.12525655.1384934507000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525655.1384934507000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525655.1384934507000.10183.1399456619374@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3297:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Finish and publish gatein_objects_1_6
> -------------------------------------
>
>                 Key: GTNPORTAL-3297
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3297
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:56:59 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:56:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3283) Eliminate the Warning
 "JBAS018204: Clustering not supported,
 falling back to non-clustered session manager"
In-Reply-To: <JIRA.12517993.1383642281000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12517993.1383642281000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12517993.1383642281000.10187.1399456619773@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3283:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Eliminate the Warning "JBAS018204: Clustering not supported, falling back to non-clustered session manager"
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3283
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3283
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Packaging
>            Reporter: Peter Palaga
>            Assignee: Marko Strukelj
>             Fix For: 3.9.0.Final
>
>
> There are two occurences of this warning in GateIn startup log on JBoss
> {code}
> 09:24:30,563 WARN  [org.jboss.web] (MSC service thread 1-2) JBAS018204: Clustering not supported, falling back to non-clustered session manager
> 09:24:30,566 WARN  [org.jboss.web] (MSC service thread 1-3) JBAS018204: Clustering not supported, falling back to non-clustered session manager
> 0
> {code}
> These warnings should be eliminated, if possible, as there should be no warnings during startup of an out of the box GateIn instance.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:00 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3282) Eliminate the "using
 a private module org.apache.cxf:main" warning on JBoss startup
In-Reply-To: <JIRA.12517992.1383641370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12517992.1383641370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12517992.1383641370000.10191.1399456620024@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3282:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Eliminate the "using a private module org.apache.cxf:main" warning on JBoss startup
> -----------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3282
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3282
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: WSRP integration
>            Reporter: Peter Palaga
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.9.0.Final
>
>
> There are several warnings like this in GateIn startup log on JBoss:
> {code}
> 09:24:27,528 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.extension-war.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
> 09:24:27,551 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-admin-gui.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
> 09:24:27,556 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-producer.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
> 09:24:27,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear.wsrp-producer.war" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
> 09:24:28,561 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.gatein-wsrp-integration.ear" is using a private module ("org.apache.cxf:main") which may be changed or removed in future versions without notice.
> {code}
> Searching for "org.apache.cxf" in GateIn source tree shows occurences in   {{org.gatein.wsrp.integration}} {{module.xml}}: https://github.com/gatein/gatein-portal/blob/master/packaging/jboss-as7/modules/src/main/resources/modules/org/gatein/wsrp/integration/main/module.xml#L49
> These warning should be eliminated if possible as there should be no warnings in an out of the box GateIn installation.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May  7 05:57:00 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3273) It restores all
 pre-defined configuration when re-creating a site config with the same name
In-Reply-To: <JIRA.12503230.1381920313000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503230.1381920313000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503230.1381920313000.10193.1399456620136@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3273:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> It restores all pre-defined configuration when re-creating a site config with the same name
> -------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3273
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3273
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.6.Final, 3.6.1.Final
>            Reporter: Trong Tran
>             Fix For: 3.9.0.Final
>
>
> Steps to reproduce:
> - Login with root
> - Edit the home page layout to add the Organization Porltet
> - In Organization portlet, go to delete the pre-defined group /organization/management/executive-board. You will notice that it also deletes all data (navigation nodes, pages) belonging to that group
> - Then re-create a group with the same name under /organization/management/.
> ===> Now you will see that all pre-defined data is restored as the first initializing time.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:00 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3267) MOP import resource
In-Reply-To: <JIRA.12500886.1379490565000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500886.1379490565000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500886.1379490565000.10201.1399456620889@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3267:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> MOP import resource
> -------------------
>
>                 Key: GTNPORTAL-3267
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3267
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Java API
>    Affects Versions: 3.5.6.Final
>            Reporter: Boubaker Khanfir
>            Assignee: Trong Tran
>             Fix For: 3.9.0.Final
>
>         Attachments: portal_mobile_2013-10-01_11-22-50.zip
>
>   Original Estimate: 4 hours
>          Time Spent: 1 day, 6 hours
>  Remaining Estimate: 0 minutes
>
> MOP resource management is based on a custom marshaller/unmarshaller (org.exoplatform.portal.mop.management.binding.xml.*).
> I had used the mop managed resource in a custom case:
> * Create a new site.
> * Add PortalBody in a container.
> * Export site using GateIN management.
> * Re-import exported site.
> => Exception:
> {code}
> Operation exception for operation import-resource and address /mop [org.gatein.management.cli<pool-4-thread-1>]
> org.gatein.management.api.exceptions.OperationException: Exception reading data for import.
>         at org.exoplatform.portal.mop.management.operations.MopImportResource.execute(MopImportResource.java:198) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.gatein.management.core.api.controller.SimpleManagementController.execute(SimpleManagementController.java:100) ~[gatein-management-core-1.1.0.Final.jar:1.1.0.Final]
> ...
> Caused by: org.staxnav.StaxNavException: Unexpected element 'page-body' at [row,col]:[167,21]
>         at org.gatein.common.xml.stax.navigator.Exceptions.unexpectedElement(Exceptions.java:45) ~[exo.portal.component.common-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.AbstractMarshaller.unmarshalContainer(AbstractMarshaller.java:171) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshalPortalConfig(SiteLayoutMarshaller.java:216) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshal(SiteLayoutMarshaller.java:80) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         ... 40 common frames omitted
> {code}
> To fix this I used the *default* MOP marshaller:
> {code}
> import org.exoplatform.portal.config.model.ModelUnmarshaller;
> // ...
>       public PortalConfig unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(PortalConfig.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> //...
>       public Page.PageSet unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(Page.PageSet.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> //...
>       public PageNavigation unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(PageNavigation.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> // ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:01 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3260) Making redirect admin
 portlet file upload more verbose
In-Reply-To: <JIRA.12500056.1378385708000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500056.1378385708000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500056.1378385708000.10203.1399456621046@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3260:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Making redirect admin portlet file upload more verbose
> ------------------------------------------------------
>
>                 Key: GTNPORTAL-3260
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3260
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Viliam Rockai
>            Assignee: Viliam Rockai
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> 1. Adding message about the failure to the file list
> 2. Show progress bar



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:01 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3218) The global chromattic
 session context doesn't close properly
In-Reply-To: <JIRA.12497829.1375438436000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12497829.1375438436000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12497829.1375438436000.10206.1399456621348@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3218:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> The global chromattic session context doesn't close properly
> ------------------------------------------------------------
>
>                 Key: GTNPORTAL-3218
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3218
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>            Assignee: Trong Tran
>             Fix For: 3.9.0.Final
>
>
> The following unit testcase doesn't work, it fails in the second openning of the context :
> {code}
>     public void testGlobalSessionClose() {
>         chromatticManager.beginRequest();
>         try {
>             test1LF.openContext();
>             // do something
>             test1LF.closeContext(false);  // close without persisting changes to DB
>             //
>             test1LF.openContext();
>             test1LF.closeContext(true);
>         }
>         finally {
>             chromatticManager.endRequest(true);
>         }
>     }
> {code}
> it raises an exception of java.lang.IllegalStateException: A context is already opened



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:01 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3184) Not allowing the same
 user login in at the same time (two sessions)
In-Reply-To: <JIRA.12496513.1373949393000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496513.1373949393000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496513.1373949393000.10209.1399456621638@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3184:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Not allowing the same user login in at the same time (two sessions)
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3184
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3184
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Identity integration, Security
>    Affects Versions: 3.6.0.Final
>            Reporter: Trong Tran
>            Assignee: Vu Viet Phuong
>              Labels: portal-s72, worked
>             Fix For: 3.9.0.Final
>
>   Original Estimate: 1 day, 4 hours
>          Time Spent: 1 day
>  Remaining Estimate: 4 hours
>
> In the DefaultLoginModule, it supports to set "singleLogin" option parameter which disallows the same user to login to use the portal at the same time from different browsers/machines
> Unfortunately it doesn't work properly. I can not login with the same user after logged-out.
> Moreover, the GateIn documentation is also missing this part. I think we could add this information in the section https://docs.jboss.org/author/display/GTNPORTAL36/Authentication+and+Authorization+intro



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:01 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2849) GateIn Redirect Admin
	UI
In-Reply-To: <JIRA.12487285.1363334586000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12487285.1363334586000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12487285.1363334586000.10211.1399456621741@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2849:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> GateIn Redirect Admin UI
> ------------------------
>
>                 Key: GTNPORTAL-2849
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2849
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Boleslaw Dawidowicz
>            Assignee: Boleslaw Dawidowicz
>             Fix For: 3.9.0.Final
>
>
> Administration UI to manage site redirections



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:01 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2808) Change wsdl-host to
 use jbossws.undefined.host to allow for proper WSDL rewriting of all ports
 for WSRP.
In-Reply-To: <JIRA.12483653.1359455966000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12483653.1359455966000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12483653.1359455966000.10213.1399456621891@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2808:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Change wsdl-host to use jbossws.undefined.host to allow for proper WSDL rewriting of all ports for WSRP.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2808
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2808
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Packaging
>    Affects Versions: 3.5.0.Final
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:02 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2760) Define new color set
 for exo calendar project
In-Reply-To: <JIRA.12480558.1354770546000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12480558.1354770546000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12480558.1354770546000.10215.1399456622056@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2760:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Define new color set for exo calendar project 
> ----------------------------------------------
>
>                 Key: GTNPORTAL-2760
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2760
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.4.0.Final
>            Reporter: Tu Nguyen
>            Priority: Minor
>              Labels: gatein
>             Fix For: 3.9.0.Final
>
>
> Define new color set for exo calendar project 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:02 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2744) Changing page size in
 AbstractSerializablePageList should recreate underlying lazy list
In-Reply-To: <JIRA.12480198.1354270407000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12480198.1354270407000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12480198.1354270407000.10217.1399456622206@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2744:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Changing page size in AbstractSerializablePageList should recreate underlying lazy list
> ---------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2744
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2744
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.0.Beta02
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> It seems that if we have pageList of type AbstractSerializablePageList and we want to change the size of the page via setPageSize, we should recreate underlying lazyList. Currently underlying lazyList is not recreated, which means that it's not in line with pageList and still have old pageSize.
> Example: 
> - I will create pageList of size 10
> - I will call pageList.setPageSize(6) -- this will update info of pageList, but underlying lazyList will still have bad info about pageSize
> - I will call pageList.getPage(7). Now lazyList needs to load 20 items (all items from 30 to 39 and then all items from 40 to 49) instead of 6 items (items from 36 to 41).
> Unit test will follow.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:02 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2668) There is portlet
 named "Gadget Wrapper Portlet" in the list of available portlets
In-Reply-To: <JIRA.12476815.1350056247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476815.1350056247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476815.1350056247000.10222.1399456622678@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2668:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> There is portlet named "Gadget Wrapper Portlet" in the list of available portlets
> ---------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2668
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2668
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.4.0.Final
>         Environment: JBoss AS 7.1.3
>            Reporter: Vlastislav Ramik
>            Assignee: Son Tran
>            Priority: Minor
>             Fix For: 3.9.0.Final
>
>
> When you adding portlet into category in application registry, there is "Gadget Wrapper Portlet" listed in available portlets. The portlet is actually Gadget Calendar. 
> If the calendar should be there rename it to calendar. In that case why aren't here other gadgets.
> If the calendar shouldn't be there remove it form there.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:02 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2586) RichFaces module for
	AS7 packaging
In-Reply-To: <JIRA.12474964.1348133247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12474964.1348133247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12474964.1348133247000.10224.1399456622878@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2586:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> RichFaces module for AS7 packaging
> ----------------------------------
>
>                 Key: GTNPORTAL-2586
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2586
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Packaging
>            Reporter: Stian Thorgersen
>             Fix For: 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:03 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2559) Invalid cookie
 message in log when access portal through loadbalancer
In-Reply-To: <JIRA.12473649.1346765964000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12473649.1346765964000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12473649.1346765964000.10227.1399456623289@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2559:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Invalid cookie message in log when access portal through loadbalancer
> ---------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2559
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2559
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.4.0.M01
>         Environment: GateIn master, cluster build, 2 nodes + mod_jk loadbalancer
>            Reporter: Michal Vanco
>            Assignee: Marko Strukelj
>            Priority: Minor
>              Labels: EPP6.0-Test-Dev
>             Fix For: 3.9.0.Final
>
>         Attachments: cookie.txt
>
>
> I'm getting message in portal log when accessing portal on loadbalancer:
> INFO  [org.apache.tomcat.util.http.Cookies] (ajp-perf11/10.16.88.189:8009-8) Cookies: Invalid cookie. Value not a token or quoted value
> This doesn't cause any issue, but wasn't present at EPP5.x version.
> Snippet from ff firebug:
> Connection	keep-alive
> Cookie	gtn.site.preference=FailoverPortal; JSESSIONID=eEGzAwUbc9eCEh9nIkE6ukzl.perf15; s_vi=[CS]v1|281B075B051D1B93-6000012D601169D9[CE]; rh_omni_tc=70160000000H4AjAAK
> Host	perf13.mw.lab.eng.bos.redhat.com:8080
> Pragma	no-cache



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:03 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2556) Stacktrace from
 JBossCachedAuthenticationManager is thrown in log in case of invalid
 credentials
In-Reply-To: <JIRA.12473383.1346322078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12473383.1346322078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12473383.1346322078000.10232.1399456623820@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2556:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Stacktrace from JBossCachedAuthenticationManager is thrown in log in case of invalid credentials
> ------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2556
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2556
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.4.0.M01, 3.4.0.Final
>         Environment: GateIn 3.4.0 M1, AS 7.1.2.Final
>            Reporter: Michal Vanco
>            Assignee: Boleslaw Dawidowicz
>              Labels: EPP6.0-Test-Dev
>             Fix For: 3.9.0.Final
>
>         Attachments: invalid-login.txt
>
>
> When you try to sign in with any invalid credentials, stacktrace is thrown in log. 
> This should be handled by single-line log and not as error with stacktrace.
> Error in log is attached.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:03 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2508) Support add extended
 rewriters for gatein-shindig
In-Reply-To: <JIRA.12470668.1342602065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12470668.1342602065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12470668.1342602065000.10234.1399456623981@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2508:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Support add extended rewriters for gatein-shindig
> -------------------------------------------------
>
>                 Key: GTNPORTAL-2508
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2508
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: kien nguyen
>             Fix For: 3.9.0.Final
>
>
> We need to add a rewriter for rendering GateIn resources in gadget. So we should support this in Shindig, See reflection to [SHINDIG-1456|https://issues.apache.org/jira/browse/SHINDIG-1456]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:04 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:04 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2506) NPE when a portlet is
 not deployed on AS 7
In-Reply-To: <JIRA.12470629.1342538605000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12470629.1342538605000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12470629.1342538605000.10237.1399456624231@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2506:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> NPE when a portlet is not deployed on AS 7
> ------------------------------------------
>
>                 Key: GTNPORTAL-2506
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2506
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>             Fix For: 3.9.0.Final
>
>
> If a portlet is not properly deployed, we get the following error on the console and an unstyled page instead of a proper page with an error message explaining the situation?
> {code}
> 17:16:09,595 ERROR [stderr] (http--127.0.0.1-8080-1) org.gatein.pc.api.NoSuchPortletException: No such portlet /gatein-admin-ui.AdminMenuPortlet
> 17:16:09,596 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:113)
> 17:16:09,596 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83)
> 17:16:09,596 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker._getPortlet(ProducerPortletInvoker.java:202)
> 17:16:09,597 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker.getPortlet(ProducerPortletInvoker.java:119)
> 17:16:09,597 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.federation.impl.FederatedPortletInvokerService.getPortlet(FederatedPortletInvokerService.java:110)
> 17:16:09,598 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.federation.impl.FederatingPortletInvokerService.getPortlet(FederatingPortletInvokerService.java:231)
> 17:16:09,598 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83)
> 17:16:09,598 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83)
> 17:16:09,599 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83)
> 17:16:09,599 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.application.UIPortlet.setState(UIPortlet.java:951)
> 17:16:09,600 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.util.PortalDataMapper.toUIPortlet(PortalDataMapper.java:247)
> 17:16:09,600 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:403)
> 17:16:09,600 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:315)
> 17:16:09,601 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:292)
> 17:16:09,601 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.util.PortalDataMapper.toUIPage(PortalDataMapper.java:321)
> 17:16:09,602 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.page.UIPageBody.getUIPage(UIPageBody.java:148)
> 17:16:09,602 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.page.UIPageBody.setPageBody(UIPageBody.java:78)
> 17:16:09,602 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.portal.UIPortal.refreshUIPage(UIPortal.java:237)
> 17:16:09,603 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.page.UIPageActionListener$ChangeNodeActionListener.execute(UIPageActionListener.java:165)
> 17:16:09,603 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.webui.core.UIComponent.broadcast(UIComponent.java:360)
> 17:16:09,603 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.webui.workspace.UIPortalApplication.processAction(UIPortalApplication.java:638)
> 17:16:09,604 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:177)
> 17:16:09,604 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:150)
> 17:16:09,605 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.WebAppController.service(WebAppController.java:366)
> 17:16:09,605 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:127)
> 17:16:09,605 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132)
> 17:16:09,606 ERROR [stderr] (http--127.0.0.1-8080-1) 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> 17:16:09,606 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
> 17:16:09,606 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,607 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:89)
> 17:16:09,607 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
> 17:16:09,607 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,608 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,608 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:110)
> 17:16:09,609 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.sample.ext.web.SampleFilter.doFilter(SampleFilter.java:46)
> 17:16:09,609 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:106)
> 17:16:09,609 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:80)
> 17:16:09,610 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:79)
> 17:16:09,610 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,610 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,611 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:72)
> 17:16:09,611 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,611 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,612 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:116)
> 17:16:09,612 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,613 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,613 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> 17:16:09,613 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,614 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,614 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.web.login.ClusteredSSOFilter.doFilter(ClusteredSSOFilter.java:73)
> 17:16:09,614 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,615 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,615 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:69)
> 17:16:09,616 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
> 17:16:09,616 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> 17:16:09,616 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
> 17:16:09,617 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> 17:16:09,617 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489)
> 17:16:09,617 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
> 17:16:09,618 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> 17:16:09,618 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 17:16:09,618 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 17:16:09,619 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> 17:16:09,619 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> 17:16:09,619 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
> 17:16:09,620 ERROR [stderr] (http--127.0.0.1-8080-1) 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
> 17:16:09,620 ERROR [stderr] (http--127.0.0.1-8080-1) 	at java.lang.Thread.run(Thread.java:680)
> 17:16:13,012 ERROR [portal:PortalRequestHandler] (http--127.0.0.1-8080-1) Error while handling request: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=1,line=3],data=   uicomponent.renderChildren();] for template system:/groovy/portal/webui/workspace/UIPortalApplicationChildren.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processRender(UIPortalApplicationLifecycle.java:142) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processRender(UIPortalApplicationLifecycle.java:105) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processRender(UIPortalApplicationLifecycle.java:37) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.workspace.UIPortalApplication.processRender(UIPortalApplication.java:686) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:184) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:150) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.web.WebAppController.service(WebAppController.java:366) [exo.portal.component.web.controller-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:127) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.3.6-GA-JBAS7.jar:2.3.6-GA-JBAS7]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:89) [exo.portal.component.web.security-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55) [exo.portal.component.web.security-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:110) [exo.portal.component.web.api-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.sample.ext.web.SampleFilter.doFilter(SampleFilter.java:46) [exo.portal.sample.extension.jar-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:106) [exo.portal.component.web.api-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:80) [exo.portal.component.web.api-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:79) [exo.portal.component.web.api-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:72) [exo.portal.component.web.security-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:116) [exo.jcr.framework.web-1.14.6-GA.jar:1.14.6-GA]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.4.6-GA.jar:2.4.6-GA]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.web.login.ClusteredSSOFilter.doFilter(ClusteredSSOFilter.java:73) [exo.portal.component.web.security-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:69) [exo.kernel.container-2.3.6-GA-JBAS7.jar:2.3.6-GA-JBAS7]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.10.Final.jar:]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:]
> 	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=6,line=2],data=uicomponent.renderChildren()] for template system:/groovy/portal/webui/workspace/UIWorkingWorkspace.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIApplication.renderChildren(UIApplication.java:126) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIPortalApplicationChildren.run(UIPortalApplicationChildren.gtmpl:3)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	... 54 more
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=11,line=55],data=uicomponent.renderChildren();] for template system:/groovy/portal/webui/container/UIContainer.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator$UIComponentDecoratorLifecycle.processRender(UIComponentDecorator.java:113) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator$UIComponentDecoratorLifecycle.processRender(UIComponentDecorator.java:104) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIWorkingWorkspace.run(UIWorkingWorkspace.gtmpl:2)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	... 73 more
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=7,line=31],data= } else { uicomponent.renderChildren(); } ] for template system:/groovy/portal/webui/page/UISiteBody.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIContainer.run(UIContainer.gtmpl:55)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	... 94 more
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=9,line=16],data=uicomponent.renderChildren();] for template system:/groovy/portal/webui/portal/UIPortal.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.portal.UIPortalLifecycle.processRender(UIPortalLifecycle.java:41) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.portal.UIPortalLifecycle.processRender(UIPortalLifecycle.java:30) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator.renderChildren(UIComponentDecorator.java:101) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UISiteBody.run(UISiteBody.gtmpl:31)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIContainer.run(UIContainer.gtmpl:66)	... 95 more
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=7,line=44],data= } else { uicomponent.renderChildren(); }] for template system:/groovy/portal/webui/page/UIPageBody.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.page.UIPageBody.processRender(UIPageBody.java:162) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIPortal.run(UIPortal.gtmpl:16)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.portal.UIPortalLifecycle.processRender(UIPortalLifecycle.java:41) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.portal.UIPortalLifecycle.processRender(UIPortalLifecycle.java:30) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator.renderChildren(UIComponentDecorator.java:101) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UISiteBody.run(UISiteBody.gtmpl:27)	... 113 more
> Caused by: org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=9,line=6],data=uicomponent.renderChildren()] for template system:/groovy/portal/webui/page/UIPage.gtmpl
> 	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:121) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.page.UIPageLifecycle.processRender(UIPageLifecycle.java:44) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator.renderChildren(UIComponentDecorator.java:101) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIPageBody.run(UIPageBody.gtmpl:44)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	... 150 more
> Caused by: java.lang.NullPointerException
> 	at org.exoplatform.portal.webui.application.UIPortlet.processRender(UIPortlet.java:1112) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIPage.run(UIPage.gtmpl:6)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:111) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:119) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117) [exo.portal.component.scripting-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:125) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:83) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.portal.webui.page.UIPageLifecycle.processRender(UIPageLifecycle.java:44) [exo.portal.webui.portal-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponent.processRender(UIComponent.java:144) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at org.exoplatform.webui.core.UIComponentDecorator.renderChildren(UIComponentDecorator.java:101) [exo.portal.webui.framework-3.4.0-GA-SNAPSHOT.jar:3.4.0-GA-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_33]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_33]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_33]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_33]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) [groovy-all-1.7.6.jar:1.7.6]
> 	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-all-1.7.6.jar:1.7.6]
> 	at UIPageBody.run(UIPageBody.gtmpl:39)	... 151 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May  7 05:57:04 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:04 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2505) Error when hot
 re-deploying a JSF portlet on AS 7
In-Reply-To: <JIRA.12470626.1342538038000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12470626.1342538038000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12470626.1342538038000.10240.1399456624475@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2505:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Error when hot re-deploying a JSF portlet on AS 7
> -------------------------------------------------
>
>                 Key: GTNPORTAL-2505
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2505
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Packaging
>            Reporter: Chris Laprun
>            Assignee: Marko Strukelj
>             Fix For: 3.9.0.Final
>
>
> Using AS 7.1.0 and looks maybe like a JSF issue:
> 17:06:36,792 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-12) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/gatein-admin-ui'
> 17:06:37,406 WARNING [javax.enterprise.resource.webcontainer.jsf.managedbean] (MSC service thread 1-12) JSF1074: Managed bean named 'a4j' has already been registered.  Replacing existing managed bean class type org.richfaces.VersionBean with org.richfaces.VersionBean.
> 17:06:37,406 WARNING [javax.enterprise.resource.webcontainer.jsf.managedbean] (MSC service thread 1-12) JSF1074: Managed bean named 'a4jSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
> 17:06:37,407 WARNING [javax.enterprise.resource.webcontainer.jsf.managedbean] (MSC service thread 1-12) JSF1074: Managed bean named 'richSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
> 17:06:37,973 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-12) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! duplicate key: interface javax.validation.constraints.AssertTrue
> 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:376) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.10.Final.jar:]
> 	at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.10.Final.jar:]
> 	at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33]
> 	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
> Caused by: java.lang.IllegalArgumentException: duplicate key: interface javax.validation.constraints.AssertTrue
> 	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115) [guava-r09.jar:]
> 	at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:72) [guava-r09.jar:]
> 	at com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:221) [guava-r09.jar:]
> 	at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:207) [guava-r09.jar:]
> 	at org.richfaces.javascript.ClientServiceConfigParser.parseConfig(ClientServiceConfigParser.java:53) [richfaces-components-ui-4.3.0-20120716.091232-81.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.ValidatorModule.createClientScriptService(ValidatorModule.java:65) [richfaces-components-ui-4.3.0-20120716.091232-81.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.ValidatorModule.configure(ValidatorModule.java:60) [richfaces-components-ui-4.3.0-20120716.091232-81.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.ServicesFactoryImpl.init(ServicesFactoryImpl.java:27) [richfaces-core-impl-4.3.0-20120716.085859-54.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.InitializationListener.createFactory(InitializationListener.java:129) [richfaces-core-impl-4.3.0-20120716.085859-54.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:67) [richfaces-core-impl-4.3.0-20120716.085859-54.jar:4.3.0-SNAPSHOT]
> 	at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:147) [richfaces-core-impl-4.3.0-20120716.085859-54.jar:4.3.0-SNAPSHOT]
> 	at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.0.Final.jar:2.0.0.Final]
> 	at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2168) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2144) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:302) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:601) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:370) [jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
> 	... 9 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:05 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:05 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2487) Caused by:
 java.lang.IllegalStateException: Portlet is not started after hot redeploy
 of portlet war
In-Reply-To: <JIRA.12469682.1340972046000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12469682.1340972046000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12469682.1340972046000.10246.1399456625057@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-2487:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> Caused by: java.lang.IllegalStateException: Portlet is not started after hot redeploy of portlet war
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2487
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2487
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: PC integration
>    Affects Versions: 3.3.0.Final
>            Reporter: Chris Laprun
>            Assignee: Marko Strukelj
>            Priority: Critical
>             Fix For: 3.9.0.Final
>
>         Attachments: GTNPORTAL-2487.patch
>
>
> Trying to access a portlet that has already been accessed and which WAR has been hot-redeployed leads to the following exception:
> Caused by: java.lang.IllegalStateException: Portlet AdminMenuPortlet is not started
> 	at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.getInfo(PortletContainerImpl.java:186) [pc-portlet-2.3.2-GA.jar:2.3.2-GA]
> 	at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.getInfo(PortletContainerImpl.java:96) [pc-portlet-2.3.2-GA.jar:2.3.2-GA]
> 	at org.gatein.pc.portlet.container.ContainerPortletInvoker$PortletImpl.getInfo(ContainerPortletInvoker.java:233) [pc-portlet-2.3.2-GA.jar:2.3.2-GA]
> 	at org.gatein.pc.federation.impl.FederatedPortlet.getInfo(FederatedPortlet.java:77) [pc-federation-2.3.2-GA.jar:2.3.2-GA]
> 	at org.exoplatform.portal.webui.application.UIPortlet.processRender(UIPortlet.java:1112) [exo.portal.webui.portal-3.3.0-GA.jar:3.3.0-GA]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:368) [exo.portal.webui.framework-3.3.0-GA.jar:3.3.0-GA]
> 	at org.exoplatform.webui.core.UIContainer.renderChildren(UIContainer.java:358) [exo.portal.webui.framework-3.3.0-GA.jar:3.3.0-GA]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:05 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:05 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-1805) add ability to send
 email on registration and x successive failures
In-Reply-To: <JIRA.12430761.1297971016000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12430761.1297971016000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12430761.1297971016000.10250.1399456625363@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-1805:
----------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> add ability to send email on registration and x successive failures
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-1805
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-1805
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Identity integration
>            Reporter: Prabhat Jha
>            Assignee: Marek Posolda
>            Priority: Optional
>             Fix For: 3.9.0.Final
>
>         Attachments: README.txt, sendMailAfterInvalidLoginPatch.txt, sendMailAfterRegistrationPatch.txt
>
>
> Please attach the patch based on your work at https://issues.jboss.org/browse/JBQA-4122. By default the feature should be turned off.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 05:57:06 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 05:57:06 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-511) userPref of gadgets
 are not sometime not saved correctly
In-Reply-To: <JIRA.12402218.1263639452000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12402218.1263639452000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12402218.1263639452000.10256.1399456626018@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-511:
---------------------------------

    Fix Version/s: 3.9.0.Final
                       (was: 3.7.1.Final)


> userPref of gadgets are not sometime not saved correctly
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-511
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-511
>             Project: GateIn Portal
>          Issue Type: Bug
>          Components: User Interface
>    Affects Versions: 3.0.0-Beta04
>         Environment: svn r1330
>            Reporter: jerem j
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.9.0.Final
>
>         Attachments: GTNPORTAL-511.js.patch, GTNPORTAL-511.patch, stacktrace.txt
>
>   Original Estimate: 2 days
>          Time Spent: 2 days, 2 hours
>  Remaining Estimate: 0 minutes
>
> Every call to gadgets.Prefs.set generate a call to save the data in the backend (an action in the dashboard portlet). To save we send all the set of preferences.
> The jira gadget call this API multiple times in a very short time. So there is multiple ajax request sent to the backend but not in a precise order. So it might happen that the first request arrive the last one, and so old preferences are saved.
> To fix:
> In the file Gadgets.js, function "gadgets.IfrGadgetService.prototype.setUserPref", prefs is updated with all the name/value, and ALL the prefs object is saved. Instead of saving all the preferences, we should only save the updated preferences.
> In org.exoplatform.portal.pom.spi.gadget.Gadget it will be needed to be able to add preference by name, something like :
> public void setUserPref(String name, String value)
> code :
> Gadgets.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResources/src/main/webapp/javascript/eXo/gadget/Gadgets.js?r=HEAD
> ExoBasedUserPrefStore.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResources/src/main/webapp/javascript/eXo/gadget/ExoBasedUserPrefStore.js?r=HEAD
> links:
> API doc about adgets.Prefs.set: http://code.google.com/apis/gadgets/docs/reference/#gadgets.Prefs.set
> Jira gadget to test: http://jira4j.exoplatform.org/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:watched-gadget/gadgets/watched-gadget.xml



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 06:10:56 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Wed, 7 May 2014 06:10:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3267) MOP import resource
In-Reply-To: <JIRA.12500886.1379490565000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500886.1379490565000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500886.1379490565000.10284.1399457456770@jira02.app.mwc.hst.phx2.redhat.com>


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

Boubaker Khanfir commented on GTNPORTAL-3267:
---------------------------------------------

If you are searching for the best solution to do this, take a look at:
https://github.com/exo-addons/staging-extension/blob/master/component/site/src/main/java/org/exoplatform/management/mop/binding/CustomMopBindingProvider.java

In this file I used the MOP API Marshaller and unmarshaller. In the current situation, you develop your own marshaller and unmarshaller instead of using the default ones. I recommend to use the default provided ones instead of coding and maintaining new one. (Two impls in the same jar for the same behavior).

> MOP import resource
> -------------------
>
>                 Key: GTNPORTAL-3267
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3267
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Java API
>    Affects Versions: 3.5.6.Final
>            Reporter: Boubaker Khanfir
>            Assignee: Trong Tran
>             Fix For: 3.9.0.Final
>
>         Attachments: portal_mobile_2013-10-01_11-22-50.zip
>
>   Original Estimate: 4 hours
>          Time Spent: 1 day, 6 hours
>  Remaining Estimate: 0 minutes
>
> MOP resource management is based on a custom marshaller/unmarshaller (org.exoplatform.portal.mop.management.binding.xml.*).
> I had used the mop managed resource in a custom case:
> * Create a new site.
> * Add PortalBody in a container.
> * Export site using GateIN management.
> * Re-import exported site.
> => Exception:
> {code}
> Operation exception for operation import-resource and address /mop [org.gatein.management.cli<pool-4-thread-1>]
> org.gatein.management.api.exceptions.OperationException: Exception reading data for import.
>         at org.exoplatform.portal.mop.management.operations.MopImportResource.execute(MopImportResource.java:198) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.gatein.management.core.api.controller.SimpleManagementController.execute(SimpleManagementController.java:100) ~[gatein-management-core-1.1.0.Final.jar:1.1.0.Final]
> ...
> Caused by: org.staxnav.StaxNavException: Unexpected element 'page-body' at [row,col]:[167,21]
>         at org.gatein.common.xml.stax.navigator.Exceptions.unexpectedElement(Exceptions.java:45) ~[exo.portal.component.common-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.AbstractMarshaller.unmarshalContainer(AbstractMarshaller.java:171) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshalPortalConfig(SiteLayoutMarshaller.java:216) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshal(SiteLayoutMarshaller.java:80) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
>         ... 40 common frames omitted
> {code}
> To fix this I used the *default* MOP marshaller:
> {code}
> import org.exoplatform.portal.config.model.ModelUnmarshaller;
> // ...
>       public PortalConfig unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(PortalConfig.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> //...
>       public Page.PageSet unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(Page.PageSet.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> //...
>       public PageNavigation unmarshal(InputStream inputStream) throws BindingException {
>         try {
>           return ModelUnmarshaller.unmarshall(PageNavigation.class, inputStream).getObject();
>         } catch (Exception e) {
>           throw new BindingException(e);
>         }
>       }
> // ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 06:24:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Wed, 7 May 2014 06:24:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.10300.1399458296402@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3472:
----------------------------------

    Description: 
We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:

{code}
[jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
java.lang.NullPointerException
	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)
{code}

*MBeans which seem to cause this problem :*
- exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=*,service=SessionRegistry
- exo:portal=portal,repository=\*,workspace=\*,service=Cache
- exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
- exo:portal=portal,service=cache,name=*

*How to reproduce :*
- unzip GateIn 3.7.0.Final tomcat distribution
- copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
- start your portal and watch the starup logs


  was:
We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:

{code}
[jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
java.lang.NullPointerException
	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)
{code}

*MBeans which seem to cause this problem :*
- exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=*,service=SessionRegistry
- exo:portal=portal,repository=\*,workspace=\*,service=Cache
- exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
- exo:portal=portal,service=cache,name=*

*How to reproduce :*
- unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
- copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
- start your portal and watch the starup logs




> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>             Fix For: 3.9.0.Final
>
>         Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 22:40:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Wed, 7 May 2014 22:40:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3474) Items in status list
 are displayed in english
In-Reply-To: <JIRA.12540204.1399516748499@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540204.1399516748499@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540204.1399516748499.12072.1399516856353@jira02.app.mwc.hst.phx2.redhat.com>

Vu Viet Phuong created GTNPORTAL-3474:
-----------------------------------------

             Summary: Items in status list are displayed in english
                 Key: GTNPORTAL-3474
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3474
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.8.0.Beta01, 3.7.1.Final
            Reporter: Vu Viet Phuong
            Assignee: Vu Viet Phuong
            Priority: Minor


1- Login as root and set language to French 
2- Go to Administration/Users/Group and Roles
3- Choose the tab "User Management"

--> the Enable/Disable/All selectbox is not localized



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 22:42:56 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Wed, 7 May 2014 22:42:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3474) Items in status list
 are displayed in english
In-Reply-To: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540204.1399516748000.12075.1399516976177@jira02.app.mwc.hst.phx2.redhat.com>


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

Vu Viet Phuong updated GTNPORTAL-3474:
--------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/853


> Items in status list are displayed in english
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3474
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3474
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.1.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>            Priority: Minor
>
> 1- Login as root and set language to French 
> 2- Go to Administration/Users/Group and Roles
> 3- Choose the tab "User Management"
> --> the Enable/Disable/All selectbox is not localized



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 03:33:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 8 May 2014 03:33:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.12202.1399534436404@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3472:
----------------------------------

    Fix Version/s: 3.5.10.Final
                   3.7.2.Final


> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>             Fix For: 3.5.10.Final, 3.7.2.Final, 3.9.0.Final
>
>         Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 03:33:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 8 May 2014 03:33:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3472) NPE in
 PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans
 are invoked
In-Reply-To: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540041.1399437704000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540041.1399437704000.12204.1399534436600@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran resolved GTNPORTAL-3472.
-----------------------------------

    Resolution: Done


> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3472
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3472
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Trong Tran
>             Fix For: 3.5.10.Final, 3.7.2.Final, 3.9.0.Final
>
>         Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> 	at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> 	at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> 	at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> 	at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> 	at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> 	at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> 	at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> 	at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> 	at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 04:15:58 2014
From: issues at jboss.org (Michael McKinsey (JIRA))
Date: Thu, 8 May 2014 04:15:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877735@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877735@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877735.12259.1399536958559@jira02.app.mwc.hst.phx2.redhat.com>

Michael McKinsey created GTNSSO-28:
--------------------------------------

             Summary: realm is wrong adds an extra g in the realm name with OpenAM 11
                 Key: GTNSSO-28
                 URL: https://issues.jboss.org/browse/GTNSSO-28
             Project: GateIn SSO
          Issue Type: Bug
    Affects Versions: 1.4.0.Beta01
         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
            Reporter: Michael McKinsey
            Assignee: Marek Posolda
            Priority: Blocker


The realm name is coming up wrong with an extra g which I believe is causing the error #403x

https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0

notice realm is ggatein

I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java

It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;

I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 04:19:56 2014
From: issues at jboss.org (Michael McKinsey (JIRA))
Date: Thu, 8 May 2014 04:19:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.12261.1399537196435@jira02.app.mwc.hst.phx2.redhat.com>


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

Michael McKinsey updated GTNSSO-28:
-----------------------------------

    Description: 
The realm name is coming up wrong with an extra g which I believe is causing the error #403x

https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0

notice realm is ggatein

I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java

It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;

I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.

  was:
The realm name is coming up wrong with an extra g which I believe is causing the error #403x

https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0

notice realm is ggatein

I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java

It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;

I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>            Priority: Blocker
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 04:21:57 2014
From: issues at jboss.org (Michael McKinsey (JIRA))
Date: Thu, 8 May 2014 04:21:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.12267.1399537317034@jira02.app.mwc.hst.phx2.redhat.com>


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

Michael McKinsey updated GTNSSO-28:
-----------------------------------

    Description: 
The realm name is coming up wrong with an extra g which I believe is causing the error #403x

https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0

notice realm is ggatein

I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java

It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;

I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.

  was:
The realm name is coming up wrong with an extra g which I believe is causing the error #403x

https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0

notice realm is ggatein

I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java

It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;

I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>            Priority: Blocker
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 04:53:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 8 May 2014 04:53:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3474) Items in status list
 are displayed in english
In-Reply-To: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540204.1399516748000.12313.1399539236695@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3474:
----------------------------------

    Fix Version/s: 3.7.2.Final
                   3.9.0.Final


> Items in status list are displayed in english
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3474
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3474
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.1.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>            Priority: Minor
>             Fix For: 3.7.2.Final, 3.9.0.Final
>
>
> 1- Login as root and set language to French 
> 2- Go to Administration/Users/Group and Roles
> 3- Choose the tab "User Management"
> --> the Enable/Disable/All selectbox is not localized



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 04:53:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 8 May 2014 04:53:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3474) Items in status list
 are displayed in english
In-Reply-To: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540204.1399516748000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540204.1399516748000.12315.1399539236901@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3474:
----------------------------------

        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Items in status list are displayed in english
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3474
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3474
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.1.Final, 3.8.0.Beta01
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>            Priority: Minor
>             Fix For: 3.7.2.Final, 3.9.0.Final
>
>
> 1- Login as root and set language to French 
> 2- Go to Administration/Users/Group and Roles
> 3- Choose the tab "User Management"
> --> the Enable/Disable/All selectbox is not localized



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 06:49:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 8 May 2014 06:49:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3224) Recursive paste
 navigation nodes in navigation editor
In-Reply-To: <JIRA.12498134.1375865465000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12498134.1375865465000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12498134.1375865465000.12439.1399546196415@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3224:
----------------------------------

    Fix Version/s: 3.5.10.Final


> Recursive paste navigation nodes in navigation editor
> -----------------------------------------------------
>
>                 Key: GTNPORTAL-3224
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3224
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Management
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>              Labels: backlogs
>             Fix For: 3.5.10.Final, 3.7.0.Final
>
>          Time Spent: 1 hour
>  Remaining Estimate: 0 minutes
>
> Login as root and open navigation editor (Site --> edit navigation)
> Copy or clone SiteMap, and paste to Home node, let's call it "NewSiteMap"
> Copy or Cut Home, paste it to "NewSiteMap" --> infinite loop happened
> The problem is in UINavigationEditor#PasteNodeActionListener --> need to traverse all node in the tree, and copy it --> we should check the condition to stop the loop



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 06:29:57 2014
From: issues at jboss.org (Vu Viet Phuong (JIRA))
Date: Fri, 9 May 2014 06:29:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3285) Logic of deleting
	user is not proper
In-Reply-To: <JIRA.12518096.1383722975000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518096.1383722975000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518096.1383722975000.14435.1399631397142@jira02.app.mwc.hst.phx2.redhat.com>


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

Vu Viet Phuong updated GTNPORTAL-3285:
--------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.7.2.Final
       Resolution: Done


> Logic of deleting user is not proper
> ------------------------------------
>
>                 Key: GTNPORTAL-3285
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3285
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.7.2.Final
>
>
> I try to add a listener to not allow delete Platform users. for example:
> {code}
> public class IntranetUserEventListenerImpl extends UserEventListener {
>   @Override
>   public void preDelete(User user) throws Exception {
>    //don't allow delete user
>       throw new MessageException(new ApplicationMessage("IntranetUserEventListener.msg.delete-user-read-only-mode-error", null, ApplicationMessage.WARNING));
> }
> {code}
> This listener can help to not allow delete user, but all memberships of user still are deleted.
> Check logic of deleting users (in file https://github.com/exoplatform/gatein-portal/blob/3.5.x-PLF/component/identity/src/main/java/org/exoplatform/services/organization/idm/UserDAOImpl.java): we can see it deletes all membershis of an user before broadcast event "preDelete"
> {code}
> public User removeUser(String userName, boolean broadcast) throws Exception {
> //...
>   
>        try {
>             // Remove all memberships and profile first
>             orgService.getMembershipHandler().removeMembershipByUser(userName, false);
>             orgService.getUserProfileHandler().removeUserProfile(userName, false);
>         } catch (Exception e) {
>             handleException("Cannot cleanup user relationships: " + userName + "; ", e);
>         }
>         User exoUser = getPopulatedUser(userName, session);
>         if (broadcast) {
>             preDelete(exoUser);
>         }
>         try {
>             session.getPersistenceManager().removeUser(foundUser, true);
>         } catch (IdentityException e) {
>             handleException("Cannot remove user: " + userName + "; ", e);
>         }
> //...
> }
> {code}
> Expectation:  
> 1) broadcast preDelete(exoUser) should be run before delete anything
> 2) Delete user and its membership should be run in one transaction



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 07:27:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 9 May 2014 07:27:56 -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@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533248.1393339019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533248.1393339019000.14512.1399634876625@jira02.app.mwc.hst.phx2.redhat.com>


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

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 ON_QA to ASSIGNED

>  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
>      Security Level: Public(Everyone can see) 
>    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.2.3#6260)


From issues at jboss.org  Fri May  9 07:41:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 9 May 2014 07:41:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695332@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695332@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695332.14526.1399635717078@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3475:
---------------------------------------

             Summary: NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
                 Key: GTNPORTAL-3475
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga


Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.

Steps to reproduce:
(1) Start clean Portal instance for the first time
(2) Go to Application Registry
(3) Import Applications

Not OK: There is an NPE logged (the whole log is attached):
{code:plain}
Caused by: java.lang.NullPointerException
	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
{code}

Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 07:43:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 9 May 2014 07:43:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.14532.1399635836787@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3475:
------------------------------------

    Attachment: GTNPORTAL-3475.log


> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:plain}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 07:47:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 9 May 2014 07:47:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.14534.1399636076232@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3475:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1096190


> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:plain}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 09:57:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 9 May 2014 09:57:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3476) Obsolete version
 numbers in jboss packaging
In-Reply-To: <JIRA.12540346.1399643839424@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540346.1399643839424@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540346.1399643839424.14957.1399643877634@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3476:
---------------------------------------

             Summary: Obsolete version numbers in jboss packaging
                 Key: GTNPORTAL-3476
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3476
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.8.0.Final
            Reporter: Peter Palaga
            Assignee: Peter Palaga


The versions in jboss packaging are still on 3.8.0.Beta02-SNAPSHOT, see https://github.com/gatein/gatein-portal/blob/3.8.0.Final/packaging/jboss/pom.xml#L6
It is probably, because packaging/jboss is not included by default and I released 3.8.0.Final without the new dedicated profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 12:03:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 9 May 2014 12:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3477) Make GadgetImporter
 throw an exception with a meaningful message
In-Reply-To: <JIRA.12540360.1399651321265@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540360.1399651321265@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540360.1399651321265.15403.1399651436968@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3477:
---------------------------------------

             Summary: Make GadgetImporter throw an exception with a meaningful message
                 Key: GTNPORTAL-3477
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3477
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga


{{GadgetImporter}} throws {{new IOException()}} without message and logs {{"Cannot import gadget " + gadgetURI + " because its data could not be found"}} on the previous line. We should apply both of the following:
(1) Either throw or log not both
(2) Throw exceptions with informative messages.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 05:07:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 12 May 2014 05:07:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3259) Configurable default
 view mode in page editor
In-Reply-To: <JIRA.12500019.1378366720000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500019.1378366720000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500019.1378366720000.16714.1399885676567@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Configurable default view mode in page editor
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3259
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3259
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            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.2.3#6260)

From issues at jboss.org  Mon May 12 07:29:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 12 May 2014 07:29:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144621@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144621@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144621.17153.1399894196408@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3478:
--------------------------------------

             Summary: CDI portlet throws an exception in session logout
                 Key: GTNPORTAL-3478
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Common integration, WCI integration
    Affects Versions: 3.8.0.Beta01
            Reporter: Lucas Ponce
            Assignee: Marko Strukelj
             Fix For: 3.8.1.Final


Test source code can be downloaded here:

https://github.com/lucasponce/cdi-portlets-ejb

After session logout in a page where cdi portlet is present we can see this exception:

13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    


























































        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
        at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
        at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 07:31:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 12 May 2014 07:31:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.17155.1399894316452@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3478:
-----------------------------------

    Attachment: cdi-portlets-ejb.war


Binary test .war used.

> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Marko Strukelj
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 07:31:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 12 May 2014 07:31:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.17157.1399894316633@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce reassigned GTNPORTAL-3478:
--------------------------------------

    Assignee: Lucas Ponce  (was: Marko Strukelj)


> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 07:37:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 12 May 2014 07:37:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.17158.1399894676213@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce commented on GTNPORTAL-3478:
----------------------------------------

English exception:

13:34:13,217 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-39) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton not set for org.exoplatform.container.PortalContainerClassLoader at 73abfce4. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
	at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:76)
	at org.jboss.weld.Container.instance(Container.java:54)
	at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
	at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
	at org.gatein.cdi.CDIPortletContextExtension$Proxy$_$$_WeldClientProxy.getContext(CDIPortletContextExtension$Proxy$_$$_WeldClientProxy.java)
	at org.gatein.cdi.contexts.listeners.AbstractCDIServletListener.sessionDestroyed(AbstractCDIServletListener.java:78)
	at org.apache.catalina.session.StandardSession.expire(StandardSession.java:681) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.session.StandardSession.expire(StandardSession.java:644) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1092) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:150) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.wci.jboss.JB7ServletContainerContext$1.executeTask(JB7ServletContainerContext.java:167) [wci-jboss7-2.4.1.Final.jar:2.4.1.Final]
	at org.gatein.wci.session.SessionTaskVisitor.accept(SessionTaskVisitor.java:53) [wci-wci-2.4.1.Final.jar:2.4.1.Final]
	at org.gatein.wci.ServletContainer.visit(ServletContainer.java:410) [wci-wci-2.4.1.Final.jar:2.4.1.Final]
	at org.gatein.wci.jboss.JB7ServletContainerContext.logout(JB7ServletContainerContext.java:162) [wci-jboss7-2.4.1.Final.jar:2.4.1.Final]
	at org.gatein.wci.ServletContainer.logout(ServletContainer.java:205) [wci-wci-2.4.1.Final.jar:2.4.1.Final]
	at org.exoplatform.portal.application.PortalLogoutLifecycle.onEndRequest(PortalLogoutLifecycle.java:93) [exo.portal.webui.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.portal.application.PortalLogoutLifecycle.onEndRequest(PortalLogoutLifecycle.java:46) [exo.portal.webui.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:260) [exo.portal.webui.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:184) [exo.portal.webui.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.web.WebAppController.service(WebAppController.java:340) [exo.portal.component.web.controller-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133) [exo.kernel.container-2.5.0-GA.jar:2.5.0-GA]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72) [exo.portal.component.web.api-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92) [exo.portal.component.web.api-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68) [exo.portal.component.web.security-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.16.0-GA.jar:1.16.0-GA]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84) [exo.portal.component.web.security-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.6.0-GA.jar:2.6.0-GA]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122) [exo.portal.component.web.security-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55) [exo.portal.component.web.security-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.4.1.Final.jar:1.4.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.5.0-GA.jar:2.5.0-GA]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.1.Final.jar:1.4.1.Final]
	at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.1.Final-SNAPSHOT.jar:3.8.1.Final-SNAPSHOT]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_05]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_05]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_05]



> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 09:51:57 2014
From: issues at jboss.org (Ken Finnigan (JIRA))
Date: Mon, 12 May 2014 09:51:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.17745.1399902717277@jira02.app.mwc.hst.phx2.redhat.com>


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

Ken Finnigan commented on GTNPORTAL-3478:
-----------------------------------------

As mentioned on IRC, I believe this is a result of https://github.com/gatein/gatein-wci/blob/master/wci/src/main/java/org/gatein/wci/ServletContainer.java#L408 not setting the TCCL of the WebApp prior to the visitor.accept() call.

> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 11:56:56 2014
From: issues at jboss.org (Fred Bricon (JIRA))
Date: Mon, 12 May 2014 11:56:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3479) Errors importing
 GateIn Portal projects in Eclipse
In-Reply-To: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540558.1399910010000.18292.1399910216633@jira02.app.mwc.hst.phx2.redhat.com>


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

Fred Bricon moved JBIDE-17259 to GTNPORTAL-3479:
------------------------------------------------

          Project: GateIn Portal  (was: Tools (JBoss Tools))
              Key: GTNPORTAL-3479  (was: JBIDE-17259)
         Assignee:     (was: Fred Bricon)
      Component/s: Common integration
                       (was: portal-gatein)
                       (was: maven)
         Security: Public
    Fix Version/s:     (was: 4.2.0.Beta2)


> Errors importing GateIn Portal projects in Eclipse
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3479
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3479
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration
>         Environment: - Fedora 20
> - OpenJDK 1.7.0_51 (latest from Fedora 20)
> - JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93)
>            Reporter: Juraci Paix?o Kr?hling
>
> When trying to import "GateIn Portal" as an "Existing Maven Project" in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages:
> - "JBoss Core Portlet 2.0 requires Java 1.5 or newer"
> - "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer"
> Steps to reproduce:
> - Install JBoss Developer Studio with EAP
> - Import "Existing Maven Project", selecting the root of the GateIn clone (ex: https://github.com/jpkrohling/gatein-portal)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 11:58:56 2014
From: issues at jboss.org (Fred Bricon (JIRA))
Date: Mon, 12 May 2014 11:58:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3479) Errors importing
 GateIn Portal projects in Eclipse
In-Reply-To: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540558.1399910010000.18302.1399910336976@jira02.app.mwc.hst.phx2.redhat.com>


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

Fred Bricon commented on GTNPORTAL-3479:
----------------------------------------

specific m2e/portlet integration errors are handled in JBIDE-17112

Now here are what the issues that need to be fixed at the gatein projects level :
* Web Facet is not installed because projects use web.xml 3.0 AND maven-compiler-plugin configuration is overridden to use 1.5. Since Web 3.0 requires 1.6, the constraint is not met, the Facet can't be installed (which in turn prevents the Java facet to be installed apparently). Why do you need to downgrade the java version in the first place? If you really really do need to (remember even 1.6 is EOL'ed), then you should also downgrade the web.xml version to 2.5
* I have several projects not compiling because of missing jdom:jdom:1.1.1 (jboss and exo repositories are configured). Where is it supposed to come from?
* Some JSPs don't compile in eclipse, because dependencies have not been added to the pom (jsp-api, exo apis...). I understand they're not required to compile the java classes, but if you want to have your projects error-free in eclipse, you need to add the required deps to your war projects.

> Errors importing GateIn Portal projects in Eclipse
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3479
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3479
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration
>         Environment: - Fedora 20
> - OpenJDK 1.7.0_51 (latest from Fedora 20)
> - JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93)
>            Reporter: Juraci Paix?o Kr?hling
>
> When trying to import "GateIn Portal" as an "Existing Maven Project" in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages:
> - "JBoss Core Portlet 2.0 requires Java 1.5 or newer"
> - "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer"
> Steps to reproduce:
> - Install JBoss Developer Studio with EAP
> - Import "Existing Maven Project", selecting the root of the GateIn clone (ex: https://github.com/jpkrohling/gatein-portal)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 12 13:26:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 12 May 2014 13:26:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.18446.1399915616400@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce commented on GTNPORTAL-3478:
----------------------------------------

Right.
After some investigation it seems that session.invalidate() logic was moved to PortalContainer CL.
A preliminar patch like:
         @Override
         public boolean executeTask(HttpSession session)
         {
            ClassLoader portalContainerCL = Thread.currentThread().getContextClassLoader();
            ClassLoader webAppCL = session.getServletContext().getClassLoader();

            Thread.currentThread().setContextClassLoader(webAppCL);
            session.invalidate();
            Thread.currentThread().setContextClassLoader(portalContainerCL);

            return true;
         }

seems to fix the issue.

I will investigate more this approach with more tests before to prepare a definitive patch.

> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May 13 04:34:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 13 May 2014 04:34:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.19244.1399970096510@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3478:
-----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-wci/pull/15


> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May 13 05:14:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 13 May 2014 05:14:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3478) CDI portlet throws an
 exception in session logout
In-Reply-To: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540490.1399894144000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540490.1399894144000.19332.1399972496410@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3478:
-----------------------------------

        Status: Closed  (was: Pull Request Sent)
    Resolution: Done


> CDI portlet throws an exception in session logout
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3478
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3478
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration, WCI integration
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.1.Final
>
>         Attachments: cdi-portlets-ejb.war
>
>
> Test source code can be downloaded here:
> https://github.com/lucasponce/cdi-portlets-ejb
> After session logout in a page where cdi portlet is present we can see this exception:
> 13:07:06,022 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/cdi-portlets-ejb]] (http-/127.0.0.1:8080-128) JBWEB000211: Session event listener threw exception: java.lang.IllegalStateException: JBAS016071: Singleton no establecido para org.exoplatform.container.PortalContainerClassLoader at 67d9d828. Esto significa que usted est? intentando acceder a una implementaci?n de soldadura con  Thread Context ClassLoader que no est? asociado con la implementaci?n.                                                                                                                                                                                                                                    
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.4.0.Final.jar:1.4.0.Final]
>         at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:94) [exo.portal.component.web.security-jboss-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
>         at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
>         at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May 13 05:17:00 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 13 May 2014 05:17:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3480) Upgrade WCI
	dependency to 2.4.2.Final
In-Reply-To: <JIRA.12540610.1399972559787@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540610.1399972559787@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540610.1399972559787.19345.1399972620789@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3480:
--------------------------------------

             Summary: Upgrade WCI dependency to 2.4.2.Final
                 Key: GTNPORTAL-3480
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3480
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 05:18:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 13 May 2014 05:18:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCI-52) Release 2.4.2.Final
In-Reply-To: <JIRA.12540611.1399972655101@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540611.1399972655101@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540611.1399972655101.19346.1399972736327@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNWCI-52:
---------------------------------

             Summary: Release 2.4.2.Final
                 Key: GTNWCI-52
                 URL: https://issues.jboss.org/browse/GTNWCI-52
             Project: GateIn Web Container Integration
          Issue Type: Enhancement
            Reporter: Lucas Ponce






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 07:08:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 07:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3452) Changing permissions
 in ApplicationRegistry causes error
In-Reply-To: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538778.1398181740000.19746.1399979336921@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Changing permissions in ApplicationRegistry causes error
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-3452
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3452
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Changing permission of any portlet in Application Registry will cause "java.lang.Exception: Invalid Application Id: [web_slash_IFramePortlet]". 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 07:12:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 07:12:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3449) Adding new node in
 group navigation doesn't work
In-Reply-To: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538736.1398157303000.19769.1399979576600@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Adding new node in group navigation doesn't work
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3449
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3449
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 07:38:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 13 May 2014 07:38:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-35) Review String manipulation
In-Reply-To: <JIRA.12540628.1399981084744@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540628.1399981084744@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540628.1399981084744.19813.1399981136248@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNWCM-35:
---------------------------------

             Summary: Review String manipulation
                 Key: GTNWCM-35
                 URL: https://issues.jboss.org/browse/GTNWCM-35
             Project: GateIn WCM
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


GateIn WCM uses old style String manipulation.
There are some areas where StringBuilder can be applied to improve overall performance.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:32:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:32:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3443) Unknown Error when
 set header and footer visible during editing page
In-Reply-To: <JIRA.12537670.1397030891000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537670.1397030891000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537670.1397030891000.20010.1399984379775@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1085707|https://bugzilla.redhat.com/show_bug.cgi?id=1085707] from MODIFIED to ON_QA

> Unknown Error when set header and footer visible during editing page
> --------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3443
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3443
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: master head on commit:
> 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration                                                                                                                                       
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Unknown Error when setting portal to show footer and header portlets in preview mode during page editing. The page cannot be saved. Footer and other portlets (Banner, Navigation, Breadcumbs and Site Redirect) are shown correctly in the preview mode during page editing.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:00 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3470) Make permission
 defaults in page creation forms consistent
In-Reply-To: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539791.1399117226000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539791.1399117226000.20018.1399984380343@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1094154|https://bugzilla.redhat.com/show_bug.cgi?id=1094154] from MODIFIED to ON_QA

> Make permission defaults in page creation forms consistent
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3470
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3470
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions.
> The page creation forms for which this applies:
> I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page 
> II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page
> III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page
> For each of them, the defaults should be set as follows: 
> (1) For portal pages the access and edit permissions should be taken from the parent site.
> (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service.
> (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used.
> In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:32:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:32:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3451) Infinispan transport
 clusterName property not properly defined
In-Reply-To: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538760.1398172565000.20012.1399984379941@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1085927|https://bugzilla.redhat.com/show_bug.cgi?id=1085927] from MODIFIED to ON_QA

> Infinispan transport clusterName property not properly defined
> --------------------------------------------------------------
>
>                 Key: GTNPORTAL-3451
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3451
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> clusterName attribute is not well defined for infinispan transport defined in HA configurations.
> This bug shows followings warnings:
> [...]
> 14:47:59,283 WARN  [org.infinispan.util.StringPropertyReplacer] (MSC service thread 1-2) ISPN000003: Property infinispan-cluster-name could not be replaced as intended!
> [...]
> And this bug is root cause for other cascading errors in cluster setup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:00 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3442) portal-setup.sh/.bat
 scripts doesnt work with JBoss EAP 6.3.0 distribution
In-Reply-To: <JIRA.12537410.1396877045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537410.1396877045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537410.1396877045000.20016.1399984380199@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1084989|https://bugzilla.redhat.com/show_bug.cgi?id=1084989] from MODIFIED to ON_QA

> portal-setup.sh/.bat scripts doesnt work with JBoss EAP 6.3.0 distribution
> --------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3442
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3442
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:00 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3452) Changing permissions
 in ApplicationRegistry causes error
In-Reply-To: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538778.1398181740000.20014.1399984380078@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1089965|https://bugzilla.redhat.com/show_bug.cgi?id=1089965] from VERIFIED to ON_QA

> Changing permissions in ApplicationRegistry causes error
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-3452
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3452
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Changing permission of any portlet in Application Registry will cause "java.lang.Exception: Invalid Application Id: [web_slash_IFramePortlet]". 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:00 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:00 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3456) Update copyright text
 to use 2014 year
In-Reply-To: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538928.1398272542000.20020.1399984380638@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1089944|https://bugzilla.redhat.com/show_bug.cgi?id=1089944] from MODIFIED to ON_QA

> Update copyright text to use 2014 year
> --------------------------------------
>
>                 Key: GTNPORTAL-3456
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3456
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:01 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3460) Move Containers
 permission is not shown when using different languages
In-Reply-To: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539213.1398680460000.20023.1399984381217@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1091319|https://bugzilla.redhat.com/show_bug.cgi?id=1091319] from MODIFIED to ON_QA

> Move Containers permission is not shown when using different languages
> ----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3460
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3460
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Some i18n languages have long texts makes overflow some UI components in fixed layout.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:01 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3462) Missing
 javax.servlet.api dependency in org.jasig.cas.client module
In-Reply-To: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539228.1398689872000.20028.1399984381589@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1062155|https://bugzilla.redhat.com/show_bug.cgi?id=1062155] from MODIFIED to ON_QA

> Missing javax.servlet.api dependency in org.jasig.cas.client module
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3462
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3462
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.0.Final
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1062155



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:01 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:01 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3455) Select page layout
 doesn't select default item.
In-Reply-To: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538926.1398271160000.20026.1399984381435@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1090491|https://bugzilla.redhat.com/show_bug.cgi?id=1090491] from MODIFIED to ON_QA

> Select page layout doesn't select default item.
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3455
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3455
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> In step 2 of UIPageCreationWizard select page layout wizard doesn't select by default first element of each sublist.
> For example, if we change to row templates and we go to step 3, page layout is empty template instead two rows template.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951000.20033.1399984382026@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1091403|https://bugzilla.redhat.com/show_bug.cgi?id=1091403] from MODIFIED to ON_QA

> Node's external link values are not persisted after exporting site
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3468
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Description of problem:
> According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
> When you create external link for a node in navigation.xml, after import/export it is not persisted. 
> Steps to Reproduce:
> 1. Export site
> 2. Enter some property values into navigation.xml inside <node> element:
> {code:xml}
> <properties> 
>     <entry key="externalURI">http://google.com</entry> 
>     <entry key="openInNewWindow">true</entry> 
> </properties> 
> {code}
> 3. Import site into portal
> 4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons
	look like inverse
In-Reply-To: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534579.1394465062000.20036.1399984382539@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1076175|https://bugzilla.redhat.com/show_bug.cgi?id=1076175] from MODIFIED to ON_QA

> Disable users icons look like inverse
> -------------------------------------
>
>                 Key: GTNPORTAL-3417
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3417
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: 3.8.0.Beta01-SNAPSHOT
>            Reporter: Vlastislav Ramik
>            Assignee: Lucas Ponce
>              Labels: RHJP62
>             Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:03 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:03 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3449) Adding new node in
 group navigation doesn't work
In-Reply-To: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538736.1398157303000.20040.1399984382999@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1089460|https://bugzilla.redhat.com/show_bug.cgi?id=1089460] from VERIFIED to ON_QA

> Adding new node in group navigation doesn't work
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3449
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3449
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:33:02 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:33:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3453) domain.xml demo with
 default and full profiles
In-Reply-To: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538873.1398251581000.20038.1399984382777@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1090419|https://bugzilla.redhat.com/show_bug.cgi?id=1090419] from MODIFIED to ON_QA

> domain.xml demo with default and full profiles
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3453
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3453
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> demo-domain-setup.sh is a demo script to run gatein in domain mode.
> server-groups defined in domain.xml use full and full-ha profiles.
> For a better demo, these profiles should be default and full, to avoid to run a separate process with a tcp H2 database.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:34:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211000.20042.1399984497016@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1094163|https://bugzilla.redhat.com/show_bug.cgi?id=1094163] from MODIFIED to ON_QA

> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3469
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
> Not OK: The {{configuration.properties}} file ends with 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected: 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:34:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3444) "Invalid Application
 Id" thrown for all apps in Application Registry
In-Reply-To: <JIRA.12537691.1397047090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537691.1397047090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537691.1397047090000.20044.1399984497224@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1085792|https://bugzilla.redhat.com/show_bug.cgi?id=1085792] from MODIFIED to ON_QA

> "Invalid Application Id" thrown for all apps in Application Registry
> --------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3444
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3444
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: master, head on commit:
> 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> The following exception is logged when when clicking on any Application in Application Registry:
> Error during the processAction phase: java.lang.Exception: Invalid Application Id: [dashboard_slash_DashboardPortlet]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:34:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3454) Remove native AMD
 modules from requireJs config
In-Reply-To: <JIRA.12538878.1398255088000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538878.1398255088000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538878.1398255088000.20046.1399984497356@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Honza Fnukal <hfnukal at redhat.com> changed the Status of [bug 1090470|https://bugzilla.redhat.com/show_bug.cgi?id=1090470] from MODIFIED to ON_QA

> Remove native AMD modules from requireJs config
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3454
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3454
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> RequireJs config is a json structure renderead inline in the HTML markup of every page returned by the portal. The recent "Native AMD Support" feature has brought the possibility to work with large third-party javascript frameworks such as Dojo containing thousands of JavaScript modules. The present implementation adds an entry for every native AMD module into RequireJs config. With a dojo portlet deployed, this causes an overhead of more than 400KB per page.
> Steps to Reproduce:
> 1. Compile and deploy the dojo portlet application from https://github.com/ppalaga/dojo-portlet
> 2. Import applications
> 3. Inspect the source of any portal page, e.g. /portal/classic/home
> 4. Locate the line starting with
>   var require =
> Actual results: All dojo resources are there in the json structure assigned to the require variable.
> Expected results: No resources coming from Dojo should be there.
> Additional info: Not having the resources coming from Dojo in requireJS config is technically possible as the native AMD modules are implicitly SHARED and the baseUrl is set properly in the config.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:56:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:56:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an
 exception during deployment
In-Reply-To: <JIRA.12535425.1395244115000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535425.1395244115000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535425.1395244115000.20137.1399985818492@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

>  CDI portlet throws an exception during deployment
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3426
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3426
>             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.0.Beta01
>
>
> From Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1075588
> CDI portlet
> Any CDI portlet will currently this exception during deployment
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service
> You can find full stack trace here - http://pastebin.com/b8WYRrhy
> I am also enclosing one CDI portlet for easy reproduction.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Tue May 13 08:58:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:58:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3452) Changing permissions
 in ApplicationRegistry causes error
In-Reply-To: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538778.1398181740000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538778.1398181740000.20140.1399985936700@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Changing permissions in ApplicationRegistry causes error
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-3452
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3452
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Changing permission of any portlet in Application Registry will cause "java.lang.Exception: Invalid Application Id: [web_slash_IFramePortlet]". 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 08:58:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 08:58:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3449) Adding new node in
 group navigation doesn't work
In-Reply-To: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538736.1398157303000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538736.1398157303000.20142.1399985936829@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Adding new node in group navigation doesn't work
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3449
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3449
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 09:00:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 09:00:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3453) domain.xml demo with
 default and full profiles
In-Reply-To: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538873.1398251581000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538873.1398251581000.20144.1399986057672@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> domain.xml demo with default and full profiles
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3453
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3453
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> demo-domain-setup.sh is a demo script to run gatein in domain mode.
> server-groups defined in domain.xml use full and full-ha profiles.
> For a better demo, these profiles should be default and full, to avoid to run a separate process with a tcp H2 database.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 09:28:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 09:28:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3455) Select page layout
 doesn't select default item.
In-Reply-To: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538926.1398271160000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538926.1398271160000.20290.1399987737862@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Select page layout doesn't select default item.
> -----------------------------------------------
>
>                 Key: GTNPORTAL-3455
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3455
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> In step 2 of UIPageCreationWizard select page layout wizard doesn't select by default first element of each sublist.
> For example, if we change to row templates and we go to step 3, page layout is empty template instead two rows template.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 09:38:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 09:38:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3460) Move Containers
 permission is not shown when using different languages
In-Reply-To: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539213.1398680460000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539213.1398680460000.20313.1399988336662@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Move Containers permission is not shown when using different languages
> ----------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3460
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3460
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Some i18n languages have long texts makes overflow some UI components in fixed layout.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 10:08:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 10:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3443) Unknown Error when
 set header and footer visible during editing page
In-Reply-To: <JIRA.12537670.1397030891000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537670.1397030891000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537670.1397030891000.20391.1399990136937@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Unknown Error when set header and footer visible during editing page
> --------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3443
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3443
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: master head on commit:
> 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration                                                                                                                                       
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> Unknown Error when setting portal to show footer and header portlets in preview mode during page editing. The page cannot be saved. Footer and other portlets (Banner, Navigation, Breadcumbs and Site Redirect) are shown correctly in the preview mode during page editing.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 17:50:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 17:50:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons
	look like inverse
In-Reply-To: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534579.1394465062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534579.1394465062000.21599.1400017856579@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Disable users icons look like inverse
> -------------------------------------
>
>                 Key: GTNPORTAL-3417
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3417
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: 3.8.0.Beta01-SNAPSHOT
>            Reporter: Vlastislav Ramik
>            Assignee: Lucas Ponce
>              Labels: RHJP62
>             Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 17:52:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 13 May 2014 17:52:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3451) Infinispan transport
 clusterName property not properly defined
In-Reply-To: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538760.1398172565000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538760.1398172565000.21605.1400017976567@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Infinispan transport clusterName property not properly defined
> --------------------------------------------------------------
>
>                 Key: GTNPORTAL-3451
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3451
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> clusterName attribute is not well defined for infinispan transport defined in HA configurations.
> This bug shows followings warnings:
> [...]
> 14:47:59,283 WARN  [org.infinispan.util.StringPropertyReplacer] (MSC service thread 1-2) ISPN000003: Property infinispan-cluster-name could not be replaced as intended!
> [...]
> And this bug is root cause for other cascading errors in cluster setup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 05:03:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Wed, 14 May 2014 05:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3479) Errors importing
 GateIn Portal projects in Eclipse
In-Reply-To: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540558.1399910010000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540558.1399910010000.22568.1400058236575@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3479:
------------------------------------

    Assignee: Juraci Paix?o Kr?hling


> Errors importing GateIn Portal projects in Eclipse
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3479
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3479
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration
>         Environment: - Fedora 20
> - OpenJDK 1.7.0_51 (latest from Fedora 20)
> - JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93)
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> When trying to import "GateIn Portal" as an "Existing Maven Project" in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages:
> - "JBoss Core Portlet 2.0 requires Java 1.5 or newer"
> - "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer"
> Steps to reproduce:
> - Install JBoss Developer Studio with EAP
> - Import "Existing Maven Project", selecting the root of the GateIn clone (ex: https://github.com/jpkrohling/gatein-portal)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Thu May 15 05:27:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 15 May 2014 05:27:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.24769.1400146076495@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Boleslaw Dawidowicz <bdawidow at redhat.com> changed the Status of [bug 1096190|https://bugzilla.redhat.com/show_bug.cgi?id=1096190] from NEW to ASSIGNED

> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:plain}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 05:29:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 15 May 2014 05:29:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-376) Different Portlet
 preference for remote portlets added on the same page
In-Reply-To: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539955.1399380095000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539955.1399380095000.24779.1400146197314@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Boleslaw Dawidowicz <bdawidow at redhat.com> changed the Status of [bug 1094772|https://bugzilla.redhat.com/show_bug.cgi?id=1094772] from NEW to ASSIGNED

> Different Portlet preference for remote portlets added on the same page
> -----------------------------------------------------------------------
>
>                 Key: GTNWSRP-376
>                 URL: https://issues.jboss.org/browse/GTNWSRP-376
>             Project: GateIn WSRP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.11.Final
>         Environment: Tested with :
> JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5)  and 
> GateIn-3.8.0.Beta01
>            Reporter: Anurag Debnath
>            Assignee: Juraci Paix?o Kr?hling
>         Attachments: PortletPreferencesPortlet.war.zip
>
>
> When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well.
> Ideally, portlets should get their own preference/s.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Thu May 15 11:41:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Thu, 15 May 2014 11:41:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.25705.1400168517916@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3475:
------------------------------------

    Description: 
Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.

Steps to reproduce:
(1) Start clean Portal instance for the first time
(2) Go to Application Registry
(3) Import Applications

Not OK: There is an NPE logged (the whole log is attached):
{code:none}
Caused by: java.lang.NullPointerException
	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
{code}

Expected: No NPE

  was:
Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.

Steps to reproduce:
(1) Start clean Portal instance for the first time
(2) Go to Application Registry
(3) Import Applications

Not OK: There is an NPE logged (the whole log is attached):
{code:plain}
Caused by: java.lang.NullPointerException
	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
{code}

Expected: No NPE



> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 11:41:59 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Thu, 15 May 2014 11:41:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.25720.1400168519434@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga commented on GTNPORTAL-3475:
-----------------------------------------

Update:
The issue is reproducible only in Chrome. It is easy to reproduce it every time with a breakpoint in {{UIGroupMembershipSelector.processRender()}} there are two threads stopping at that breakpoint when working with Chrome.
Chrome sends two subsequent requests that look almost identical: 
{code:none}
http://127.0.0.1:8180/portal/g/:platform:administrators/administration/registry?portal:componentId=gtn7bc4a833-42ec-4be6-93dc-b376ca2531d0&interactionstate=JBPNS_rO0ABXdRAAJvcAAAAAEAFUltcG9ydEFsbEFwcGxpY2F0aW9ucwALdWljb21wb25lbnQAAAABABZVSUFwcGxpY2F0aW9uT3JnYW5pemVyAAdfX0VPRl9f&portal:type=action&ajaxRequest=true&_=1400167775387
http://127.0.0.1:8180/portal/g/:platform:administrators/administration/registry?portal:componentId=gtn7bc4a833-42ec-4be6-93dc-b376ca2531d0&interactionstate=JBPNS_rO0ABXdRAAJvcAAAAAEAFUltcG9ydEFsbEFwcGxpY2F0aW9ucwALdWljb21wb25lbnQAAAABABZVSUFwcGxpY2F0aW9uT3JnYW5pemVyAAdfX0VPRl9f&portal:type=action&ajaxRequest=true&_=1400167775418
{code}

> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 03:31:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 16 May 2014 03:31:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3456) Update copyright text
 to use 2014 year
In-Reply-To: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538928.1398272542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538928.1398272542000.26538.1400225516560@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1089944|https://bugzilla.redhat.com/show_bug.cgi?id=1089944] from ON_QA to VERIFIED

> Update copyright text to use 2014 year
> --------------------------------------
>
>                 Key: GTNPORTAL-3456
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3456
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 04:13:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Fri, 16 May 2014 04:13:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3481) Remove empty java
	class files
In-Reply-To: <JIRA.12540972.1400228011529@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540972.1400228011529@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540972.1400228011529.26564.1400228036657@jira02.app.mwc.hst.phx2.redhat.com>

Trong Tran created GTNPORTAL-3481:
-------------------------------------

             Summary: Remove empty java class files
                 Key: GTNPORTAL-3481
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3481
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Trong Tran
             Fix For: 3.9.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 04:17:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Fri, 16 May 2014 04:17:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3481) Remove empty java
	class files
In-Reply-To: <JIRA.12540972.1400228011000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540972.1400228011000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540972.1400228011000.26569.1400228276598@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3481:
----------------------------------

    Priority: Optional  (was: Major)


> Remove empty java class files
> -----------------------------
>
>                 Key: GTNPORTAL-3481
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3481
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>            Priority: Optional
>             Fix For: 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 04:21:57 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Fri, 16 May 2014 04:21:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3481) Remove empty java
	class files
In-Reply-To: <JIRA.12540972.1400228011000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540972.1400228011000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540972.1400228011000.26587.1400228517062@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran resolved GTNPORTAL-3481.
-----------------------------------

      Assignee: Trong Tran
    Resolution: Done


> Remove empty java class files
> -----------------------------
>
>                 Key: GTNPORTAL-3481
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3481
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>            Assignee: Trong Tran
>            Priority: Optional
>             Fix For: 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 04:43:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 16 May 2014 04:43:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3374) Submenu is displayed
 off the screen in right to left mode
In-Reply-To: <JIRA.12529885.1390233114000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529885.1390233114000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529885.1390233114000.26637.1400229836768@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Filip Kiss <fkiss at redhat.com> changed the Status of [bug 1053019|https://bugzilla.redhat.com/show_bug.cgi?id=1053019] from ON_QA to VERIFIED

> Submenu is displayed off the screen in right to left mode
> ---------------------------------------------------------
>
>                 Key: GTNPORTAL-3374
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3374
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Mobile
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>            Priority: Minor
>             Fix For: 3.7.0.Final, 3.6.5.Final
>
>
> Description of problem:
> On tablet devices there is menu displayed off the screen when you are in Right to left mode. Go to /portal/mobile/home and click: Group pages -> User pages -> My link -> submenu is displayed off the screen. This only happens in landscape mode. See attached screenshot.
> Additional info:
> Tested on Android 3.2 tablet and 4.1.2 tablet. Phones worked fine.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 05:17:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 16 May 2014 05:17:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3468) Node's external link
 values are not persisted after exporting site
In-Reply-To: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539705.1399031951000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539705.1399031951000.26677.1400231876298@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Filip Kiss <fkiss at redhat.com> changed the Status of [bug 1091403|https://bugzilla.redhat.com/show_bug.cgi?id=1091403] from ON_QA to VERIFIED

> Node's external link values are not persisted after exporting site
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3468
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3468
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Description of problem:
> According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937
> When you create external link for a node in navigation.xml, after import/export it is not persisted. 
> Steps to Reproduce:
> 1. Export site
> 2. Enter some property values into navigation.xml inside <node> element:
> {code:xml}
> <properties> 
>     <entry key="externalURI">http://google.com</entry> 
>     <entry key="openInNewWindow">true</entry> 
> </properties> 
> {code}
> 3. Import site into portal
> 4. When you are exporting the same site again - property values are not persisted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 08:15:58 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 16 May 2014 08:15:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.26943.1400242558473@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga commented on GTNPORTAL-3475:
-----------------------------------------

The two requests are sent only if my Chrome extension (1) is active. When I disable it, there is only one request sent. The extension used to work without problems before, so it is maybe a bug in the current Chrome version.

But anyway, given that two concurrent requests are possible by design of WebUI, this needs to be fixed in {{UIGroupMembershipSelector}}. The second concurrent request can theoretically also come from some other source, say a browser refresh (combined with an overloaded server) or similar. So, I am going to fix this in UIGroupMembershipSelector through loading listMemberhip in a thread-safe manner.

(1) https://github.com/ppalaga/misc-content-scripts

> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 09:07:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 16 May 2014 09:07:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.27032.1400245676449@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3475:
------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/854


> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 10:53:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 16 May 2014 10:53:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.27358.1400252036606@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1096190|https://bugzilla.redhat.com/show_bug.cgi?id=1096190] from ASSIGNED to POST

> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 04:08:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 19 May 2014 04:08:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3482) Deprecated class of
	UserImpl
In-Reply-To: <JIRA.12541070.1400486823967@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541070.1400486823967@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541070.1400486823967.28649.1400486936465@jira02.app.mwc.hst.phx2.redhat.com>

Tuyen Nguyen The created GTNPORTAL-3482:
-------------------------------------------

             Summary: Deprecated class of UserImpl
                 Key: GTNPORTAL-3482
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3482
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Tuyen Nguyen The
            Assignee: Tuyen Nguyen The
            Priority: Minor


*org.exoplatform.services.organization.idm.UserImpl* class was created in order to make a workaround to display the *userName* if exist.

This class should be *deleted* in Gatein according to a *TODO* annotation mentioned in top. In fact, the related issue *was fixed* in JCR 1.15, see:
https://issues.jboss.org/browse/EXOJCR-1780.
 
the correction was made into the class *org.exoplatform.services.organization.impl.UserImpl* on method getFullName (responsible for displaying the username)
{code:title=UserImpl.java|borderStyle=solid}
// wrapper method
   public String getFullName()
   {
      return getDisplayName();
   }

public String getDisplayName()
   {
      return displayName != null ? displayName : getFirstName() + " " + getLastName();
   }
{code} 
So no need to  *...organization.idm.UserImpl* class any more as the class *org.exoplatform.services.organization.impl.UserImpl* was fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 04:52:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Mon, 19 May 2014 04:52:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3482) Deprecated class of
	UserImpl
In-Reply-To: <JIRA.12541070.1400486823000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541070.1400486823000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541070.1400486823000.28752.1400489576350@jira02.app.mwc.hst.phx2.redhat.com>


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

Tuyen Nguyen The updated GTNPORTAL-3482:
----------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/855


> Deprecated class of UserImpl
> ----------------------------
>
>                 Key: GTNPORTAL-3482
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3482
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>
> *org.exoplatform.services.organization.idm.UserImpl* class was created in order to make a workaround to display the *userName* if exist.
> This class should be *deleted* in Gatein according to a *TODO* annotation mentioned in top. In fact, the related issue *was fixed* in JCR 1.15, see:
> https://issues.jboss.org/browse/EXOJCR-1780.
>  
> the correction was made into the class *org.exoplatform.services.organization.impl.UserImpl* on method getFullName (responsible for displaying the username)
> {code:title=UserImpl.java|borderStyle=solid}
> // wrapper method
>    public String getFullName()
>    {
>       return getDisplayName();
>    }
> public String getDisplayName()
>    {
>       return displayName != null ? displayName : getFirstName() + " " + getLastName();
>    }
> {code} 
> So no need to  *...organization.idm.UserImpl* class any more as the class *org.exoplatform.services.organization.impl.UserImpl* was fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:30:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:30:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.28817.1400491856611@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda commented on GTNSSO-28:
-------------------------------------

yes, you're right. This was needed for OpenAM 9 and 10, which are currently supported versions. For OpenAM 11, you can either workaround and build gatein-sso in your environment,  or if you have time, you can send PR with more proper fix, which will work in both OpenAM 9,10 and 11 . I think proper fix will need to add another init parameter (either with OpenAM version or name of the realm for ProviderID part).

For build gatein-sso, you just need java 6 (or later) and maven 3.0.3 (or later) and run just "mvn clean install" from "gatein-sso" directory. If it doesn't work, feel free to create another JIRA and please attach details about your environment (java version, maven version, OS etc).

> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>            Priority: Blocker
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:30:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:30:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.28819.1400491856757@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-28:
--------------------------------

    Priority: Major  (was: Blocker)


> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:34:57 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-18) Investigate Picketlink
 federation WARNINGS during GateIn as IDP setup
In-Reply-To: <JIRA.12477035.1350339326000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12477035.1350339326000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12477035.1350339326000.28826.1400492097550@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-18:
--------------------------------

    Fix Version/s: 1.4.2.Final
                       (was: 1.4.1.Final)


> Investigate Picketlink federation WARNINGS during GateIn as IDP setup
> ---------------------------------------------------------------------
>
>                 Key: GTNSSO-18
>                 URL: https://issues.jboss.org/browse/GTNSSO-18
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.3.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.2.Final
>
>
> There are some WARNs from picketlink federation when having GateIn as SAML2 IDP. It doesn't break functionality, but needs to be investigated if everything is ok in configuration.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:34:57 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-16) Callback support for JOSSO
	2.2
In-Reply-To: <JIRA.12477002.1350316489000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12477002.1350316489000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12477002.1350316489000.28827.1400492097649@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-16:
--------------------------------

    Fix Version/s: 1.4.2.Final
                       (was: 1.4.1.Final)


> Callback support for JOSSO 2.2
> ------------------------------
>
>                 Key: GTNSSO-16
>                 URL: https://issues.jboss.org/browse/GTNSSO-16
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.3.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.2.Final
>
>
> It's defacto working, but setup is quite complicated for SSO users. Revisit this later and check if it could be simplified.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:34:57 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-11) Remove SPNEGO workarounds
 needed for SECURITY-695 and SECURITY-696
In-Reply-To: <JIRA.12474983.1348147571000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12474983.1348147571000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12474983.1348147571000.28828.1400492097731@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-11:
--------------------------------

    Fix Version/s: 1.4.2.Final
                       (was: 1.4.1.Final)


> Remove SPNEGO workarounds needed for SECURITY-695 and SECURITY-696
> ------------------------------------------------------------------
>
>                 Key: GTNSSO-11
>                 URL: https://issues.jboss.org/browse/GTNSSO-11
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.2.0-Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.2.Final
>
>
> After upgrade to jboss-negotiation 2.2.2.Final we need to remove workaround in SPNEGOLoginModule (just left method getIdentityForSubject and remove others)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:34:57 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-8) Unit tests
In-Reply-To: <JIRA.12461101.1331226582000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12461101.1331226582000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12461101.1331226582000.28829.1400492097798@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-8:
-------------------------------

    Fix Version/s: 1.4.2.Final
                       (was: 1.4.1.Final)


> Unit tests
> ----------
>
>                 Key: GTNSSO-8
>                 URL: https://issues.jboss.org/browse/GTNSSO-8
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.1.1-GA
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.2.Final
>
>
> Current support of unit tests is not good. There are couple of dummy unit tests, but they are disabled as they require server to be running before running tests. It will be needed to provide integration with some well-known solution (Arquillian, Cargo, JBoss unit...) and provide more unit tests for SSO component.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 05:34:57 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Mon, 19 May 2014 05:34:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.28831.1400492097926@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-28:
--------------------------------

    Fix Version/s: 1.4.2.Final


> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>             Fix For: 1.4.2.Final
>
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 07:06:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Mon, 19 May 2014 07:06:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase
 are order dependent
In-Reply-To: <JIRA.12541101.1400497517051@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541101.1400497517051@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541101.1400497517051.29009.1400497616454@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNMOP-54:
----------------------------------

             Summary: Tests in WorkspaceTestCase are order dependent
                 Key: GTNMOP-54
                 URL: https://issues.jboss.org/browse/GTNMOP-54
             Project: GateIn Model Object for Portal
          Issue Type: Bug
            Reporter: Peter Palaga
            Assignee: Peter Palaga


Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114
Description of problem:
Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). 

Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=1.3.1.Final-redhat-1) has test dependency junit-4.11-redhat-1.jar. 

There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#test-execution-order

Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites

Version-Release number of selected component (if applicable):
community MOP: 1.3.1.Final with junit 4.10
prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1

Additional info:
When I declare junit version to 4.11 in community project I get the errors.
When I declare junit version to 4.10-redhat-2 in prod project all tests passed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 07:06:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 19 May 2014 07:06:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase
 are order dependent
In-Reply-To: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541101.1400497517000.29011.1400497616618@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNMOP-54:
------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1091114


> Tests in WorkspaceTestCase are order dependent
> ----------------------------------------------
>
>                 Key: GTNMOP-54
>                 URL: https://issues.jboss.org/browse/GTNMOP-54
>             Project: GateIn Model Object for Portal
>          Issue Type: Bug
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114
> Description of problem:
> Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). 
> Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=1.3.1.Final-redhat-1) has test dependency junit-4.11-redhat-1.jar. 
> There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#test-execution-order
> Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites
> Version-Release number of selected component (if applicable):
> community MOP: 1.3.1.Final with junit 4.10
> prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1
> Additional info:
> When I declare junit version to 4.11 in community project I get the errors.
> When I declare junit version to 4.10-redhat-2 in prod project all tests passed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 09:40:57 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 19 May 2014 09:40:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-35) Review String manipulation
In-Reply-To: <JIRA.12540628.1399981084000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540628.1399981084000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540628.1399981084000.29525.1400506857009@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce resolved GTNWCM-35.
-------------------------------

    Resolution: Done


> Review String manipulation
> --------------------------
>
>                 Key: GTNWCM-35
>                 URL: https://issues.jboss.org/browse/GTNWCM-35
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> GateIn WCM uses old style String manipulation.
> There are some areas where StringBuilder can be applied to improve overall performance.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 09:42:57 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 19 May 2014 09:42:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-35) Review String manipulation
In-Reply-To: <JIRA.12540628.1399981084000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540628.1399981084000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540628.1399981084000.29534.1400506977171@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNWCM-35:
------------------------------

        Fix Version/s: 2.x
    Affects Version/s: 2.x


> Review String manipulation
> --------------------------
>
>                 Key: GTNWCM-35
>                 URL: https://issues.jboss.org/browse/GTNWCM-35
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.x
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 2.x
>
>
> GateIn WCM uses old style String manipulation.
> There are some areas where StringBuilder can be applied to improve overall performance.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 13:40:58 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 19 May 2014 13:40:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-36) Support for self-closing
 wcm tags in templates
In-Reply-To: <JIRA.12541158.1400521239790@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541158.1400521239790@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541158.1400521239790.30267.1400521258354@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNWCM-36:
---------------------------------

             Summary: Support for self-closing wcm tags in templates
                 Key: GTNWCM-36
                 URL: https://issues.jboss.org/browse/GTNWCM-36
             Project: GateIn WCM
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 13:52:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 19 May 2014 13:52:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-36) Support for self-closing
 wcm tags in templates
In-Reply-To: <JIRA.12541158.1400521239000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541158.1400521239000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541158.1400521239000.30296.1400521976340@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce resolved GTNWCM-36.
-------------------------------

    Fix Version/s: 2.x
       Resolution: Done


> Support for self-closing wcm tags in templates
> ----------------------------------------------
>
>                 Key: GTNWCM-36
>                 URL: https://issues.jboss.org/browse/GTNWCM-36
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 2.x
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:18:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:18:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3483) Improvements for WCM
 Editor error messages
In-Reply-To: <JIRA.12541198.1400573818737@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541198.1400573818737@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541198.1400573818737.30936.1400573936379@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3483:
--------------------------------------

             Summary: Improvements for WCM Editor error messages
                 Key: GTNPORTAL-3483
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3483
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


WCM Editor can show better meaningful messages.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:30:58 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:30:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3483) Improvements for WCM
 Editor error messages
In-Reply-To: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541198.1400573818000.30975.1400574658738@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce closed GTNPORTAL-3483.
----------------------------------

    Resolution: Done


This JIRA is created under GTNPORTAL project instead GTNWCM.

> Improvements for WCM Editor error messages
> ------------------------------------------
>
>                 Key: GTNPORTAL-3483
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3483
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> WCM Editor can show better meaningful messages.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:32:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:32:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-37) Improvements for WCM
	Editor error messages
In-Reply-To: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541198.1400573818000.30976.1400574776258@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce moved GTNPORTAL-3483 to GTNWCM-37:
----------------------------------------------

    Project: GateIn WCM  (was: GateIn Portal)
        Key: GTNWCM-37  (was: GTNPORTAL-3483)


> Improvements for WCM Editor error messages
> ------------------------------------------
>
>                 Key: GTNWCM-37
>                 URL: https://issues.jboss.org/browse/GTNWCM-37
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> WCM Editor can show better meaningful messages.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:32:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:32:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-37) Improvements for WCM
	Editor error messages
In-Reply-To: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541198.1400573818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541198.1400573818000.30977.1400574776312@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce reopened GTNWCM-37:
-------------------------------



> Improvements for WCM Editor error messages
> ------------------------------------------
>
>                 Key: GTNWCM-37
>                 URL: https://issues.jboss.org/browse/GTNWCM-37
>             Project: GateIn WCM
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> WCM Editor can show better meaningful messages.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:46:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 20 May 2014 04:46:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3435) Import .zip REST API
 broken with EAP 6.3.0.Alpha1
In-Reply-To: <JIRA.12536480.1396020937000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536480.1396020937000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536480.1396020937000.31022.1400575618489@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Import .zip REST API broken with EAP 6.3.0.Alpha1
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3435
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3435
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>         Attachments: jbossweb-7.4.1.Final.jar, portal_classic_2014-03-28_16-59-29.zip
>
>
> A curl operation over template/user API:
> curl -i -H "Content-Type: application/zip" -u root:gtn -X PUT -T examples/user.zip "http://localhost:8080/rest/private/managed-components/template/user"
> hangs with:
> 16:35:16,466 INFO  [org.exoplatform.portal.mop.management.operations.TemplateImportResource] (http-/127.0.0.1:8080-4) Import successful !
> 16:35:16,475 ERROR [org.apache.catalina.connector] (http-/127.0.0.1:8080-4) JBWEB001018: An exception or error occurred in the container during the request processing: java.nio.BufferOverflowException
>         at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:357) [rt.jar:1.7.0_25]
>         at org.apache.coyote.http11.InternalNioOutputBuffer.commit(InternalNioOutputBuffer.java:666) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.commit(Http11NioProcessor.java:480) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.action(Http11NioProcessor.java:798) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.Response.action(Response.java:190) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.Response.sendHeaders(Response.java:390) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:352) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:318) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.Response.finishResponse(Response.java:487) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:371) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
>         at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:52:58 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:52:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908709@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908709@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908709.31044.1400575978078@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3484:
--------------------------------------

             Summary: Commit changes for a page before send response
                 Key: GTNPORTAL-3484
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.

This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:56:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 20 May 2014 04:56:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908000.31059.1400576216627@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3484:
-----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/856


> Commit changes for a page before send response
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3484
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.
> This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:56:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 20 May 2014 04:56:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908000.31061.1400576216757@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3484:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080249


> Commit changes for a page before send response
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3484
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.
> This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 05:16:58 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Tue, 20 May 2014 05:16:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3485) Add an option to load
 AMD JavaScript from a CDN
In-Reply-To: <JIRA.12541211.1400577402995@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541211.1400577402995@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541211.1400577402995.31108.1400577418242@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3485:
---------------------------------------

             Summary: Add an option to load AMD JavaScript from a CDN
                 Key: GTNPORTAL-3485
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3485
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 05:28:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Tue, 20 May 2014 05:28:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3486) redirect to /dologin
 instead of /login when user access to page that require login
In-Reply-To: <JIRA.12541214.1400578046788@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541214.1400578046788@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541214.1400578046788.31127.1400578136218@jira02.app.mwc.hst.phx2.redhat.com>

Tuyen Nguyen The created GTNPORTAL-3486:
-------------------------------------------

             Summary: redirect to /dologin instead of /login when user access to page that require login
                 Key: GTNPORTAL-3486
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3486
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Tuyen Nguyen The
            Assignee: Tuyen Nguyen The


When i configure SPNEGO SSO for Gatein,
It work ok when i login with "login" link at top navigation bar. But when i try to access to page that rerquire login, (for example http://server.local.network:8080/portal/g/:platform:administrators/administration/registry), it will redirect to /login and i will not be logged in automatically with SPNEGO because spnego only work when it redirect to /dologin

I see that both /login and /dologin are mapping with LoginServlet and they always have the same behaviours.

So, i think we should redirect to /dologin instead of /login when user access to page that require login



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 05:32:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Tue, 20 May 2014 05:32:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3486) redirect to /dologin
 instead of /login when user access to page that require login
In-Reply-To: <JIRA.12541214.1400578046000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541214.1400578046000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541214.1400578046000.31128.1400578376263@jira02.app.mwc.hst.phx2.redhat.com>


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

Tuyen Nguyen The updated GTNPORTAL-3486:
----------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/857


> redirect to /dologin instead of /login when user access to page that require login
> ----------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3486
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3486
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>
> When i configure SPNEGO SSO for Gatein,
> It work ok when i login with "login" link at top navigation bar. But when i try to access to page that rerquire login, (for example http://server.local.network:8080/portal/g/:platform:administrators/administration/registry), it will redirect to /login and i will not be logged in automatically with SPNEGO because spnego only work when it redirect to /dologin
> I see that both /login and /dologin are mapping with LoginServlet and they always have the same behaviours.
> So, i think we should redirect to /dologin instead of /login when user access to page that require login



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:56:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Wed, 21 May 2014 09:56:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3487) Add an option to load
	CSS from a CDN
In-Reply-To: <JIRA.12541386.1400680523775@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541386.1400680523775@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541386.1400680523775.34044.1400680616730@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3487:
---------------------------------------

             Summary: Add an option to load CSS from a CDN
                 Key: GTNPORTAL-3487
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3487
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


Loading CSS from an external URL is not possible ATM. This a task similar to GTNPORTAL-3485.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 12:30:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Wed, 21 May 2014 12:30:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWCM-38) Export / Import
In-Reply-To: <JIRA.12541420.1400689767881@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541420.1400689767881@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541420.1400689767881.34419.1400689856695@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNWCM-38:
---------------------------------

             Summary: Export / Import
                 Key: GTNWCM-38
                 URL: https://issues.jboss.org/browse/GTNWCM-38
             Project: GateIn WCM
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


Add a export / import tool that can handle content in a bundle.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 05:10:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 22 May 2014 05:10:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2581) RichFaces is not
 defined after adding a RF portlet to a page
In-Reply-To: <JIRA.12474884.1348062188000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12474884.1348062188000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12474884.1348062188000.35608.1400749857151@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Boleslaw Dawidowicz <bdawidow at redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from ASSIGNED to POST

> RichFaces is not defined after adding a RF portlet to a page
> ------------------------------------------------------------
>
>                 Key: GTNPORTAL-2581
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2581
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: GateIn 3.4.0.Final
>            Reporter: Peter Palaga
>         Attachments: jsf2-rf4-hello-world-portlet.war
>
>
> (1) Start a fresh GateIn 3.4.0.Final:
> cd tmp
> wget http://downloads.jboss.org/gatein/Releases/Portal/3.4.0.Final/GateIn-3.4.0.Final-jbossas7.zip 
> unzip GateIn-3.4.0.Final-jbossas7.zip
> cd GateIn-3.4.0.Final-jbossas7/bin
> ./standalone.sh
> (2) Install gatein-bom-3.4
> git clone https://github.com/ppalaga/gatein-bom.github
> cd gatein-bom
> mvn install -Dgpg.skip=true
> (3) Pack and deploy jsf2-rf4-hello-world-portlet:
> cd tmp
> git clone https://github.com/ppalaga/gatein-portal-quickstart.git
> cd gatein-portal-quickstart/jsf2-rf4-hello-world-portlet
> mvn package jboss-as:deploy
> (4)  In web browser:
> * login as root http://127.0.0.1:8080/portal/login?username=root&password=gtn&initialURI=/portal/classic/
> (5) In web browser:
> * Group > Administration > Application Registry > Import Applications
> * Site > Classic > Home
> * Site Editor > Edit Page
> * Drag jsf2-rf4-hello-world-portlet and drop it e.g. under the Home Page portlet
> * make the console with server log visible to you
> * Open developer tools (F12 in Chrome) and switch to Resources. Have a look at loaded scripts. Note that there are no PBR-related scripts there.
> (6) Hit Finish (Diskette Icon) in Page Editor dialog
> (7) UNEXPECTED: After hitting Finish, there comes a modal message in the browser window saying "RichFaces is not defined". 
> * Note that while this message is being displayed, there is no change in the scripts compared to before (5).
> * Note that nothing happened in the server log.
>  
> (8) Hit OK in the "RichFaces is not defined" alert.
> * Note that one or more PBR-related scripts were loaded. Some of them have error markers in them
> * Sometimes one or more org.exoplatform.portal.config.NoSuchDataExceptions appear in the server log
>  
> The problem seems to be related to the fact that the inline JavaScript needed to render the rich:select component is evaluated before the needed js resources were loaded. After reloading the whole page or accessing the page from another session jsf2-rf4-hello-world-portlet works as expected. 
> For further observations, define one more step:
> (9)
> * Site > Classic > Home
> * Site Editor > Edit Page
> * remove jsf2-rf4-hello-world-portlet from the page
> * Hit Finish (Diskette Icon) in Page Editor dialog
> When in the state after (8), one performs (9) and then again (5) and (6), "RichFaces is not defined" does not appear.
> "RichFaces is not defined" appears only when one signs out from the portal and signs in again between (9) and (5) of the previous scenario.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 05:10:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 22 May 2014 05:10:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908000.35610.1400749857351@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Boleslaw Dawidowicz <bdawidow at redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from ASSIGNED to POST

> Commit changes for a page before send response
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3484
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>
> In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.
> This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 14:00:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 22 May 2014 14:00:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNCOMMON-21) Serialization of
 ParameterMap breaks with JBoss Marshalling
In-Reply-To: <JIRA.12530365.1390813730000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530365.1390813730000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530365.1390813730000.37374.1400781658226@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GTNCOMMON-21:
--------------------------------------------------

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1058216|https://bugzilla.redhat.com/show_bug.cgi?id=1058216] from ON_QA to ASSIGNED

> Serialization of ParameterMap breaks with JBoss Marshalling
> -----------------------------------------------------------
>
>                 Key: GTNCOMMON-21
>                 URL: https://issues.jboss.org/browse/GTNCOMMON-21
>             Project: GateIn Common
>          Issue Type: Bug
>    Affects Versions: 2.1.1.Final
>         Environment: JPP 6.1.0
>            Reporter: Martin Weiler
>             Fix For: 2.2.0.Beta01, 2.1.2.Final
>
>
> Serialization of a ParameterMap instance with JBoss Marshalling (used by Infinispan) breaks with the following exception:
> {noformat}
> 15:20:33,853 ERROR [org.infinispan.marshall.VersionAwareMarshaller] (transport-thread-11) ISPN000065: Exception while marshalling object: java.io.NotActiveException: Fields were never written
> 	at org.jboss.marshalling.river.RiverObjectOutputStream.finish(RiverObjectOutputStream.java:175)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1009)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:680)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:680)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.jboss.as.clustering.SimpleMarshalledValue.getBytes(SimpleMarshalledValue.java:85)
> 	at org.jboss.as.clustering.SimpleMarshalledValue.writeExternal(SimpleMarshalledValue.java:175)
> 	at org.jboss.as.clustering.infinispan.io.ExternalizableExternalizer.writeObject(ExternalizableExternalizer.java:47)
> 	at org.jboss.as.clustering.infinispan.io.ExternalizableExternalizer.writeObject(ExternalizableExternalizer.java:36)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ForeignExternalizerAdapter.writeObject(ExternalizerTable.java:459)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.marshall.MarshallUtil.marshallMap(MarshallUtil.java:59)
> 	at org.infinispan.marshall.exts.MapExternalizer.writeObject(MapExternalizer.java:63)
> 	at org.infinispan.marshall.exts.MapExternalizer.writeObject(MapExternalizer.java:47)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.atomic.AtomicHashMap$Externalizer.writeObject(AtomicHashMap.java:250)
> 	at org.infinispan.atomic.AtomicHashMap$Externalizer.writeObject(AtomicHashMap.java:247)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.container.entries.ImmortalCacheEntry$Externalizer.writeObject(ImmortalCacheEntry.java:154)
> 	at org.infinispan.container.entries.ImmortalCacheEntry$Externalizer.writeObject(ImmortalCacheEntry.java:150)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.marshall.MarshallUtil.marshallCollection(MarshallUtil.java:48)
> 	at org.infinispan.marshall.exts.ArrayListExternalizer.writeObject(ArrayListExternalizer.java:50)
> 	at org.infinispan.marshall.exts.ArrayListExternalizer.writeObject(ArrayListExternalizer.java:45)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.statetransfer.StateChunk$Externalizer.writeObject(StateChunk.java:103)
> 	at org.infinispan.statetransfer.StateChunk$Externalizer.writeObject(StateChunk.java:88)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.marshall.MarshallUtil.marshallCollection(MarshallUtil.java:48)
> 	at org.infinispan.marshall.exts.ArrayListExternalizer.writeObject(ArrayListExternalizer.java:50)
> 	at org.infinispan.marshall.exts.ArrayListExternalizer.writeObject(ArrayListExternalizer.java:45)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.marshall.exts.ReplicableCommandExternalizer.writeCommandParameters(ReplicableCommandExternalizer.java:87)
> 	at org.infinispan.marshall.exts.CacheRpcCommandExternalizer.marshallParameters(CacheRpcCommandExternalizer.java:128)
> 	at org.infinispan.marshall.exts.CacheRpcCommandExternalizer.writeObject(CacheRpcCommandExternalizer.java:112)
> 	at org.infinispan.marshall.exts.CacheRpcCommandExternalizer.writeObject(CacheRpcCommandExternalizer.java:73)
> 	at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.writeObject(ExternalizerTable.java:410)
> 	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:145)
> 	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
> 	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
> 	at org.infinispan.marshall.jboss.AbstractJBossMarshaller.objectToObjectStream(AbstractJBossMarshaller.java:96)
> 	at org.infinispan.marshall.VersionAwareMarshaller.objectToBuffer(VersionAwareMarshaller.java:92)
> 	at org.infinispan.marshall.AbstractMarshaller.objectToBuffer(AbstractMarshaller.java:64)
> 	at org.infinispan.marshall.AbstractDelegatingMarshaller.objectToBuffer(AbstractDelegatingMarshaller.java:109)
> 	at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectToBuffer(MarshallerAdapter.java:45)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.marshallCall(CommandAwareRpcDispatcher.java:279)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:300)
> 	at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:179)
> 	at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515)
> 	at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:169)
> 	at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:190)
> 	at org.infinispan.statetransfer.OutboundTransferTask.sendEntries(OutboundTransferTask.java:257)
> 	at org.infinispan.statetransfer.OutboundTransferTask.run(OutboundTransferTask.java:187)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: an exception which occurred:
> 	in field parameters
> 	in field navigationalState
> 	in object java.util.HashMap at 7b2c68fe
> {noformat}
> The NotActiveException is a result of a broken writeObject implementation in org.gatein.common.util.ParameterMap, which does not call out.defaultWriteObject();



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 14:50:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 22 May 2014 14:50:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3462) Missing
 javax.servlet.api dependency in org.jasig.cas.client module
In-Reply-To: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539228.1398689872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539228.1398689872000.37483.1400784656646@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1062155|https://bugzilla.redhat.com/show_bug.cgi?id=1062155] from ON_QA to VERIFIED

> Missing javax.servlet.api dependency in org.jasig.cas.client module
> -------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3462
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3462
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 3.8.0.Final
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1062155



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 23:36:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Thu, 22 May 2014 23:36:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3486) Redirect to /sso
 instead of /login when SSO is enabled
In-Reply-To: <JIRA.12541214.1400578046000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541214.1400578046000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541214.1400578046000.38261.1400816216347@jira02.app.mwc.hst.phx2.redhat.com>


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

Tuyen Nguyen The updated GTNPORTAL-3486:
----------------------------------------

        Summary: Redirect to /sso instead of /login when SSO is enabled  (was: redirect to /dologin instead of /login when user access to page that require login)
    Description: 
When i configure SPNEGO SSO for Gatein,
It work ok when i login with "login" link at top navigation bar. But when i try to access to page that rerquire login, (for example http://server.local.network:8080/portal/g/:platform:administrators/administration/registry), it will redirect to /login and i will not be logged in automatically with SPNEGO because spnego only work when it redirect to /dologin

I think when SSO is enabled, we should redirect to /sso instead of /login when user try to access page that require login, then SSO will redirect to loginURL which was configured. 
It's similar that we change link of "login" at top navigation bar to /sso when SSO is enabled. 

  was:
When i configure SPNEGO SSO for Gatein,
It work ok when i login with "login" link at top navigation bar. But when i try to access to page that rerquire login, (for example http://server.local.network:8080/portal/g/:platform:administrators/administration/registry), it will redirect to /login and i will not be logged in automatically with SPNEGO because spnego only work when it redirect to /dologin

I see that both /login and /dologin are mapping with LoginServlet and they always have the same behaviours.

So, i think we should redirect to /dologin instead of /login when user access to page that require login



> Redirect to /sso instead of /login when SSO is enabled
> ------------------------------------------------------
>
>                 Key: GTNPORTAL-3486
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3486
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>
> When i configure SPNEGO SSO for Gatein,
> It work ok when i login with "login" link at top navigation bar. But when i try to access to page that rerquire login, (for example http://server.local.network:8080/portal/g/:platform:administrators/administration/registry), it will redirect to /login and i will not be logged in automatically with SPNEGO because spnego only work when it redirect to /dologin
> I think when SSO is enabled, we should redirect to /sso instead of /login when user try to access page that require login, then SSO will redirect to loginURL which was configured. 
> It's similar that we change link of "login" at top navigation bar to /sso when SSO is enabled. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 04:28:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Fri, 23 May 2014 04:28:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3488) ERROR | Could not
 render css
 /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
 when client abort
In-Reply-To: <JIRA.12541674.1400833710161@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541674.1400833710161@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541674.1400833710161.38447.1400833736461@jira02.app.mwc.hst.phx2.redhat.com>

Tuyen Nguyen The created GTNPORTAL-3488:
-------------------------------------------

             Summary: ERROR | Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css when client abort
                 Key: GTNPORTAL-3488
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3488
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Tuyen Nguyen The
            Assignee: Tuyen Nguyen The


Case to reproduce:
- Duplicate content of css file: $GATEIN_TOMCAT/webapps/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css (make it contain many css define)
- Run gatein
- Goto homepage
- Goto http://localhost:8080/portal/skins/3.9.0.Alpha01-SNAPSHOT/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin-lt.css
- Press and keep the keyboard Ctrl+R to multi reload page
- Have many exception *ERROR* on console.
{code}
[http-bio-8080-exec-4] ERROR org.exoplatform.portal.resource.SkinResourceRequestHandler - Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
ClientAbortException:  java.net.SocketException: Broken pipe
	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388)
	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413)
	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401)
	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:84)
	at org.exoplatform.portal.resource.SkinResourceRequestHandler$1.write(SkinResourceRequestHandler.java:74)
	at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:465)
	at org.exoplatform.portal.resource.SkinResourceRequestHandler.execute(SkinResourceRequestHandler.java:101)
	at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72)
	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92)
	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122)
	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
	at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:371)
	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:240)
	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:119)
	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:192)
	at org.apache.coyote.Response.doWrite(Response.java:505)
	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383)
	... 68 more
{code}

For this broken pipe exception, we should catch up the exception and keep it silent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 04:58:56 2014
From: issues at jboss.org (Tuyen Nguyen The (JIRA))
Date: Fri, 23 May 2014 04:58:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3488) ERROR | Could not
 render css
 /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
 when client abort
In-Reply-To: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541674.1400833710000.38595.1400835536655@jira02.app.mwc.hst.phx2.redhat.com>


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

Tuyen Nguyen The updated GTNPORTAL-3488:
----------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/858


> ERROR | Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css when client abort
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3488
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3488
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>
> Case to reproduce:
> - Duplicate content of css file: $GATEIN_TOMCAT/webapps/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css (make it contain many css define)
> - Run gatein
> - Goto homepage
> - Goto http://localhost:8080/portal/skins/3.9.0.Alpha01-SNAPSHOT/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin-lt.css
> - Press and keep the keyboard Ctrl+R to multi reload page
> - Have many exception *ERROR* on console.
> {code}
> [http-bio-8080-exec-4] ERROR org.exoplatform.portal.resource.SkinResourceRequestHandler - Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
> ClientAbortException:  java.net.SocketException: Broken pipe
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388)
> 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
> 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413)
> 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:84)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler$1.write(SkinResourceRequestHandler.java:74)
> 	at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:465)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler.execute(SkinResourceRequestHandler.java:101)
> 	at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
> 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
> 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
> 	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92)
> 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
> 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> 	at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:722)
> Caused by: java.net.SocketException: Broken pipe
> 	at java.net.SocketOutputStream.socketWrite0(Native Method)
> 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> 	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> 	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:371)
> 	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:240)
> 	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:119)
> 	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:192)
> 	at org.apache.coyote.Response.doWrite(Response.java:505)
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383)
> 	... 68 more
> {code}
> For this broken pipe exception, we should catch up the exception and keep it silent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 07:18:57 2014
From: issues at jboss.org (Ahmed Zaoui (JIRA))
Date: Fri, 23 May 2014 07:18:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3489)
 [MembershipDAOImpl]ORA-00001: unique constraint (IDM.SYS_C0015551) violated
In-Reply-To: <JIRA.12541698.1400843865547@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541698.1400843865547@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541698.1400843865547.38881.1400843937520@jira02.app.mwc.hst.phx2.redhat.com>

Ahmed Zaoui created GTNPORTAL-3489:
--------------------------------------

             Summary: [MembershipDAOImpl]ORA-00001: unique constraint (IDM.SYS_C0015551) violated
                 Key: GTNPORTAL-3489
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3489
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.5.9.Final
            Reporter: Ahmed Zaoui
            Priority: Minor


When synchronizing new user from ldap with an already created relationship we got this exception:

{noformat}
2014-04-29 16:01:05,248 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ajp-arecasapps02/10.100.8.17:14011-2) ORA-00001: unique constraint (IDM.SYS_C0015551) violated

2014-04-29 16:01:05,257 WARN  Failed to call postSave for gerap User with listener : class org.exoplatform.services.organization.impl.NewUserEventListener: org.picketlink.idm.common.exception.IdentityException: Cannot create relationship: 
	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.createRelationship(HibernateIdentityStoreImpl.java:1212) [picketlink-idm-hibernate.jar:1.4.4.Final]
	at org.picketlink.idm.impl.repository.FallbackIdentityStoreRepository.createRelationship(FallbackIdentityStoreRepository.java:1042) [picketlink-idm-core.jar:1.4.4.Final]
	at org.picketlink.idm.impl.api.session.managers.RelationshipManagerImpl.associateUserByKeys(RelationshipManagerImpl.java:375) [picketlink-idm-core.jar:1.4.4.Final]
	at org.exoplatform.services.organization.idm.MembershipDAOImpl.linkMembership(MembershipDAOImpl.java:132) [exo.portal.component.identity-3.5.9.Final_patched.jar:3.5.9.Final]
	at org.exoplatform.services.organization.impl.NewUserEventListener.createDefaultUserMemberships(NewUserEventListener.java:101) [exo.core.component.organization.api.jar:2.5.8-GA]
	at org.exoplatform.services.organization.impl.NewUserEventListener.postSave(NewUserEventListener.java:72) [exo.core.component.organization.api.jar:2.5.8-GA]
{noformat}

We should add test checking the existence of the association before creating new one



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 08:08:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 08:08:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3272) Site header/footer
 preview when editing a page
In-Reply-To: <JIRA.12502176.1380877540000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502176.1380877540000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502176.1380877540000.38998.1400846937362@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Site header/footer preview when editing a page
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3272
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3272
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.7.0.Final
>
>
> https://community.jboss.org/wiki/SiteHeaderfooterPreviewWhenEditingAPage



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 08:12:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 08:12:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3370) Add a function to
 completely hide a page using check-box and date-control
In-Reply-To: <JIRA.12529523.1389806048000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529523.1389806048000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529523.1389806048000.39003.1400847177019@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Add a function to completely hide a page using check-box and date-control
> -------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3370
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3370
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.8.0.Beta01
>
>
> As mentioned in GTNPORTAL-2033/JBEPP-1096, "Visible" and "Publication date" are effective only for Navigation. Pages are still accessible via direct URL access, such as http://localhost:8080/portal/private/classic/pagename
> GTNPORTAL-2033/JBEPP-1096 is for a documentation fix because it is an expected behaviour and the document should mention the limitation.
> This JIRA is raised for a feature request to implement the function to completely hide a page from users. It may be going to add some capability to "Visible" and "Publication date" feature.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Fri May 23 08:12:58 2014
From: issues at jboss.org (Ahmed Zaoui (JIRA))
Date: Fri, 23 May 2014 08:12:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3489)
 [MembershipDAOImpl]ORA-00001: unique constraint (IDM.SYS_C0015551) violated
In-Reply-To: <JIRA.12541698.1400843865000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541698.1400843865000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541698.1400843865000.39017.1400847178673@jira02.app.mwc.hst.phx2.redhat.com>


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

Ahmed Zaoui updated GTNPORTAL-3489:
-----------------------------------

    Git Pull Request: https://github.com/gatein/gatein-portal/pull/859/files


> [MembershipDAOImpl]ORA-00001: unique constraint (IDM.SYS_C0015551) violated
> ---------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3489
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3489
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Ahmed Zaoui
>            Priority: Minor
>
> When synchronizing new user from ldap with an already created relationship we got this exception:
> {noformat}
> 2014-04-29 16:01:05,248 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ajp-arecasapps02/10.100.8.17:14011-2) ORA-00001: unique constraint (IDM.SYS_C0015551) violated
> 2014-04-29 16:01:05,257 WARN  Failed to call postSave for gerap User with listener : class org.exoplatform.services.organization.impl.NewUserEventListener: org.picketlink.idm.common.exception.IdentityException: Cannot create relationship: 
> 	at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.createRelationship(HibernateIdentityStoreImpl.java:1212) [picketlink-idm-hibernate.jar:1.4.4.Final]
> 	at org.picketlink.idm.impl.repository.FallbackIdentityStoreRepository.createRelationship(FallbackIdentityStoreRepository.java:1042) [picketlink-idm-core.jar:1.4.4.Final]
> 	at org.picketlink.idm.impl.api.session.managers.RelationshipManagerImpl.associateUserByKeys(RelationshipManagerImpl.java:375) [picketlink-idm-core.jar:1.4.4.Final]
> 	at org.exoplatform.services.organization.idm.MembershipDAOImpl.linkMembership(MembershipDAOImpl.java:132) [exo.portal.component.identity-3.5.9.Final_patched.jar:3.5.9.Final]
> 	at org.exoplatform.services.organization.impl.NewUserEventListener.createDefaultUserMemberships(NewUserEventListener.java:101) [exo.core.component.organization.api.jar:2.5.8-GA]
> 	at org.exoplatform.services.organization.impl.NewUserEventListener.postSave(NewUserEventListener.java:72) [exo.core.component.organization.api.jar:2.5.8-GA]
> {noformat}
> We should add test checking the existence of the association before creating new one



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 08:14:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 08:14:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3379) Provide a button/icon
 to reset the search string
In-Reply-To: <JIRA.12530072.1390386653000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530072.1390386653000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530072.1390386653000.39027.1400847298028@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

>  Provide a button/icon to reset the search string
> -------------------------------------------------
>
>                 Key: GTNPORTAL-3379
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3379
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.7.0.Final
>
>
> When I first click on the User Management, it does show the full list of users from LDAP. But after searching some user entry if I click on the User Management again, it does not render the full user list. The only way to get the full user list is to clear the entry in the search box and click the Search Icon. 
> From the usability standpoint of view, I think clicking again on the User Management should clear the search entry and render the full list of users.
> If this can't be changed because of the current design then at least there should be a way to clear the search criteria. 
> The same applies to other lists which offer search functionality, such as in the Page Management.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Fri May 23 08:14:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 08:14:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3362) Add examples for
 Inter Portlet Communication
In-Reply-To: <JIRA.12529116.1389368733000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529116.1389368733000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529116.1389368733000.39038.1400847298987@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Add examples for Inter Portlet Communication
> --------------------------------------------
>
>                 Key: GTNPORTAL-3362
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3362
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.7.0.Final
>
>
> Add examples covering Public Render Parameters and Portlet Events



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 08:14:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 08:14:59 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3369) Add Public Render
 Parameter support at URL level
In-Reply-To: <JIRA.12529522.1389805950000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529522.1389805950000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529522.1389805950000.39040.1400847299156@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Add Public Render Parameter support at URL level
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3369
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3369
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> Add support to pass Public Render Parameters at URL level



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 09:21:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 23 May 2014 09:21:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3328) Automatic way to
 update all sites at once (Portal, groups and user sites)
In-Reply-To: <JIRA.12527041.1386235077000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12527041.1386235077000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12527041.1386235077000.39279.1400851316716@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Automatic way to update all sites at once (Portal, groups and user sites)
> -------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3328
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3328
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> This feature is described in the following document:
> https://community.jboss.org/wiki/AutomaticWayToUpdateAllSitesAtOncePortalGroupsAndUserSites



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sun May 25 22:49:56 2014
From: issues at jboss.org (H. Trang Vu (JIRA))
Date: Sun, 25 May 2014 22:49:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3490) [Services Management
 gadget] Hard-coded English labels
In-Reply-To: <JIRA.12541833.1401072516891@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541833.1401072516891@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541833.1401072516891.40937.1401072596582@jira02.app.mwc.hst.phx2.redhat.com>

H. Trang Vu created GTNPORTAL-3490:
--------------------------------------

             Summary: [Services Management gadget] Hard-coded English labels
                 Key: GTNPORTAL-3490
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3490
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: Internationalization and Localization
    Affects Versions: 3.7.1.Final, 3.5.10.Final
            Reporter: H. Trang Vu
            Assignee: H. Trang Vu


Steps to reproduce:
* Login as root
* Go to Application Registry, add *Services Management* gadget into a category
* Open Dashboard
* Add *Services Management* gadget
* Switch to French. 
* Open the gadget in both normal size and large size
** "Methods", "Properties" are still in English.





--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sun May 25 22:51:56 2014
From: issues at jboss.org (H. Trang Vu (JIRA))
Date: Sun, 25 May 2014 22:51:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3490) [Services Management
 gadget] Hard-coded English labels
In-Reply-To: <JIRA.12541833.1401072516000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541833.1401072516000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541833.1401072516000.40939.1401072716464@jira02.app.mwc.hst.phx2.redhat.com>


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

H. Trang Vu updated GTNPORTAL-3490:
-----------------------------------

    Attachment: FR-Properties.png
                FR-LargeSize-Methods-Properties.png


> [Services Management gadget] Hard-coded English labels
> ------------------------------------------------------
>
>                 Key: GTNPORTAL-3490
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3490
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Internationalization and Localization
>    Affects Versions: 3.5.10.Final, 3.7.1.Final
>            Reporter: H. Trang Vu
>            Assignee: H. Trang Vu
>         Attachments: FR-LargeSize-Methods-Properties.png, FR-Properties.png
>
>
> Steps to reproduce:
> * Login as root
> * Go to Application Registry, add *Services Management* gadget into a category
> * Open Dashboard
> * Add *Services Management* gadget
> * Switch to French. 
> * Open the gadget in both normal size and large size
> ** "Methods", "Properties" are still in English.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sun May 25 22:55:56 2014
From: issues at jboss.org (H. Trang Vu (JIRA))
Date: Sun, 25 May 2014 22:55:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3491) [Gadget] Hard-coded
 English labels in Title and Field Name
In-Reply-To: <JIRA.12541834.1401072946642@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541834.1401072946642@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541834.1401072946642.40941.1401072956473@jira02.app.mwc.hst.phx2.redhat.com>

H. Trang Vu created GTNPORTAL-3491:
--------------------------------------

             Summary: [Gadget] Hard-coded English labels in Title and Field Name
                 Key: GTNPORTAL-3491
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3491
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: Internationalization and Localization
    Affects Versions: 3.7.1.Final, 3.5.10.Final
            Reporter: H. Trang Vu


Steps to reproduce:
* Login as root
* Go to Application Registry, add *Services Management* gadget into a category
* Switch to Vietnamese
* Open Dashboard
* Add *Services Management* gadget
* The gadget title is always in English
* Click pencil icon to edit gadget setting
** "Services URL" is always in English



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sun May 25 23:07:56 2014
From: issues at jboss.org (H. Trang Vu (JIRA))
Date: Sun, 25 May 2014 23:07:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3491) [Gadget] Hard-coded
 English labels in Title and Field Name
In-Reply-To: <JIRA.12541834.1401072946000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541834.1401072946000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541834.1401072946000.40943.1401073676580@jira02.app.mwc.hst.phx2.redhat.com>


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

H. Trang Vu updated GTNPORTAL-3491:
-----------------------------------

    Attachment: VI-Title-FieldName.png


In [Gadgets.js|https://github.com/gatein/gatein-portal/blob/3.7.1.Final/gadgets/core/src/main/javascript/gatein-features/gatein-container/Gadgets.js], the translation of gadget title and field display_name isn't taken into account.
{code:title=Gadgets.js}
        ...
gadgets.IfrGadgetService.prototype.setTitle = function(title) {
  var element = $("#" + this.f).closest(".UIGadget").find("div.GadgetTitle").eq(0);
  if(element)
  {
    element.html(title.replace(/&/g, '&amp;').replace(/</g, '&lt;'));
  }
};
...
gadgets.IfrGadget.prototype.generateForm = function(gadget) {
        ....
        labelEl.innerHTML = prefs[att].displayName + ": ";
        attEl.appendChild(labelEl);
        ...
};
{code}

> [Gadget] Hard-coded English labels in Title and Field Name
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3491
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3491
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Internationalization and Localization
>    Affects Versions: 3.5.10.Final, 3.7.1.Final
>            Reporter: H. Trang Vu
>         Attachments: VI-Title-FieldName.png
>
>
> Steps to reproduce:
> * Login as root
> * Go to Application Registry, add *Services Management* gadget into a category
> * Switch to Vietnamese
> * Open Dashboard
> * Add *Services Management* gadget
> * The gadget title is always in English
> * Click pencil icon to edit gadget setting
> ** "Services URL" is always in English



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 00:27:56 2014
From: issues at jboss.org (H. Trang Vu (JIRA))
Date: Mon, 26 May 2014 00:27:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3490) [Services Management
 gadget] Hard-coded English labels
In-Reply-To: <JIRA.12541833.1401072516000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541833.1401072516000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541833.1401072516000.40959.1401078476742@jira02.app.mwc.hst.phx2.redhat.com>


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

H. Trang Vu updated GTNPORTAL-3490:
-----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/860


> [Services Management gadget] Hard-coded English labels
> ------------------------------------------------------
>
>                 Key: GTNPORTAL-3490
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3490
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Internationalization and Localization
>    Affects Versions: 3.5.10.Final, 3.7.1.Final
>            Reporter: H. Trang Vu
>            Assignee: H. Trang Vu
>         Attachments: FR-LargeSize-Methods-Properties.png, FR-Properties.png
>
>
> Steps to reproduce:
> * Login as root
> * Go to Application Registry, add *Services Management* gadget into a category
> * Open Dashboard
> * Add *Services Management* gadget
> * Switch to French. 
> * Open the gadget in both normal size and large size
> ** "Methods", "Properties" are still in English.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 04:53:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 04:53:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3442) portal-setup.sh/.bat
 scripts doesnt work with JBoss EAP 6.3.0 distribution
In-Reply-To: <JIRA.12537410.1396877045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537410.1396877045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537410.1396877045000.41325.1401094436696@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1084989|https://bugzilla.redhat.com/show_bug.cgi?id=1084989] from ON_QA to VERIFIED

> portal-setup.sh/.bat scripts doesnt work with JBoss EAP 6.3.0 distribution
> --------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3442
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3442
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 05:07:56 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Mon, 26 May 2014 05:07:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-377) Concurrency problem
 might cause credentials swap
In-Reply-To: <JIRA.12541857.1401095190806@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541857.1401095190806@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541857.1401095190806.41357.1401095276370@jira02.app.mwc.hst.phx2.redhat.com>

Juraci Paix?o Kr?hling created GTNWSRP-377:
----------------------------------------------

             Summary: Concurrency problem might cause credentials swap
                 Key: GTNWSRP-377
                 URL: https://issues.jboss.org/browse/GTNWSRP-377
             Project: GateIn WSRP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling


>From BZ 1063918:

--
In some circumstances, the following situations might occur:

- a non-authenticated user can get the contents for a remote portlet as if another user had requested. 
- an authenticated user might be presented as "not logged in" for the remote portlet

For this to happen, the following must happen:

- the WS-Security checkbox on the WSRP Consumer Configuration should be checked, so that the user propagation between producer and consumer is activated
- for a specific WSRP endpoint (MarkupService, for example), a high-concurrency scenario is required and/or a situation where the SOAP message takes long to execute

This is so because there is one instance of GTNSubjectCreatingInterceptor per endpoint, and the state of the instance is changed at the same time by multiple threads, causing one thread to assign wsUsernameTokenPrincipal, while another might consume the it when it's not supposed to.

To illustrate this, I've added some System.out's on the interceptor and added a random delay after the message has been processed (after super.handleMessage(msg)), so that my low-concurrency scenario would easily reach a situation where a high-concurrency environment might experience. 

To reproduce:
- replace WSRP's ./ws-security/jboss7/src/main/java/org/gatein/wsrp/wss/cxf/producer/GTNSubjectCreatingInterceptor.java with the version from this ticket (with the random Thread.sleep + System.out's)
- build WSRP
- build GateIn from this branch: https://github.com/jpkrohling/gatein-portal/tree/JPK-UserInformationInPortlet , which changes the "simplest hello world" portlet to display the current user's info
- Deploy the simplest hello world portlet, built from the branch above
- Deploy the RichFaces Showcase portlet (attached to this BZ)
- Boot GateIn, login as root, open the WSRP's Consumer Configuration screen and check the "Enable WS Security" checkbox
- Click on "Refresh & Save"
- Add both the remote and local versions of the portlets to one category each (local in the Web, remote on the WSRP)
- Create a new page, adding the remote version of the "simplest hello world" portlet to it 
- Create a new page, adding the remote version of the "RichFaces Showcase" portlet to it
- Open a new browser, and login as "john"
- On the first browser (root), click on the RichFaces Showcase
- On the second browser, click on the page with the "simplest hello world"

The last two steps might need a few tries to reach the state of the screenshots.
--



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 26 05:49:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Mon, 26 May 2014 05:49:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3492) Providing an
 extensible searching for skins in SkinService
In-Reply-To: <JIRA.12541861.1401097759538@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541861.1401097759538@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541861.1401097759538.41436.1401097796529@jira02.app.mwc.hst.phx2.redhat.com>

Trong Tran created GTNPORTAL-3492:
-------------------------------------

             Summary: Providing an extensible searching for skins in SkinService
                 Key: GTNPORTAL-3492
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3492
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Trong Tran
             Fix For: 3.7.2.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 06:17:56 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Mon, 26 May 2014 06:17:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3492) Providing an
 extensible searching for skins in SkinService
In-Reply-To: <JIRA.12541861.1401097759000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541861.1401097759000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541861.1401097759000.41469.1401099476589@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3492:
----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/861


> Providing an extensible searching for skins in SkinService
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-3492
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3492
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Trong Tran
>             Fix For: 3.7.2.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 07:57:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 07:57:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand
 does not ensure that initialpassword is written on a new line
In-Reply-To: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539757.1399047211000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539757.1399047211000.41710.1401105476378@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3469
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3469
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} 
> Not OK: The {{configuration.properties}} file ends with 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected: 
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 08:57:58 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 08:57:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3361) Allow more flexible
 cache-control header per portal
In-Reply-To: <JIRA.12529103.1389364124000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529103.1389364124000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529103.1389364124000.41939.1401109078151@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 811126|https://bugzilla.redhat.com/show_bug.cgi?id=811126] from ON_QA to VERIFIED

> Allow more flexible cache-control header per portal
> ---------------------------------------------------
>
>                 Key: GTNPORTAL-3361
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3361
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.7.0.Final
>
>
> Allow each portal to have its own Cache-control directive, as per Bugzilla 811126



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 26 09:53:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 09:53:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3444) "Invalid Application
 Id" thrown for all apps in Application Registry
In-Reply-To: <JIRA.12537691.1397047090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537691.1397047090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537691.1397047090000.42154.1401112436600@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1085792|https://bugzilla.redhat.com/show_bug.cgi?id=1085792] from ON_QA to VERIFIED

> "Invalid Application Id" thrown for all apps in Application Registry
> --------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3444
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3444
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: master, head on commit:
> 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> The following exception is logged when when clicking on any Application in Application Registry:
> Error during the processAction phase: java.lang.Exception: Invalid Application Id: [dashboard_slash_DashboardPortlet]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:36:02 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Mon, 26 May 2014 10:36:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3493) Membership just added,
	disappears
In-Reply-To: <JIRA.12541890.1401114872205@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541890.1401114872205@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541890.1401114872205.42279.1401114962594@jira02.app.mwc.hst.phx2.redhat.com>

Boubaker Khanfir created GTNPORTAL-3493:
-------------------------------------------

             Summary: Membership just added, disappears
                 Key: GTNPORTAL-3493
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3493
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Boubaker Khanfir
         Attachments: plidm-ldap-membership-disappear.zip

I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).

This one shows how we can add a membership and just after that it disappears.

In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/web/portal/src/main/webapp/WEB-INF/conf/organization/idm-configuration.xml], the comment :

{quote}
          <!-- if "associationMembershipType" option is used and this option is set to true
                then Membership with MembershipType configured to be stored as PicketLink IDM association
                will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
                For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
                However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
{quote}

is not good and have to be like this:

{quote}
          <!-- if "associationMembershipType" option is used and this option is set to true
                then Membership with MembershipType configured to be stored as PicketLink IDM association
                will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
                For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
                However for DB only, it's recommended to not map anything here -->
{quote}

What changes in this comment ?
The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".

I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:36:02 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Mon, 26 May 2014 10:36:02 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3493) Membership just added,
	disappears
In-Reply-To: <JIRA.12541890.1401114872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541890.1401114872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541890.1401114872000.42280.1401114962648@jira02.app.mwc.hst.phx2.redhat.com>


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

Boubaker Khanfir updated GTNPORTAL-3493:
----------------------------------------

    Attachment: plidm-ldap-membership-disappear.zip


> Membership just added, disappears
> ---------------------------------
>
>                 Key: GTNPORTAL-3493
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3493
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Boubaker Khanfir
>         Attachments: plidm-ldap-membership-disappear.zip
>
>
> I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).
> This one shows how we can add a membership and just after that it disappears.
> In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/web/portal/src/main/webapp/WEB-INF/conf/organization/idm-configuration.xml], the comment :
> {quote}
>           <!-- if "associationMembershipType" option is used and this option is set to true
>                 then Membership with MembershipType configured to be stored as PicketLink IDM association
>                 will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
>                 For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
>                 However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
> {quote}
> is not good and have to be like this:
> {quote}
>           <!-- if "associationMembershipType" option is used and this option is set to true
>                 then Membership with MembershipType configured to be stored as PicketLink IDM association
>                 will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
>                 For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
>                 However for DB only, it's recommended to not map anything here -->
> {quote}
> What changes in this comment ?
> The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".
> I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:57:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 10:57:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character
 issues in Dashboard tab name
In-Reply-To: <JIRA.12533315.1393397780000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533315.1393397780000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533315.1393397780000.42381.1401116276920@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1070077|https://bugzilla.redhat.com/show_bug.cgi?id=1070077] from ON_QA to VERIFIED

> Multibyte character issues in Dashboard tab name
> ------------------------------------------------
>
>                 Key: GTNPORTAL-3400
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3400
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.6.0.Final
>         Environment: Internet Explorer 9
>            Reporter: Takayuki Konishi
>            Assignee: Juraci Paix?o Kr?hling
>             Fix For: 3.8.0.Beta01
>
>         Attachments: gatein.png
>
>
> 1. After set multibyte characters in Dashboard tab, we cannot edit it anymore on IE 9.
> 2. The window title doesn't display multibyte characters. It displays numeric character references (i.e. "&\#x3042;&\#x3042;&\#x3042;" for "???")



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Mon May 26 11:31:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 26 May 2014 11:31:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3494) Names of imported
 applications in Application Registry are not localized
In-Reply-To: <JIRA.12541900.1401118291310@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541900.1401118291310@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541900.1401118291310.42550.1401118316266@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3494:
--------------------------------------

             Summary: Names of imported applications in Application Registry are not localized 
                 Key: GTNPORTAL-3494
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3494
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: WebUI
    Affects Versions: 3.8.1.Final
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce
             Fix For: 3.8.2.Final, 3.9.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 11:33:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 11:33:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3494) Names of imported
 applications in Application Registry are not localized
In-Reply-To: <JIRA.12541900.1401118291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541900.1401118291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541900.1401118291000.42561.1401118437648@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3494:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1101275


> Names of imported applications in Application Registry are not localized 
> -------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3494
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3494
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>    Affects Versions: 3.8.1.Final
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 11:39:56 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Mon, 26 May 2014 11:39:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3494) Names of imported
 applications in Application Registry are not localized
In-Reply-To: <JIRA.12541900.1401118291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541900.1401118291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541900.1401118291000.42572.1401118796754@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3494:
-----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/862


> Names of imported applications in Application Registry are not localized 
> -------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3494
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3494
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WebUI
>    Affects Versions: 3.8.1.Final
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 12:05:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 12:05:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3401) Encoding of "&"
	characters in URLs.
In-Reply-To: <JIRA.12533339.1393414394000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533339.1393414394000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533339.1393414394000.42661.1401120357831@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1065987|https://bugzilla.redhat.com/show_bug.cgi?id=1065987] from ON_QA to VERIFIED

> Encoding of "&" characters in URLs.
> -----------------------------------
>
>                 Key: GTNPORTAL-3401
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3401
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> For a w3c validation, URLs should be encoded using html entities instead of plain "&" characters.
> A configuration flag should be implemented to enable/disable URLs encoded.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 12:11:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 12:11:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of
 custom attributes for portal navigation portlets.
In-Reply-To: <JIRA.12533769.1393855334000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533769.1393855334000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533769.1393855334000.42679.1401120717470@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1065991|https://bugzilla.redhat.com/show_bug.cgi?id=1065991] from ON_QA to VERIFIED

> Avoid the use of custom attributes for portal navigation portlets.
> ------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3406
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3406
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> For a w3c validation, standard html elements can not contain custom attributes.
> There are several custom attributes like "exo:getNodeURL", "exo:minWidth", "exo:minHeight" used creating non compliant markup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 12:13:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 12:13:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements
 starting with number
In-Reply-To: <JIRA.12533810.1393861870000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533810.1393861870000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533810.1393861870000.42683.1401120836663@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1065997|https://bugzilla.redhat.com/show_bug.cgi?id=1065997] from ON_QA to VERIFIED

> Avoid ID elements starting with number
> --------------------------------------
>
>                 Key: GTNPORTAL-3407
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3407
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> For a w3c validation, elements ID should not start with number.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 12:17:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 12:17:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html
 attributes not compliant
In-Reply-To: <JIRA.12533816.1393865466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533816.1393865466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533816.1393865466000.42685.1401121076564@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1066001|https://bugzilla.redhat.com/show_bug.cgi?id=1066001] from ON_QA to ASSIGNED

> Use of legacy html attributes not compliant
> -------------------------------------------
>
>                 Key: GTNPORTAL-3409
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3409
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> There are some legacy html elements (i.e. target="_blank") not compatible with XHTML 1.0 Strict type document creating a non compliant markup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 12:17:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 12:17:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML
	issues
In-Reply-To: <JIRA.12533919.1393925082000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533919.1393925082000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533919.1393925082000.42687.1401121076690@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1066010|https://bugzilla.redhat.com/show_bug.cgi?id=1066010] from ON_QA to VERIFIED

> Minor markup XHTML issues
> -------------------------
>
>                 Key: GTNPORTAL-3411
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3411
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> There are some minor markups not compliant with XHTML specification (i.e. empty list <ul></ul>, or bad use of <span> tag inside a block element).
> These issues don't affect to Portal behaviour but creates a non compliant markup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 13:01:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 26 May 2014 13:01:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html
 attributes not compliant
In-Reply-To: <JIRA.12533816.1393865466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533816.1393865466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533816.1393865466000.42796.1401123716457@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1066001|https://bugzilla.redhat.com/show_bug.cgi?id=1066001] from ASSIGNED to VERIFIED

> Use of legacy html attributes not compliant
> -------------------------------------------
>
>                 Key: GTNPORTAL-3409
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3409
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> GateIn produces XHTML 1.0 Strict type documents.
> There are some legacy html elements (i.e. target="_blank") not compatible with XHTML 1.0 Strict type document creating a non compliant markup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 03:55:56 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Tue, 27 May 2014 03:55:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3493) Membership just added,
	disappears
In-Reply-To: <JIRA.12541890.1401114872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541890.1401114872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541890.1401114872000.43425.1401177356685@jira02.app.mwc.hst.phx2.redhat.com>


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

Boubaker Khanfir updated GTNPORTAL-3493:
----------------------------------------

    Affects Version/s: 3.5.9.Final


> Membership just added, disappears
> ---------------------------------
>
>                 Key: GTNPORTAL-3493
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3493
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Boubaker Khanfir
>         Attachments: plidm-ldap-membership-disappear.zip
>
>
> I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).
> This one shows how we can add a membership and just after that it disappears.
> In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/web/portal/src/main/webapp/WEB-INF/conf/organization/idm-configuration.xml], the comment :
> {quote}
>           <!-- if "associationMembershipType" option is used and this option is set to true
>                 then Membership with MembershipType configured to be stored as PicketLink IDM association
>                 will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
>                 For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
>                 However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
> {quote}
> is not good and have to be like this:
> {quote}
>           <!-- if "associationMembershipType" option is used and this option is set to true
>                 then Membership with MembershipType configured to be stored as PicketLink IDM association
>                 will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
>                 For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
>                 However for DB only, it's recommended to not map anything here -->
> {quote}
> What changes in this comment ?
> The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".
> I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:03:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Tue, 27 May 2014 06:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-18) Investigate Picketlink
 federation WARNINGS during GateIn as IDP setup
In-Reply-To: <JIRA.12477035.1350339326000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12477035.1350339326000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12477035.1350339326000.43887.1401185036662@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-18:
--------------------------------

    Fix Version/s: 1.4.3.Final
                       (was: 1.4.2.Final)


> Investigate Picketlink federation WARNINGS during GateIn as IDP setup
> ---------------------------------------------------------------------
>
>                 Key: GTNSSO-18
>                 URL: https://issues.jboss.org/browse/GTNSSO-18
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.3.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.3.Final
>
>
> There are some WARNs from picketlink federation when having GateIn as SAML2 IDP. It doesn't break functionality, but needs to be investigated if everything is ok in configuration.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:03:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Tue, 27 May 2014 06:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-28) realm is wrong adds an
 extra g in the realm name with OpenAM 11
In-Reply-To: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540213.1399536877000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540213.1399536877000.43886.1401185036619@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-28:
--------------------------------

    Fix Version/s: 1.4.3.Final
                       (was: 1.4.2.Final)


> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
>                 Key: GTNSSO-28
>                 URL: https://issues.jboss.org/browse/GTNSSO-28
>             Project: GateIn SSO
>          Issue Type: Bug
>    Affects Versions: 1.4.0.Beta01
>         Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
>            Reporter: Michael McKinsey
>            Assignee: Marek Posolda
>             Fix For: 1.4.3.Final
>
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1a0b0d800a/agent/src/main/java/org/gatein/sso/agent/filter/OpenSSOCDLoginRedirectFilter.java
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11.  I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:03:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Tue, 27 May 2014 06:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-16) Callback support for JOSSO
	2.2
In-Reply-To: <JIRA.12477002.1350316489000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12477002.1350316489000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12477002.1350316489000.43888.1401185036702@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-16:
--------------------------------

    Fix Version/s: 1.4.3.Final
                       (was: 1.4.2.Final)


> Callback support for JOSSO 2.2
> ------------------------------
>
>                 Key: GTNSSO-16
>                 URL: https://issues.jboss.org/browse/GTNSSO-16
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.3.0.Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.3.Final
>
>
> It's defacto working, but setup is quite complicated for SSO users. Revisit this later and check if it could be simplified.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:03:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Tue, 27 May 2014 06:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-8) Unit tests
In-Reply-To: <JIRA.12461101.1331226582000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12461101.1331226582000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12461101.1331226582000.43890.1401185036789@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-8:
-------------------------------

    Fix Version/s: 1.4.3.Final
                       (was: 1.4.2.Final)


> Unit tests
> ----------
>
>                 Key: GTNSSO-8
>                 URL: https://issues.jboss.org/browse/GTNSSO-8
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.1.1-GA
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.3.Final
>
>
> Current support of unit tests is not good. There are couple of dummy unit tests, but they are disabled as they require server to be running before running tests. It will be needed to provide integration with some well-known solution (Arquillian, Cargo, JBoss unit...) and provide more unit tests for SSO component.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:03:56 2014
From: issues at jboss.org (Marek Posolda (JIRA))
Date: Tue, 27 May 2014 06:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNSSO-11) Remove SPNEGO workarounds
 needed for SECURITY-695 and SECURITY-696
In-Reply-To: <JIRA.12474983.1348147571000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12474983.1348147571000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12474983.1348147571000.43889.1401185036745@jira02.app.mwc.hst.phx2.redhat.com>


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

Marek Posolda updated GTNSSO-11:
--------------------------------

    Fix Version/s: 1.4.3.Final
                       (was: 1.4.2.Final)


> Remove SPNEGO workarounds needed for SECURITY-695 and SECURITY-696
> ------------------------------------------------------------------
>
>                 Key: GTNSSO-11
>                 URL: https://issues.jboss.org/browse/GTNSSO-11
>             Project: GateIn SSO
>          Issue Type: Enhancement
>    Affects Versions: 1.2.0-Beta01
>            Reporter: Marek Posolda
>            Assignee: Marek Posolda
>             Fix For: 1.4.3.Final
>
>
> After upgrade to jboss-negotiation 2.2.2.Final we need to remove workaround in SPNEGOLoginModule (just left method getIdentityForSubject and remove others)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:55:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 06:55:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3428) Unify CDATA uses
In-Reply-To: <JIRA.12535702.1395406496000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535702.1395406496000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535702.1395406496000.44070.1401188157526@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Unify CDATA uses
> ----------------
>
>                 Key: GTNPORTAL-3428
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3428
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Beta01
>
>
> Review and unify the use of CDATA for <script> tags into markup.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 07:03:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 07:03:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3385) Support full-ha and
 ha profiles in domain mode
In-Reply-To: <JIRA.12530204.1390485984000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530204.1390485984000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530204.1390485984000.44096.1401188636651@jira02.app.mwc.hst.phx2.redhat.com>


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

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

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

> Support full-ha and ha profiles in domain mode
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3385
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3385
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.7.0.Final, 3.6.5.Final
>
>
> Add support for full-ha and ha profiles in domain mode for GateIn distribution based on JBoss.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 08:39:58 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Tue, 27 May 2014 08:39:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.44415.1401194398305@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3475:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
         Assignee: Peter Palaga
    Fix Version/s: 3.8.2.Final
                   3.9.0.Final
       Resolution: Done


> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 08:41:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 08:41:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3475) NPE in
 LinkedList$ListItr.next when iterating over
 UIGroupMembershipSelect.getListMemberhip()
In-Reply-To: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540331.1399635695000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540331.1399635695000.44422.1401194517427@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1096190|https://bugzilla.redhat.com/show_bug.cgi?id=1096190] from POST to MODIFIED

> NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()
> ---------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3475
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3475
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>         Attachments: GTNPORTAL-3475.log
>
>
> Looks like a concurrent modification of  the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because:
> i. It is not always reproducible, the NPE occurs roughly once per 10 attempts.
> ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause.
> Steps to reproduce:
> (1) Start clean Portal instance for the first time
> (2) Go to Application Registry
> (3) Import Applications
> Not OK: There is an NPE logged (the whole log is attached):
> {code:none}
> Caused by: java.lang.NullPointerException
> 	at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55]
> 	at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20)	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> 	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT]
> {code}
> Expected: No NPE



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 08:43:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Tue, 27 May 2014 08:43:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908000.44438.1401194636750@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3484:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.2.Final
                   3.9.0.Final
       Resolution: Done


> Commit changes for a page before send response
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3484
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>
> In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.
> This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 08:43:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 08:43:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3484) Commit changes for a
 page before send response
In-Reply-To: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541206.1400575908000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541206.1400575908000.44440.1401194636916@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from POST to MODIFIED

> Commit changes for a page before send response
> ----------------------------------------------
>
>                 Key: GTNPORTAL-3484
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3484
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>
> In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited.
> This can cause some StaleModelException cases under heavy load or database congestion.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 08:43:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 08:43:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-2581) RichFaces is not
 defined after adding a RF portlet to a page
In-Reply-To: <JIRA.12474884.1348062188000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12474884.1348062188000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12474884.1348062188000.44442.1401194637009@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from POST to MODIFIED

> RichFaces is not defined after adding a RF portlet to a page
> ------------------------------------------------------------
>
>                 Key: GTNPORTAL-2581
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2581
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: GateIn 3.4.0.Final
>            Reporter: Peter Palaga
>         Attachments: jsf2-rf4-hello-world-portlet.war
>
>
> (1) Start a fresh GateIn 3.4.0.Final:
> cd tmp
> wget http://downloads.jboss.org/gatein/Releases/Portal/3.4.0.Final/GateIn-3.4.0.Final-jbossas7.zip 
> unzip GateIn-3.4.0.Final-jbossas7.zip
> cd GateIn-3.4.0.Final-jbossas7/bin
> ./standalone.sh
> (2) Install gatein-bom-3.4
> git clone https://github.com/ppalaga/gatein-bom.github
> cd gatein-bom
> mvn install -Dgpg.skip=true
> (3) Pack and deploy jsf2-rf4-hello-world-portlet:
> cd tmp
> git clone https://github.com/ppalaga/gatein-portal-quickstart.git
> cd gatein-portal-quickstart/jsf2-rf4-hello-world-portlet
> mvn package jboss-as:deploy
> (4)  In web browser:
> * login as root http://127.0.0.1:8080/portal/login?username=root&password=gtn&initialURI=/portal/classic/
> (5) In web browser:
> * Group > Administration > Application Registry > Import Applications
> * Site > Classic > Home
> * Site Editor > Edit Page
> * Drag jsf2-rf4-hello-world-portlet and drop it e.g. under the Home Page portlet
> * make the console with server log visible to you
> * Open developer tools (F12 in Chrome) and switch to Resources. Have a look at loaded scripts. Note that there are no PBR-related scripts there.
> (6) Hit Finish (Diskette Icon) in Page Editor dialog
> (7) UNEXPECTED: After hitting Finish, there comes a modal message in the browser window saying "RichFaces is not defined". 
> * Note that while this message is being displayed, there is no change in the scripts compared to before (5).
> * Note that nothing happened in the server log.
>  
> (8) Hit OK in the "RichFaces is not defined" alert.
> * Note that one or more PBR-related scripts were loaded. Some of them have error markers in them
> * Sometimes one or more org.exoplatform.portal.config.NoSuchDataExceptions appear in the server log
>  
> The problem seems to be related to the fact that the inline JavaScript needed to render the rich:select component is evaluated before the needed js resources were loaded. After reloading the whole page or accessing the page from another session jsf2-rf4-hello-world-portlet works as expected. 
> For further observations, define one more step:
> (9)
> * Site > Classic > Home
> * Site Editor > Edit Page
> * remove jsf2-rf4-hello-world-portlet from the page
> * Hit Finish (Diskette Icon) in Page Editor dialog
> When in the state after (8), one performs (9) and then again (5) and (6), "RichFaces is not defined" does not appear.
> "RichFaces is not defined" appears only when one signs out from the portal and signs in again between (9) and (5) of the previous scenario.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 09:19:58 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Tue, 27 May 2014 09:19:58 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3365) Exception swallow in
 UserDaoImpl.persistUserInfo()
In-Reply-To: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529293.1389667726000.44572.1401196798878@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3365:
-----------------------------------

              Status: Pull Request Sent  (was: Pull Request Sent)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/765, https://github.com/gatein/gatein-portal/pull/864  (was: https://github.com/gatein/gatein-portal/pull/765)


New PR to resolve small conflicts with master branch.

> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3365
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3365
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.6.3.Final
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.6.4.Final, 3.9.0.Final
>
>   Original Estimate: 4 hours
>          Time Spent: 6 hours
>  Remaining Estimate: 0 minutes
>
> Under "{{org.exoplatform.services.organization.idm}}, 
> focus on : 
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
>    {
>       orgService.flush();
>       AttributesManager am = session.getAttributesManager();
>       ArrayList attributes = new ArrayList();
>       /* ... */
>       if (user.getPassword() != null)
>       {
>          if (orgService.getConfiguration().isPasswordAsAttribute())
>          {
>             attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
>          }
>          else
>          {
>             try
>             {
>                am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
>             }
>             catch (IdentityException e)
>             {
>                log.info("Cannot update password: " + user.getUserName() + "; ", e);
>             }
>          }
>       }
>       Attribute[] attrs = new Attribute[attributes.size()];
>       attrs = (Attribute[])attributes.toArray(attrs);
>       try
>       {
>          am.updateAttributes(user.getUserName(), attrs);
>       }
>       catch (IdentityException e)
>       {
>          log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
>       }
>    } 
> {code} 
>  
> The method {{saveUser(User, boolean) _throws Exception_}} 
> calls 
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}. 
>  
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}: 
> * first time in the password level
> * second time when updating all of the attributes. 
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:27:56 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Tue, 27 May 2014 11:27:56 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase
 are order dependent
In-Reply-To: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541101.1400497517000.45254.1401204476650@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga commented on GTNMOP-54:
------------------------------------

PR sent https://github.com/gatein/gatein-mop/pull/2

> Tests in WorkspaceTestCase are order dependent
> ----------------------------------------------
>
>                 Key: GTNMOP-54
>                 URL: https://issues.jboss.org/browse/GTNMOP-54
>             Project: GateIn Model Object for Portal
>          Issue Type: Bug
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114
> Description of problem:
> Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). 
> Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=1.3.1.Final-redhat-1) has test dependency junit-4.11-redhat-1.jar. 
> There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#test-execution-order
> Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites
> Version-Release number of selected component (if applicable):
> community MOP: 1.3.1.Final with junit 4.10
> prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1
> Additional info:
> When I declare junit version to 4.11 in community project I get the errors.
> When I declare junit version to 4.10-redhat-2 in prod project all tests passed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:31:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 11:31:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase
 are order dependent
In-Reply-To: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541101.1400497517000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541101.1400497517000.45270.1401204717380@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GTNMOP-54:
-----------------------------------------------

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1091114|https://bugzilla.redhat.com/show_bug.cgi?id=1091114] from ASSIGNED to POST

> Tests in WorkspaceTestCase are order dependent
> ----------------------------------------------
>
>                 Key: GTNMOP-54
>                 URL: https://issues.jboss.org/browse/GTNMOP-54
>             Project: GateIn Model Object for Portal
>          Issue Type: Bug
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114
> Description of problem:
> Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). 
> Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=1.3.1.Final-redhat-1) has test dependency junit-4.11-redhat-1.jar. 
> There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#test-execution-order
> Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites
> Version-Release number of selected component (if applicable):
> community MOP: 1.3.1.Final with junit 4.10
> prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1
> Additional info:
> When I declare junit version to 4.11 in community project I get the errors.
> When I declare junit version to 4.10-redhat-2 in prod project all tests passed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:57:57 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Tue, 27 May 2014 11:57:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3495) Membership Pagination
	don't work
In-Reply-To: <JIRA.12542051.1401206275442@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542051.1401206275442@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542051.1401206275442.45336.1401206277379@jira02.app.mwc.hst.phx2.redhat.com>

Boubaker Khanfir created GTNPORTAL-3495:
-------------------------------------------

             Summary: Membership Pagination don't work
                 Key: GTNPORTAL-3495
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3495
             Project: GateIn Portal
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Boubaker Khanfir


I attach a new unit test for a bug that I met in PL IDM 1.4.4.

Test case description:
1/ add about 10 users in an LDAP group
2/ use SearchCriteria to paginate on the Members of this group
=> Problem: pagination doesn't work

Why does it fails:

Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.


To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:59:57 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Tue, 27 May 2014 11:59:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3495) Membership Pagination
	don't work
In-Reply-To: <JIRA.12542051.1401206275000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542051.1401206275000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542051.1401206275000.45337.1401206397064@jira02.app.mwc.hst.phx2.redhat.com>


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

Boubaker Khanfir updated GTNPORTAL-3495:
----------------------------------------

    Affects Version/s: 3.5.9.Final


> Membership Pagination don't work
> --------------------------------
>
>                 Key: GTNPORTAL-3495
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3495
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Boubaker Khanfir
>         Attachments: plidm-ldap-membership-pagination.zip
>
>
> I attach a new unit test for a bug that I met in PL IDM 1.4.4.
> Test case description:
> 1/ add about 10 users in an LDAP group
> 2/ use SearchCriteria to paginate on the Members of this group
> => Problem: pagination doesn't work
> Why does it fails:
> Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.
> To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:59:57 2014
From: issues at jboss.org (Boubaker Khanfir (JIRA))
Date: Tue, 27 May 2014 11:59:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3495) Membership Pagination
	don't work
In-Reply-To: <JIRA.12542051.1401206275000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542051.1401206275000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542051.1401206275000.45344.1401206397834@jira02.app.mwc.hst.phx2.redhat.com>


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

Boubaker Khanfir updated GTNPORTAL-3495:
----------------------------------------

    Attachment: plidm-ldap-membership-pagination.zip


> Membership Pagination don't work
> --------------------------------
>
>                 Key: GTNPORTAL-3495
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3495
>             Project: GateIn Portal
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Boubaker Khanfir
>         Attachments: plidm-ldap-membership-pagination.zip
>
>
> I attach a new unit test for a bug that I met in PL IDM 1.4.4.
> Test case description:
> 1/ add about 10 users in an LDAP group
> 2/ use SearchCriteria to paginate on the Members of this group
> => Problem: pagination doesn't work
> Why does it fails:
> Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.
> To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 03:27:57 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Wed, 28 May 2014 03:27:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3365) Exception swallow in
 UserDaoImpl.persistUserInfo()
In-Reply-To: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529293.1389667726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529293.1389667726000.46353.1401262077661@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3365:
------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.8.2.Final
                       (was: 3.6.4.Final)
       Resolution: Done


https://github.com/gatein/gatein-portal/pull/864 was merged to master (a.k.a. 3.9.x) and 3.8.x

> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
>                 Key: GTNPORTAL-3365
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3365
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.6.3.Final
>            Reporter: Vu Viet Phuong
>            Assignee: Vu Viet Phuong
>             Fix For: 3.8.2.Final, 3.9.0.Final
>
>   Original Estimate: 4 hours
>          Time Spent: 6 hours
>  Remaining Estimate: 0 minutes
>
> Under "{{org.exoplatform.services.organization.idm}}, 
> focus on : 
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
>    {
>       orgService.flush();
>       AttributesManager am = session.getAttributesManager();
>       ArrayList attributes = new ArrayList();
>       /* ... */
>       if (user.getPassword() != null)
>       {
>          if (orgService.getConfiguration().isPasswordAsAttribute())
>          {
>             attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
>          }
>          else
>          {
>             try
>             {
>                am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
>             }
>             catch (IdentityException e)
>             {
>                log.info("Cannot update password: " + user.getUserName() + "; ", e);
>             }
>          }
>       }
>       Attribute[] attrs = new Attribute[attributes.size()];
>       attrs = (Attribute[])attributes.toArray(attrs);
>       try
>       {
>          am.updateAttributes(user.getUserName(), attrs);
>       }
>       catch (IdentityException e)
>       {
>          log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
>       }
>    } 
> {code} 
>  
> The method {{saveUser(User, boolean) _throws Exception_}} 
> calls 
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}. 
>  
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}: 
> * first time in the password level
> * second time when updating all of the attributes. 
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 04:32:57 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Wed, 28 May 2014 04:32:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3496) Services Management
 Gadget does not work when eXoPlatform server runs behind Apache server
In-Reply-To: <JIRA.12542099.1401265862414@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542099.1401265862414@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542099.1401265862414.46464.1401265977083@jira02.app.mwc.hst.phx2.redhat.com>

Tran Trung Thanh created GTNPORTAL-3496:
-------------------------------------------

             Summary: Services Management Gadget does not work when eXoPlatform server runs behind Apache server
                 Key: GTNPORTAL-3496
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3496
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.5.9.Final
            Reporter: Tran Trung Thanh
         Attachments: Gatein Services-Management.png

- Configure Gatein with apache 2 in HTTP mode by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
- Start GateIn server
- Access Gatein by using address of apache 
- Login as root
- Go to Group > Administration Services Management
-> There is a warning and no service is displayed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 04:32:57 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Wed, 28 May 2014 04:32:57 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3496) Services Management
 Gadget does not work when eXoPlatform server runs behind Apache server
In-Reply-To: <JIRA.12542099.1401265862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542099.1401265862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542099.1401265862000.46466.1401265977234@jira02.app.mwc.hst.phx2.redhat.com>


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

Tran Trung Thanh updated GTNPORTAL-3496:
----------------------------------------

    Attachment: Gatein Services-Management.png


> Services Management Gadget does not work when eXoPlatform server runs behind Apache server
> ------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3496
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3496
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Tran Trung Thanh
>         Attachments: Gatein Services-Management.png
>
>
> - Configure Gatein with apache 2 in HTTP mode by following
> http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
> - Start GateIn server
> - Access Gatein by using address of apache 
> - Login as root
> - Go to Group > Administration Services Management
> -> There is a warning and no service is displayed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 04:45:37 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Wed, 28 May 2014 04:45:37 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3497) Portlet in Dashboard
 is broken for the first access
In-Reply-To: <JIRA.12542102.1401266724070@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542102.1401266724070@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542102.1401266724070.46617.1401266737918@jira02.app.mwc.hst.phx2.redhat.com>

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

             Summary:  Portlet in Dashboard is broken for the first access
                 Key: GTNPORTAL-3497
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3497
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Juraci Paix?o Kr?hling
            Assignee: Juraci Paix?o Kr?hling


>From BZ 1059036: 

If you configure a richfaces portlet in dashboard template, the portlet may break for the first access by a newly created user.

https://bugzilla.redhat.com/show_bug.cgi?id=1059036



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May 28 05:09:16 2014
From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=)
Date: Wed, 28 May 2014 05:09:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3497) Portlet in Dashboard
 is broken for the first access
In-Reply-To: <JIRA.12542102.1401266724000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542102.1401266724000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542102.1401266724000.24.1401268156871@jira02.app.mwc.hst.phx2.redhat.com>


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

Juraci Paix?o Kr?hling updated GTNPORTAL-3497:
----------------------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/866


>  Portlet in Dashboard is broken for the first access
> ----------------------------------------------------
>
>                 Key: GTNPORTAL-3497
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3497
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> From BZ 1059036: 
> If you configure a richfaces portlet in dashboard template, the portlet may break for the first access by a newly created user.
> https://bugzilla.redhat.com/show_bug.cgi?id=1059036



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May 28 05:09:17 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 28 May 2014 05:09:17 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3497) Portlet in Dashboard
 is broken for the first access
In-Reply-To: <JIRA.12542102.1401266724000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542102.1401266724000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542102.1401266724000.26.1401268157075@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated GTNPORTAL-3497:
-----------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059036


>  Portlet in Dashboard is broken for the first access
> ----------------------------------------------------
>
>                 Key: GTNPORTAL-3497
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3497
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Juraci Paix?o Kr?hling
>            Assignee: Juraci Paix?o Kr?hling
>
> From BZ 1059036: 
> If you configure a richfaces portlet in dashboard template, the portlet may break for the first access by a newly created user.
> https://bugzilla.redhat.com/show_bug.cgi?id=1059036



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


From issues at jboss.org  Wed May 28 07:21:17 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Wed, 28 May 2014 07:21:17 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3498) Errors on
	TestSocialNetworkService
In-Reply-To: <JIRA.12542132.1401276072234@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542132.1401276072234@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542132.1401276072234.410.1401276077362@jira02.app.mwc.hst.phx2.redhat.com>

Lucas Ponce created GTNPORTAL-3498:
--------------------------------------

             Summary: Errors on TestSocialNetworkService
                 Key: GTNPORTAL-3498
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3498
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Lucas Ponce
            Assignee: Lucas Ponce


Due GTNPORTAL-3365 some tests gets some unexpected exceptions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 07:23:16 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Wed, 28 May 2014 07:23:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3498) Errors on
	TestSocialNetworkService
In-Reply-To: <JIRA.12542132.1401276072000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542132.1401276072000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542132.1401276072000.423.1401276196493@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3498:
-----------------------------------

    Attachment: org.gatein.security.oauth.test.TestSocialNetworkService.txt


> Errors on TestSocialNetworkService
> ----------------------------------
>
>                 Key: GTNPORTAL-3498
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3498
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>         Attachments: org.gatein.security.oauth.test.TestSocialNetworkService.txt
>
>
> Due GTNPORTAL-3365 some tests gets some unexpected exceptions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 07:31:16 2014
From: issues at jboss.org (Lucas Ponce (JIRA))
Date: Wed, 28 May 2014 07:31:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3498) Errors on
	TestSocialNetworkService
In-Reply-To: <JIRA.12542132.1401276072000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542132.1401276072000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542132.1401276072000.451.1401276676294@jira02.app.mwc.hst.phx2.redhat.com>


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

Lucas Ponce updated GTNPORTAL-3498:
-----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/gatein/gatein-portal/pull/867


> Errors on TestSocialNetworkService
> ----------------------------------
>
>                 Key: GTNPORTAL-3498
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3498
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>         Attachments: org.gatein.security.oauth.test.TestSocialNetworkService.txt
>
>
> Due GTNPORTAL-3365 some tests gets some unexpected exceptions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 16:17:15 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 28 May 2014 16:17:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to
 customize login validation and accounts expiration
In-Reply-To: <JIRA.12533491.1393506528000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533491.1393506528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533491.1393506528000.2170.1401308235568@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 973835|https://bugzilla.redhat.com/show_bug.cgi?id=973835] from ON_QA to VERIFIED

>  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
>      Security Level: Public(Everyone can see) 
>            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.2.3#6260)


From issues at jboss.org  Wed May 28 22:11:15 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Wed, 28 May 2014 22:11:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3499) esult of Rest API
 contains original host when Gatein runs behind apache server
In-Reply-To: <JIRA.12542260.1401329432454@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542260.1401329432454@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542260.1401329432454.2506.1401329475500@jira02.app.mwc.hst.phx2.redhat.com>

Tran Trung Thanh created GTNPORTAL-3499:
-------------------------------------------

             Summary: esult of Rest API contains original host when Gatein runs behind apache server
                 Key: GTNPORTAL-3499
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3499
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.5.9.Final
            Reporter: Tran Trung Thanh


- Configure Gatein with apache 2 with HTTP by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
- Start Gatein server at localhost:8080
- Access Gatein service by using address of apache for example example.localhost
- Login as john
- Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/john/pages/Tab_Default
-> The result contains the original host
{noformat}
{"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default"}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.xml","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.zip","type":"application/zip","method":"get"}}]}
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 22:47:15 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Wed, 28 May 2014 22:47:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3499) Result of Rest API
 contains original host when Gatein runs behind apache server
In-Reply-To: <JIRA.12542260.1401329432000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542260.1401329432000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542260.1401329432000.2517.1401331635448@jira02.app.mwc.hst.phx2.redhat.com>


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

Tran Trung Thanh updated GTNPORTAL-3499:
----------------------------------------

    Summary: Result of Rest API contains original host when Gatein runs behind apache server  (was: esult of Rest API contains original host when Gatein runs behind apache server)


> Result of Rest API contains original host when Gatein runs behind apache server
> -------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3499
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3499
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Tran Trung Thanh
>
> - Configure Gatein with apache 2 with HTTP by following
> http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
> - Start Gatein server at localhost:8080
> - Access Gatein service by using address of apache for example example.localhost
> - Login as john
> - Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/john/pages/Tab_Default
> -> The result contains the original host
> {noformat}
> {"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default"}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.xml","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.zip","type":"application/zip","method":"get"}}]}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:15:16 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Thu, 29 May 2014 03:15:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3499) Result of Rest API
 contains original host when Gatein runs behind apache server via HTTP
 protocal
In-Reply-To: <JIRA.12542260.1401329432000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542260.1401329432000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542260.1401329432000.2821.1401347716654@jira02.app.mwc.hst.phx2.redhat.com>


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

Tran Trung Thanh updated GTNPORTAL-3499:
----------------------------------------

        Summary: Result of Rest API contains original host when Gatein runs behind apache server via HTTP protocal  (was: Result of Rest API contains original host when Gatein runs behind apache server)
    Description: 
- Configure eXo Platform with apache 2 via HTTP protocol by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.ConnectViaHTTP.html
- Start Gatein server at localhost:8080
- Access Gatein service by using address of apache for example example.localhost
- Login as john
- Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/john/pages/Tab_Default
-> The result contains the original host
{noformat}
{"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default"}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.xml","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.zip","type":"application/zip","method":"get"}}]}
{noformat}

Note that: No problem when configuring apache front-end with ajp.

  was:
- Configure Gatein with apache 2 with HTTP by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
- Start Gatein server at localhost:8080
- Access Gatein service by using address of apache for example example.localhost
- Login as john
- Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/john/pages/Tab_Default
-> The result contains the original host
{noformat}
{"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default"}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.xml","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.zip","type":"application/zip","method":"get"}}]}
{noformat}



> Result of Rest API contains original host when Gatein runs behind apache server via HTTP protocal
> -------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3499
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3499
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Tran Trung Thanh
>
> - Configure eXo Platform with apache 2 via HTTP protocol by following
> http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.ConnectViaHTTP.html
> - Start Gatein server at localhost:8080
> - Access Gatein service by using address of apache for example example.localhost
> - Login as john
> - Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/john/pages/Tab_Default
> -> The result contains the original host
> {noformat}
> {"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default"}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.xml","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/pages/Tab_Default.zip","type":"application/zip","method":"get"}}]}
> {noformat}
> Note that: No problem when configuring apache front-end with ajp.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:17:15 2014
From: issues at jboss.org (Tran Trung Thanh (JIRA))
Date: Thu, 29 May 2014 03:17:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3496) Services Management
 Gadget does not work when eXoPlatform server runs behind Apache server via
 HTTP protocol
In-Reply-To: <JIRA.12542099.1401265862000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542099.1401265862000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542099.1401265862000.2823.1401347835718@jira02.app.mwc.hst.phx2.redhat.com>


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

Tran Trung Thanh updated GTNPORTAL-3496:
----------------------------------------

        Summary: Services Management Gadget does not work when eXoPlatform server runs behind Apache server via HTTP protocol  (was: Services Management Gadget does not work when eXoPlatform server runs behind Apache server)
    Description: 
- Configure eXo Platform with apache 2 via HTTP protocol by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.ConnectViaHTTP.html
- Start GateIn server
- Access Gatein by using address of apache 
- Login as root
- Go to Group > Administration Services Management
-> There is a warning and no service is displayed.

Note that: No problem when configuring apache front-end with ajp.

  was:
- Configure Gatein with apache 2 in HTTP mode by following
http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.html
- Start GateIn server
- Access Gatein by using address of apache 
- Login as root
- Go to Group > Administration Services Management
-> There is a warning and no service is displayed.



> Services Management Gadget does not work when eXoPlatform server runs behind Apache server via HTTP protocol
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-3496
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3496
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.9.Final
>            Reporter: Tran Trung Thanh
>         Attachments: Gatein Services-Management.png
>
>
> - Configure eXo Platform with apache 2 via HTTP protocol by following
> http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.SetupApacheFrontend.ConnectViaHTTP.html
> - Start GateIn server
> - Access Gatein by using address of apache 
> - Login as root
> - Go to Group > Administration Services Management
> -> There is a warning and no service is displayed.
> Note that: No problem when configuring apache front-end with ajp.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:35:15 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 29 May 2014 03:35:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3488) Do NOT log ERROR for
 client abort exception
In-Reply-To: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541674.1400833710000.2851.1401348915816@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3488:
----------------------------------

    Summary: Do NOT log ERROR for client abort exception  (was: ERROR | Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css when client abort)


> Do NOT log ERROR for client abort exception
> -------------------------------------------
>
>                 Key: GTNPORTAL-3488
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3488
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>
> Case to reproduce:
> - Duplicate content of css file: $GATEIN_TOMCAT/webapps/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css (make it contain many css define)
> - Run gatein
> - Goto homepage
> - Goto http://localhost:8080/portal/skins/3.9.0.Alpha01-SNAPSHOT/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin-lt.css
> - Press and keep the keyboard Ctrl+R to multi reload page
> - Have many exception *ERROR* on console.
> {code}
> [http-bio-8080-exec-4] ERROR org.exoplatform.portal.resource.SkinResourceRequestHandler - Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
> ClientAbortException:  java.net.SocketException: Broken pipe
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388)
> 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
> 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413)
> 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:84)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler$1.write(SkinResourceRequestHandler.java:74)
> 	at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:465)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler.execute(SkinResourceRequestHandler.java:101)
> 	at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
> 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
> 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
> 	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92)
> 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
> 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> 	at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:722)
> Caused by: java.net.SocketException: Broken pipe
> 	at java.net.SocketOutputStream.socketWrite0(Native Method)
> 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> 	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> 	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:371)
> 	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:240)
> 	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:119)
> 	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:192)
> 	at org.apache.coyote.Response.doWrite(Response.java:505)
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383)
> 	... 68 more
> {code}
> For this broken pipe exception, we should catch up the exception and keep it silent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:37:15 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 29 May 2014 03:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3488) Do NOT log ERROR for
 client abort exception
In-Reply-To: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541674.1400833710000.2858.1401349035706@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3488:
----------------------------------

    Fix Version/s: 3.7.2.Final
                   3.9.0.Final


> Do NOT log ERROR for client abort exception
> -------------------------------------------
>
>                 Key: GTNPORTAL-3488
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3488
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.7.2.Final, 3.9.0.Final
>
>
> Case to reproduce:
> - Duplicate content of css file: $GATEIN_TOMCAT/webapps/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css (make it contain many css define)
> - Run gatein
> - Goto homepage
> - Goto http://localhost:8080/portal/skins/3.9.0.Alpha01-SNAPSHOT/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin-lt.css
> - Press and keep the keyboard Ctrl+R to multi reload page
> - Have many exception *ERROR* on console.
> {code}
> [http-bio-8080-exec-4] ERROR org.exoplatform.portal.resource.SkinResourceRequestHandler - Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
> ClientAbortException:  java.net.SocketException: Broken pipe
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388)
> 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
> 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413)
> 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:84)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler$1.write(SkinResourceRequestHandler.java:74)
> 	at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:465)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler.execute(SkinResourceRequestHandler.java:101)
> 	at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
> 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
> 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
> 	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92)
> 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
> 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> 	at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:722)
> Caused by: java.net.SocketException: Broken pipe
> 	at java.net.SocketOutputStream.socketWrite0(Native Method)
> 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> 	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> 	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:371)
> 	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:240)
> 	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:119)
> 	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:192)
> 	at org.apache.coyote.Response.doWrite(Response.java:505)
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383)
> 	... 68 more
> {code}
> For this broken pipe exception, we should catch up the exception and keep it silent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:37:15 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 29 May 2014 03:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3488) Do NOT log ERROR for
 client abort exception
In-Reply-To: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541674.1400833710000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541674.1400833710000.2860.1401349035858@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3488:
----------------------------------

        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Do NOT log ERROR for client abort exception
> -------------------------------------------
>
>                 Key: GTNPORTAL-3488
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3488
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>             Fix For: 3.7.2.Final, 3.9.0.Final
>
>
> Case to reproduce:
> - Duplicate content of css file: $GATEIN_TOMCAT/webapps/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css (make it contain many css define)
> - Run gatein
> - Goto homepage
> - Goto http://localhost:8080/portal/skins/3.9.0.Alpha01-SNAPSHOT/eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin-lt.css
> - Press and keep the keyboard Ctrl+R to multi reload page
> - Have many exception *ERROR* on console.
> {code}
> [http-bio-8080-exec-4] ERROR org.exoplatform.portal.resource.SkinResourceRequestHandler - Could not render css /eXoResources/skin/DefaultSkin/portal/webui/component/UIPortalApplicationSkin.css
> ClientAbortException:  java.net.SocketException: Broken pipe
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:388)
> 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
> 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:413)
> 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:401)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
> 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:84)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler$1.write(SkinResourceRequestHandler.java:74)
> 	at org.exoplatform.portal.resource.SkinService.renderCSS(SkinService.java:465)
> 	at org.exoplatform.portal.resource.SkinResourceRequestHandler.execute(SkinResourceRequestHandler.java:101)
> 	at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
> 	at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
> 	at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
> 	at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:72)
> 	at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:92)
> 	at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
> 	at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:68)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.web.security.impersonation.ImpersonationFilter.doFilter(ImpersonationFilter.java:84)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:122)
> 	at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:55)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> 	at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:722)
> Caused by: java.net.SocketException: Broken pipe
> 	at java.net.SocketOutputStream.socketWrite0(Native Method)
> 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
> 	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> 	at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
> 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:371)
> 	at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:240)
> 	at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:119)
> 	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:192)
> 	at org.apache.coyote.Response.doWrite(Response.java:505)
> 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383)
> 	... 68 more
> {code}
> For this broken pipe exception, we should catch up the exception and keep it silent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 03:53:15 2014
From: issues at jboss.org (Trong Tran (JIRA))
Date: Thu, 29 May 2014 03:53:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3482) Deprecated class of
	UserImpl
In-Reply-To: <JIRA.12541070.1400486823000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541070.1400486823000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541070.1400486823000.2876.1401349995990@jira02.app.mwc.hst.phx2.redhat.com>


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

Trong Tran updated GTNPORTAL-3482:
----------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 3.7.2.Final
                   3.9.0.Final
       Resolution: Done


> Deprecated class of UserImpl
> ----------------------------
>
>                 Key: GTNPORTAL-3482
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3482
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Tuyen Nguyen The
>            Assignee: Tuyen Nguyen The
>            Priority: Minor
>             Fix For: 3.7.2.Final, 3.9.0.Final
>
>
> *org.exoplatform.services.organization.idm.UserImpl* class was created in order to make a workaround to display the *userName* if exist.
> This class should be *deleted* in Gatein according to a *TODO* annotation mentioned in top. In fact, the related issue *was fixed* in JCR 1.15, see:
> https://issues.jboss.org/browse/EXOJCR-1780.
>  
> the correction was made into the class *org.exoplatform.services.organization.impl.UserImpl* on method getFullName (responsible for displaying the username)
> {code:title=UserImpl.java|borderStyle=solid}
> // wrapper method
>    public String getFullName()
>    {
>       return getDisplayName();
>    }
> public String getDisplayName()
>    {
>       return displayName != null ? displayName : getFirstName() + " " + getLastName();
>    }
> {code} 
> So no need to  *...organization.idm.UserImpl* class any more as the class *org.exoplatform.services.organization.impl.UserImpl* was fixed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 03:29:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 03:29:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3396) Support all possible
 js module dependency names in define()
In-Reply-To: <JIRA.12532199.1392377025000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12532199.1392377025000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12532199.1392377025000.5640.1401434955533@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3396.
-------------------------------------

    Fix Version/s: 3.8.0.Final
       Resolution: Done


Fixed by https://github.com/gatein/gatein-portal/commit/1554d8b0b6855527334eb7233707a6c01117cc00

> Support all possible js module dependency names in define()
> -----------------------------------------------------------
>
>                 Key: GTNPORTAL-3396
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3396
>             Project: GateIn Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.7.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.8.0.Final
>
>
> Let's have a dependeny graph as simple as:
>   dojo/sniff depends on dojo/has
> Given that both dojo/sniff and dojo/has live in the same directory named "dojo", the dojo/sniff.js file starts with
>   define(["./has"], function(has){
> Note the relative module path name "./has" there. Relative paths comply with the AMD spec [1] and "../<someModule>" should also be supported.
> Using such relative module names in define() does not seem to work in GateIn.
> [1] https://github.com/amdjs/amdjs-api/wiki/AMD 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 03:37:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 03:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3476) Obsolete version
 numbers in jboss packaging
In-Reply-To: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540346.1399643839000.5644.1401435435622@jira02.app.mwc.hst.phx2.redhat.com>


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

Work on GTNPORTAL-3476 started by Peter Palaga.

> Obsolete version numbers in jboss packaging
> -------------------------------------------
>
>                 Key: GTNPORTAL-3476
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3476
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.9.0.Final
>
>
> The versions in jboss packaging are still on 3.8.0.Beta02-SNAPSHOT, see https://github.com/gatein/gatein-portal/blob/3.8.0.Final/packaging/jboss/pom.xml#L6
> It is probably, because packaging/jboss is not included by default and I released 3.8.0.Final without the new dedicated profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 03:37:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 03:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3476) Obsolete version
 numbers in jboss packaging
In-Reply-To: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540346.1399643839000.5646.1401435435820@jira02.app.mwc.hst.phx2.redhat.com>


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

Work on GTNPORTAL-3476 stopped by Peter Palaga.

> Obsolete version numbers in jboss packaging
> -------------------------------------------
>
>                 Key: GTNPORTAL-3476
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3476
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.9.0.Final
>
>
> The versions in jboss packaging are still on 3.8.0.Beta02-SNAPSHOT, see https://github.com/gatein/gatein-portal/blob/3.8.0.Final/packaging/jboss/pom.xml#L6
> It is probably, because packaging/jboss is not included by default and I released 3.8.0.Final without the new dedicated profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 03:37:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 03:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3476) Obsolete version
 numbers in jboss packaging
In-Reply-To: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540346.1399643839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540346.1399643839000.5648.1401435435925@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga resolved GTNPORTAL-3476.
-------------------------------------

    Fix Version/s: 3.9.0.Final
       Resolution: Done


Fixed by https://github.com/gatein/gatein-portal/commit/8970fd4eadd6752fdd3969f19c9a8b4bb77935ed

> Obsolete version numbers in jboss packaging
> -------------------------------------------
>
>                 Key: GTNPORTAL-3476
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3476
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.8.0.Final
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.9.0.Final
>
>
> The versions in jboss packaging are still on 3.8.0.Beta02-SNAPSHOT, see https://github.com/gatein/gatein-portal/blob/3.8.0.Final/packaging/jboss/pom.xml#L6
> It is probably, because packaging/jboss is not included by default and I released 3.8.0.Final without the new dedicated profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 03:55:16 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 30 May 2014 03:55:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3457) Unify gatein jgroups
	configurations
In-Reply-To: <JIRA.12538962.1398331821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538962.1398331821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538962.1398331821000.5676.1401436516397@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1090675|https://bugzilla.redhat.com/show_bug.cgi?id=1090675] from POST to ON_QA

> Unify gatein jgroups configurations
> -----------------------------------
>
>                 Key: GTNPORTAL-3457
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3457
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> GateIn cluster configuration is defined under:
> ./gatein/gatein.ear/portal.war/WEB-INF/classes/jgroups/ folder.
> There are two separate jgroups configurations for exo.jcr and idm subsystems that can be merged into one.
> Also, some properties has to be reviewed, as binding ips and enable_diagnostics.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 10:11:16 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 30 May 2014 10:11:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3457) Unify gatein jgroups
	configurations
In-Reply-To: <JIRA.12538962.1398331821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538962.1398331821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538962.1398331821000.6506.1401459076440@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Tomas Kyjovsky <tkyjovsk at redhat.com> changed the Status of [bug 1090675|https://bugzilla.redhat.com/show_bug.cgi?id=1090675] from ON_QA to VERIFIED

> Unify gatein jgroups configurations
> -----------------------------------
>
>                 Key: GTNPORTAL-3457
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3457
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Lucas Ponce
>            Assignee: Lucas Ponce
>             Fix For: 3.8.0.Final
>
>
> GateIn cluster configuration is defined under:
> ./gatein/gatein.ear/portal.war/WEB-INF/classes/jgroups/ folder.
> There are two separate jgroups configurations for exo.jcr and idm subsystems that can be merged into one.
> Also, some properties has to be reviewed, as binding ips and enable_diagnostics.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 12:57:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 12:57:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3500)
 testMemoryLeakWithMultiThread fails sometimes
In-Reply-To: <JIRA.12542430.1401469023809@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542430.1401469023809@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542430.1401469023809.6943.1401469035557@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3500:
---------------------------------------

             Summary: testMemoryLeakWithMultiThread fails sometimes
                 Key: GTNPORTAL-3500
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3500
             Project: GateIn Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga


Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304
org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace:
junit.framework.AssertionFailedError
	at junit.framework.Assert.fail(Assert.java:48)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertTrue(Assert.java:27)
	at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

The line where it fails is 

assertTrue(cache.getCacheSize() <= 10);

Version-Release number of selected component (if applicable):
JBoss Portal 6.2.0.ER2

How reproducible:
Sometimes, 1/10 or even less. Happens both on Jenkins and desktop.

Steps to Reproduce:
Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests.

Actual results:
Test fails

Expected results:
Not sure if the subject under the test is broken or the test itself.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 12:59:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 12:59:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3500)
 testMemoryLeakWithMultiThread fails sometimes
In-Reply-To: <JIRA.12542430.1401469023000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542430.1401469023000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542430.1401469023000.6946.1401469155785@jira02.app.mwc.hst.phx2.redhat.com>


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

Peter Palaga updated GTNPORTAL-3500:
------------------------------------

    Description: 
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304
org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace:
junit.framework.AssertionFailedError
	at junit.framework.Assert.fail(Assert.java:48)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertTrue(Assert.java:27)
	at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

The line where it fails is 

assertTrue(cache.getCacheSize() <= 10);

Version-Release number of selected component (if applicable):
GateIn 3.8.x or 3.9.x

Reproducible sometimes: 1/10 or even less. Happens both on Jenkins and desktop.

Steps to Reproduce:
Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests repeatedly until it fails.

Actual results:
Test fails

Expected results:
Not sure if the subject under the test is broken or the test itself.

  was:
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304
org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace:
junit.framework.AssertionFailedError
	at junit.framework.Assert.fail(Assert.java:48)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertTrue(Assert.java:27)
	at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

The line where it fails is 

assertTrue(cache.getCacheSize() <= 10);

Version-Release number of selected component (if applicable):
JBoss Portal 6.2.0.ER2

How reproducible:
Sometimes, 1/10 or even less. Happens both on Jenkins and desktop.

Steps to Reproduce:
Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests.

Actual results:
Test fails

Expected results:
Not sure if the subject under the test is broken or the test itself.



> testMemoryLeakWithMultiThread fails sometimes
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3500
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3500
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304
> org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace:
> junit.framework.AssertionFailedError
> 	at junit.framework.Assert.fail(Assert.java:48)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertTrue(Assert.java:27)
> 	at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> The line where it fails is 
> assertTrue(cache.getCacheSize() <= 10);
> Version-Release number of selected component (if applicable):
> GateIn 3.8.x or 3.9.x
> Reproducible sometimes: 1/10 or even less. Happens both on Jenkins and desktop.
> Steps to Reproduce:
> Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests repeatedly until it fails.
> Actual results:
> Test fails
> Expected results:
> Not sure if the subject under the test is broken or the test itself.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 15:37:15 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 15:37:15 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3501) Introduce XML schema
 validation for gatein-resources.xml
In-Reply-To: <JIRA.12542441.1401478549470@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542441.1401478549470@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542441.1401478549470.7269.1401478635571@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3501:
---------------------------------------

             Summary: Introduce XML schema validation for gatein-resources.xml
                 Key: GTNPORTAL-3501
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3501
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


There are several lines of code that indicate that {{org.exoplatform.commons.xml.XMLValidator}} was originally designed to check if a given document complies with an XML schema declared in it:
{code:java}
factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");        factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource", schemas);
factory.setNamespaceAware(true);
factory.setValidating(true);
{code}
However, there were no tests checking if the validation works and indeed, it does not. It is out of the present scope to investigate what is wrong with {{XMLValidator}} and how it can be corrected, because it is too general to be used for validating {{gatein-resources.xml}} at this point. The main problem is that if we have not validated so far, there must be a lot of schema-incompatible {{gatein-resources.xml}} out there in the wild that were silently accepted by the portal in the past. Therefore, we cannot start validating all {{gatein-resources.xml}} files now. 

To meet the natural expectation that inputs are properly validated to widest possible extent, I propose to start validating now, but only {{gatein-resources.xml}} documents that use the namespace {{http://www.gatein.org/xml/ns/gatein_resources_1_5}} or newer. {{gatein_resources_1_5.xsd}} will be introduced these days with fixing 
GTNPORTAL-3485 and GTNPORTAL-3487. In this way we can stay backwards-compatible and start validating from now on.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 16:31:16 2014
From: issues at jboss.org (Peter Palaga (JIRA))
Date: Fri, 30 May 2014 16:31:16 -0400 (EDT)
Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3502) Commnon deployer for
 JavaScript and skin services
In-Reply-To: <JIRA.12542445.1401481836642@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542445.1401481836642@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542445.1401481836642.7324.1401481876390@jira02.app.mwc.hst.phx2.redhat.com>

Peter Palaga created GTNPORTAL-3502:
---------------------------------------

             Summary: Commnon deployer for JavaScript and skin services
                 Key: GTNPORTAL-3502
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3502
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Peter Palaga
            Assignee: Peter Palaga


At present, there are two independent deployers for JavaScript and skin services: {{GateInSkinConfigDeployer}} and {{JavascriptConfigDeployer}}. There are two problems with that:

(1) Both of them parse {{gatein-resources.xml}} independently, which is a performance drawback.

(2) They can succeed or fail independently, e.g. in case there is some meaningless declaration in {{gatein-resources.xml}}, which can lead to an inconsistent state of the portal.

An ideal solution for (2) would be to rollback deployment of the whole web application, but unfortunately, the present design of the portal does not allow for that. Therefore, I propose to keep at least the two services consistent by introducing a common deployer, that will grant that resources will either succeed to be added to both or to none. Problem (1) will be solved by that too.





--
This message was sent by Atlassian JIRA
(v6.2.3#6260)