From issues at jboss.org Mon Mar 3 04:24:48 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 3 Mar 2014 04:24:48 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3398) Improve gatein oauth integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3398?focusedWorklogId=12430676&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430676 ] Trong Tran logged work on GTNPORTAL-3398: ----------------------------------------- Author: Trong Tran Created on: 03/Mar/14 4:24 AM Start Date: 03/Mar/14 4:24 AM Worklog Time Spent: 1 day, 4 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 day, 4 hours) Time Spent: 2 days (was: 4 hours) Worklog Id: (was: 12430676) > Improve gatein oauth integration > -------------------------------- > > Key: GTNPORTAL-3398 > URL: https://issues.jboss.org/browse/GTNPORTAL-3398 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Implement improvements in gatein oauth integration follow by spec: https://community.jboss.org/wiki/OAuthAuthenticationWithSocialNetworks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 04:28:47 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 3 Mar 2014 04:28:47 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3398) Improve gatein oauth integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran resolved GTNPORTAL-3398. ----------------------------------- Fix Version/s: 3.7.0.Final 3.8.0.Final Resolution: Done > Improve gatein oauth integration > -------------------------------- > > Key: GTNPORTAL-3398 > URL: https://issues.jboss.org/browse/GTNPORTAL-3398 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Fix For: 3.7.0.Final, 3.8.0.Final > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Implement improvements in gatein oauth integration follow by spec: https://community.jboss.org/wiki/OAuthAuthenticationWithSocialNetworks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 07:08:47 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Mon, 3 Mar 2014 07:08:47 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3328) Automatic way to update all sites at once (Portal, groups and user sites) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated GTNPORTAL-3328: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.0.Final Resolution: Done > 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.Final > > > This feature is described in the following document: > https://community.jboss.org/wiki/AutomaticWayToUpdateAllSitesAtOncePortalGroupsAndUserSites -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 07:10:48 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Mon, 3 Mar 2014 07:10:48 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3395) Eliminate warning ISPN000190: Use of the 'loader' element... In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated GTNPORTAL-3395: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.0.Final Resolution: Done > Eliminate warning ISPN000190: Use of the 'loader' element... > ------------------------------------------------------------ > > Key: GTNPORTAL-3395 > URL: https://issues.jboss.org/browse/GTNPORTAL-3395 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Peter Palaga > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > This warning gets logged five times during GateIn startup on JBoss AS 7.1.1 > {code:none} > WARN [org.infinispan.configuration.parsing.Parser52] (MSC service thread 1-1) ISPN000190: Use of the 'loader' element to configure a store is deprecated, please use the 'store' element instead > {code} > Expected: no warnings during default GateIn startup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 08:46:49 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 08:46:49 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3401) Encoding of "&" characters in URLs. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949336#comment-12949336 ] RH Bugzilla Integration commented on GTNPORTAL-3401: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065987|https://bugzilla.redhat.com/show_bug.cgi?id=1065987] from NEW to ASSIGNED > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 08:56:47 2014 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Mon, 3 Mar 2014 08:56:47 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-372) Exception appears in log while using WSRP portlets with PortletBridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949341#comment-12949341 ] Vlastislav Ramik commented on GTNWSRP-372: ------------------------------------------ It would be possible to run tests when the test suite will be upgraded to gatein-master. I suppose during DR. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 09:02:48 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 09:02:48 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3406: -------------------------------------- Summary: 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: Feature Request Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 09:04:51 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 09:04:51 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3406: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1065991 > 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: Feature Request > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 09:06:50 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 09:06:50 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949345#comment-12949345 ] RH Bugzilla Integration commented on GTNPORTAL-3406: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065991|https://bugzilla.redhat.com/show_bug.cgi?id=1065991] from NEW to ASSIGNED > 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: Feature Request > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 10:51:37 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 10:51:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3407: -------------------------------------- Summary: Avoid ID elements starting with number Key: GTNPORTAL-3407 URL: https://issues.jboss.org/browse/GTNPORTAL-3407 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce GateIn produces XHTML 1.0 Strict type documents. For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 10:53:37 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 10:53:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3408) Avoid ID elements starting with number In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3408: -------------------------------------- Summary: Avoid ID elements starting with number Key: GTNPORTAL-3408 URL: https://issues.jboss.org/browse/GTNPORTAL-3408 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce GateIn produces XHTML 1.0 Strict type documents. For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:16:38 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 11:16:38 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3408) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce closed GTNPORTAL-3408. ---------------------------------- Resolution: Duplicate Issue > Avoid ID elements starting with number > -------------------------------------- > > Key: GTNPORTAL-3408 > URL: https://issues.jboss.org/browse/GTNPORTAL-3408 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:18:37 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 11:18:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3406: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:18:38 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 11:18:38 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3407: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > 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 > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:38:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 11:38:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3407: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1065997 > 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 > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:42:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 11:42:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949427#comment-12949427 ] RH Bugzilla Integration commented on GTNPORTAL-3407: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065997|https://bugzilla.redhat.com/show_bug.cgi?id=1065997] from NEW to ASSIGNED > 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 > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:52:36 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Mon, 3 Mar 2014 11:52:36 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3409: -------------------------------------- Summary: 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 11:52:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 11:52:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3409: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1066001 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 22:48:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 22:48:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3362) Add examples for Inter Portlet Communication In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3362: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 22:48:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 22:48:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3369) Add Public Render Parameter support at URL level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3369: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726) > 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.Final > > > Add support to pass Public Render Parameters at URL level -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 22:54:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 22:54:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3361) Allow more flexible cache-control header per portal In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3361: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=811126, https://bugzilla.redhat.com/show_bug.cgi?id=1072146 (was: https://bugzilla.redhat.com/show_bug.cgi?id=811126) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 22:54:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 22:54:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3361) Allow more flexible cache-control header per portal In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949586#comment-12949586 ] RH Bugzilla Integration commented on GTNPORTAL-3361: ---------------------------------------------------- Jared MORGAN changed the Status of [bug 1072146|https://bugzilla.redhat.com/show_bug.cgi?id=1072146] from NEW to ASSIGNED > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 22:56:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 22:56:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3363) Provide feedback on logs when gadget is not white-listed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3363: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=794468, https://bugzilla.redhat.com/show_bug.cgi?id=1072147 (was: https://bugzilla.redhat.com/show_bug.cgi?id=794468) > Provide feedback on logs when gadget is not white-listed > -------------------------------------------------------- > > Key: GTNPORTAL-3363 > URL: https://issues.jboss.org/browse/GTNPORTAL-3363 > 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 a gadget is not white-listed, the ProxyFilterService rejects the loading of the contents, but provides no hints on the logs about it, making the user to believe that the gadget might be at fault. A solution is to log at INFO level that access to it has been blocked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 23:06:37 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 3 Mar 2014 23:06:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 23:06:37 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 3 Mar 2014 23:06:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Sprint: Sprint 95 > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 23:26:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 23:26:36 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3402: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=973835, https://bugzilla.redhat.com/show_bug.cgi?id=1072150 (was: https://bugzilla.redhat.com/show_bug.cgi?id=973835) > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 3 23:32:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 3 Mar 2014 23:32:36 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949590#comment-12949590 ] RH Bugzilla Integration commented on GTNPORTAL-3402: ---------------------------------------------------- Jared MORGAN changed the Status of [bug 1072150|https://bugzilla.redhat.com/show_bug.cgi?id=1072150] from NEW to ASSIGNED > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 00:12:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 00:12:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3362) Add examples for Inter Portlet Communication In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3362: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145, https://bugzilla.redhat.com/show_bug.cgi?id=1072173 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 00:12:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 00:12:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3369) Add Public Render Parameter support at URL level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3369: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145, https://bugzilla.redhat.com/show_bug.cgi?id=1072173 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145) > 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.Final > > > Add support to pass Public Render Parameters at URL level -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 00:14:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 00:14:36 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3379) Provide a button/icon to reset the search string In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3379: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793647, https://bugzilla.redhat.com/show_bug.cgi?id=1072176 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793647) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 00:18:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 00:18:37 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3259) Configurable default view mode in page editor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3259: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1038554, https://bugzilla.redhat.com/show_bug.cgi?id=1072177 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1038554) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 01:23:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 01:23:16 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3328) Automatic way to update all sites at once (Portal, groups and user sites) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3328: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1038545, https://bugzilla.redhat.com/show_bug.cgi?id=1072188, https://bugzilla.redhat.com/show_bug.cgi?id=1072189 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1038545) > 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.Final > > > This feature is described in the following document: > https://community.jboss.org/wiki/AutomaticWayToUpdateAllSitesAtOncePortalGroupsAndUserSites -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 01:23:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 01:23:16 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3328) Automatic way to update all sites at once (Portal, groups and user sites) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3328: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1038545, https://bugzilla.redhat.com/show_bug.cgi?id=1072188, https://bugzilla.redhat.com/show_bug.cgi?id=1072189 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1038545) > 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.Final > > > This feature is described in the following document: > https://community.jboss.org/wiki/AutomaticWayToUpdateAllSitesAtOncePortalGroupsAndUserSites -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 02:25:33 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Tue, 4 Mar 2014 02:25:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: Tuyen Nguyen The created GTNPORTAL-3410: ------------------------------------------- Summary: Templates-cache is not share between nodes in cluster Key: GTNPORTAL-3410 URL: https://issues.jboss.org/browse/GTNPORTAL-3410 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tuyen Nguyen The Assignee: Tuyen Nguyen The Start by setting up a cluster environement with two nodes and start the nodes In Node 1: - Goto Sitemap page - Use editor to edit UISitemapTree.gtmpl - Goto sitemap page, it still old template because template is cached. - Use template management MBean to clear cache in node1 - Goto sitemap page again and we see the change In Node 2: - Goto sitemap page => NOK: sitemap page in node 2 still use old template OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 02:33:34 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Tue, 4 Mar 2014 02:33:34 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuyen Nguyen The updated GTNPORTAL-3410: ---------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/794 > Templates-cache is not share between nodes in cluster > ----------------------------------------------------- > > Key: GTNPORTAL-3410 > URL: https://issues.jboss.org/browse/GTNPORTAL-3410 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Start by setting up a cluster environement with two nodes and start the nodes > In Node 1: > - Goto Sitemap page > - Use editor to edit UISitemapTree.gtmpl > - Goto sitemap page, it still old template because template is cached. > - Use template management MBean to clear cache in node1 > - Goto sitemap page again and we see the change > In Node 2: > - Goto sitemap page > => NOK: sitemap page in node 2 still use old template > OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 04:21:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 04:21:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949644#comment-12949644 ] RH Bugzilla Integration commented on GTNPORTAL-3409: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1066001|https://bugzilla.redhat.com/show_bug.cgi?id=1066001] from NEW 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 04:25:34 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 4 Mar 2014 04:25:34 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML issues In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3411: -------------------------------------- Summary: 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 GateIn produces XHTML 1.0 Strict type documents. There are some minor markups not compliant with XHTML specification (i.e. empty list
    , or bad use of tag inside a block element). These issues don't affect to Portal behaviour but creates a non compliant markup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 04:25:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 04:25:35 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3411: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1066010 > 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 > > GateIn produces XHTML 1.0 Strict type documents. > There are some minor markups not compliant with XHTML specification (i.e. empty list
      , or bad use of tag inside a block element). > These issues don't affect to Portal behaviour but creates a non compliant markup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 04:25:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 04:25:35 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949649#comment-12949649 ] RH Bugzilla Integration commented on GTNPORTAL-3411: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1066010|https://bugzilla.redhat.com/show_bug.cgi?id=1066010] from NEW to ASSIGNED > 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 > > GateIn produces XHTML 1.0 Strict type documents. > There are some minor markups not compliant with XHTML specification (i.e. empty list
        , or bad use of tag inside a block element). > These issues don't affect to Portal behaviour but creates a non compliant markup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 04:49:34 2014 From: issues at jboss.org (Marek Posolda (JIRA)) Date: Tue, 4 Mar 2014 04:49:34 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949655#comment-12949655 ] Marek Posolda commented on GTNPORTAL-3410: ------------------------------------------ Hi, Can I ask about usecase for it? To me it seems that you need to change groovy templates just during development as far as I understand? On the other hand in production environment, the content of templates is always static. And usually cluster setup is used just during production, no? My point is that replication of static things like groovy templates is usually not needed as each cluster communication is adding some unecessarry overhead. > Templates-cache is not share between nodes in cluster > ----------------------------------------------------- > > Key: GTNPORTAL-3410 > URL: https://issues.jboss.org/browse/GTNPORTAL-3410 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Start by setting up a cluster environement with two nodes and start the nodes > In Node 1: > - Goto Sitemap page > - Use editor to edit UISitemapTree.gtmpl > - Goto sitemap page, it still old template because template is cached. > - Use template management MBean to clear cache in node1 > - Goto sitemap page again and we see the change > In Node 2: > - Goto sitemap page > => NOK: sitemap page in node 2 still use old template > OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 05:41:33 2014 From: issues at jboss.org (Tran Trung Thanh (JIRA)) Date: Tue, 4 Mar 2014 05:41:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949678#comment-12949678 ] Tran Trung Thanh commented on GTNPORTAL-3410: --------------------------------------------- Hi, This issue is created because of problem in eXo Platform. We use a template which is cached by TemplateService from gatein-portal in order to render inside a portlet. In cluster mode, we modify this template in a node and this modification is taken effect in this node but not in others. For more information, you can go https://jira.exoplatform.org/browse/EXOGTN-1758 Br, > Templates-cache is not share between nodes in cluster > ----------------------------------------------------- > > Key: GTNPORTAL-3410 > URL: https://issues.jboss.org/browse/GTNPORTAL-3410 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Start by setting up a cluster environement with two nodes and start the nodes > In Node 1: > - Goto Sitemap page > - Use editor to edit UISitemapTree.gtmpl > - Goto sitemap page, it still old template because template is cached. > - Use template management MBean to clear cache in node1 > - Goto sitemap page again and we see the change > In Node 2: > - Goto sitemap page > => NOK: sitemap page in node 2 still use old template > OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 06:11:33 2014 From: issues at jboss.org (Marek Posolda (JIRA)) Date: Tue, 4 Mar 2014 06:11:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949694#comment-12949694 ] Marek Posolda commented on GTNPORTAL-3410: ------------------------------------------ Ok, Thanks for the info > Templates-cache is not share between nodes in cluster > ----------------------------------------------------- > > Key: GTNPORTAL-3410 > URL: https://issues.jboss.org/browse/GTNPORTAL-3410 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Start by setting up a cluster environement with two nodes and start the nodes > In Node 1: > - Goto Sitemap page > - Use editor to edit UISitemapTree.gtmpl > - Goto sitemap page, it still old template because template is cached. > - Use template management MBean to clear cache in node1 > - Goto sitemap page again and we see the change > In Node 2: > - Goto sitemap page > => NOK: sitemap page in node 2 still use old template > OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 06:21:33 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Tue, 4 Mar 2014 06:21:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949701#comment-12949701 ] Tuyen Nguyen The commented on GTNPORTAL-3410: --------------------------------------------- This is PR for version 3.5.x - https://github.com/gatein/gatein-portal/pull/795 > Templates-cache is not share between nodes in cluster > ----------------------------------------------------- > > Key: GTNPORTAL-3410 > URL: https://issues.jboss.org/browse/GTNPORTAL-3410 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Start by setting up a cluster environement with two nodes and start the nodes > In Node 1: > - Goto Sitemap page > - Use editor to edit UISitemapTree.gtmpl > - Goto sitemap page, it still old template because template is cached. > - Use template management MBean to clear cache in node1 > - Goto sitemap page again and we see the change > In Node 2: > - Goto sitemap page > => NOK: sitemap page in node 2 still use old template > OK: template cache in 2 node must the same -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 08:53:35 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 4 Mar 2014 08:53:35 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3412) HTML5 data-* attributes not compatible with XHTML 1.0 In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3412: -------------------------------------- Summary: HTML5 data-* attributes not compatible with XHTML 1.0 Key: GTNPORTAL-3412 URL: https://issues.jboss.org/browse/GTNPORTAL-3412 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce GateIn produces XHTML 1.0 Strict type documents. mobile-integration/portlets/header portlet uses html5 data-* attributes not compliant with XHTML 1.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 08:55:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 4 Mar 2014 08:55:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949783#comment-12949783 ] Juraci Paix?o Kr?hling commented on GTNPORTAL-3402: --------------------------------------------------- This feature will be split into two parts: 1) On a first phase, we'll read the configuration files for a policy called "passwordpolicy". If this is available, then it will automatically be applied to the places where password is used as input before persisting (not when logging in, for instance, but when setting a new password). Ex.: gatein.validators.passwordpolicy.length.min=5 gatein.validators.passwordpolicy.length.max=50 gatein.validators.passwordpolicy.regexp=... 2) On a second step, customers will be able to add more policies, and select which one is active on the UI, via a select box. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 08:57:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 4 Mar 2014 08:57:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3413) Extension of feature GTNPORTAL-3402 In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNPORTAL-3413: ------------------------------------------------- Summary: Extension of feature GTNPORTAL-3402 Key: GTNPORTAL-3413 URL: https://issues.jboss.org/browse/GTNPORTAL-3413 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 This issue is for the second part of GTNPORTAL-3402 , which is to implement the UI allowing customers to select which password policy is currently active. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 12:19:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 4 Mar 2014 12:19:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3402: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/796 Test results: http://torii.gva.redhat.com/jenkins/job/gatein-portal-jbossas711-CustomizePasswordPolicies/2/ > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 4 12:19:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 4 Mar 2014 12:19:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949903#comment-12949903 ] RH Bugzilla Integration commented on GTNPORTAL-3402: ---------------------------------------------------- Juraci Paixao Krohling changed the Status of [bug 973835|https://bugzilla.redhat.com/show_bug.cgi?id=973835] from ASSIGNED to POST > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 09:07:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 5 Mar 2014 09:07:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNCOMMON-23) Add support for reversing character entities into chars In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNCOMMON-23: ----------------------------------------------- Summary: Add support for reversing character entities into chars Key: GTNCOMMON-23 URL: https://issues.jboss.org/browse/GTNCOMMON-23 Project: GateIn Common Issue Type: Feature Request Reporter: Juraci Paix?o Kr?hling The EntityEncoder currently has means to convert a given input into character entities, meant to be safe for display as HTML. As part of GTNPORTAL-3400, we need a way to do the reverse: get the char for a given character entity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 09:11:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 5 Mar 2014 09:11:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNCOMMON-23) Add support for reversing character entities into chars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNCOMMON-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950229#comment-12950229 ] Juraci Paix?o Kr?hling commented on GTNCOMMON-23: ------------------------------------------------- It seems I don't have permissions to link the PR into the issue, so, here it is: https://github.com/gatein/gatein-common/pull/5 > Add support for reversing character entities into chars > ------------------------------------------------------- > > Key: GTNCOMMON-23 > URL: https://issues.jboss.org/browse/GTNCOMMON-23 > Project: GateIn Common > Issue Type: Feature Request > Reporter: Juraci Paix?o Kr?hling > > The EntityEncoder currently has means to convert a given input into character entities, meant to be safe for display as HTML. As part of GTNPORTAL-3400, we need a way to do the reverse: get the char for a given character entity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 09:45:49 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 5 Mar 2014 09:45:49 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character issues in Dashboard tab name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling reassigned GTNPORTAL-3400: ------------------------------------------------- Assignee: Juraci Paix?o Kr?hling > 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) > Environment: Internet Explorer 9 > Reporter: Takayuki Konishi > Assignee: Juraci Paix?o Kr?hling > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 09:51:35 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 5 Mar 2014 09:51:35 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character issues in Dashboard tab name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3400: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/797 > 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) > Environment: Internet Explorer 9 > Reporter: Takayuki Konishi > Assignee: Juraci Paix?o Kr?hling > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 10:11:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 5 Mar 2014 10:11:39 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character issues in Dashboard tab name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950278#comment-12950278 ] RH Bugzilla Integration commented on GTNPORTAL-3400: ---------------------------------------------------- Juraci Paixao Krohling changed the Status of [bug 1070077|https://bugzilla.redhat.com/show_bug.cgi?id=1070077] from ASSIGNED to POST > 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) > Environment: Internet Explorer 9 > Reporter: Takayuki Konishi > Assignee: Juraci Paix?o Kr?hling > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 23:51:33 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Wed, 5 Mar 2014 23:51:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: Tuyen Nguyen The created GTNPORTAL-3414: ------------------------------------------- Summary: Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension Key: GTNPORTAL-3414 URL: https://issues.jboss.org/browse/GTNPORTAL-3414 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tuyen Nguyen The Assignee: Tuyen Nguyen The When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. So we should enable developer change the way to generate gatein user for each oauth provider via extension. To enable developer change the way to generate gatein user via extension, we will: - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: + Find OAuthUserGeneratorPlugin by oauthProviderType, + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 5 23:53:33 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Wed, 5 Mar 2014 23:53:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuyen Nguyen The updated GTNPORTAL-3414: ---------------------------------------- Attachment: linkedin-registration.png > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: linkedin-registration.png > > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 02:17:33 2014 From: issues at jboss.org (Martin Weiler (JIRA)) Date: Thu, 6 Mar 2014 02:17:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: Martin Weiler created GTNPORTAL-3415: ---------------------------------------- Summary: 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: Vu Viet Phuong Fix For: 3.5.9.Final, 3.7.0.Final 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 02:19:33 2014 From: issues at jboss.org (Martin Weiler (JIRA)) Date: Thu, 6 Mar 2014 02:19:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Weiler updated GTNPORTAL-3415: ------------------------------------- Fix Version/s: (was: 3.7.0.Final) (was: 3.5.9.Final) Description: 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 was: 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. Assignee: (was: Vu Viet Phuong) Git Pull Request: (was: https://github.com/gatein/gatein-portal/pull/779) > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 02:51:33 2014 From: issues at jboss.org (Martin Weiler (JIRA)) Date: Thu, 6 Mar 2014 02:51:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Weiler updated GTNPORTAL-3415: ------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/798 > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 05:27:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Thu, 6 Mar 2014 05:27:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNWSRP-373: ---------------------------------------------- Summary: Empty producer-handler-chains causes WARN Key: GTNWSRP-373 URL: https://issues.jboss.org/browse/GTNWSRP-373 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Juraci Paix?o Kr?hling Assignee: Juraci Paix?o Kr?hling We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element . For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 05:31:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Thu, 6 Mar 2014 05:31:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNWSRP-373: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-wsrp/pull/91 > Empty producer-handler-chains causes WARN > ------------------------------------------ > > Key: GTNWSRP-373 > URL: https://issues.jboss.org/browse/GTNWSRP-373 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > Assignee: Juraci Paix?o Kr?hling > > We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element . For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). > {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 6 05:33:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Thu, 6 Mar 2014 05:33:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNWSRP-373: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > Empty producer-handler-chains causes WARN > ------------------------------------------ > > Key: GTNWSRP-373 > URL: https://issues.jboss.org/browse/GTNWSRP-373 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > Assignee: Juraci Paix?o Kr?hling > > We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element . For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). > {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 7 04:53:33 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Fri, 7 Mar 2014 04:53:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuyen Nguyen The updated GTNPORTAL-3414: ---------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/799 > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: linkedin-registration.png > > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 7 08:56:33 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Fri, 7 Mar 2014 08:56:33 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-374) Improve admin GUI to be W3C compliant In-Reply-To: References: Message-ID: Lucas Ponce created GTNWSRP-374: ----------------------------------- Summary: Improve admin GUI to be W3C compliant Key: GTNWSRP-374 URL: https://issues.jboss.org/browse/GTNWSRP-374 Project: GateIn WSRP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Admin GUI Affects Versions: 2.2.11.Final Reporter: Lucas Ponce Assignee: Juraci Paix?o Kr?hling Fix For: 2.2.12.Final Admin GUI portlet has some issues incompatible with XHTML 1.0 spec: - tags rendered inside tags. - Repeated id attributes in generated JSF tags. - Other minor enhancenemtns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 7 09:10:34 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Fri, 7 Mar 2014 09:10:34 -0500 (EST) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-374) Improve admin GUI to be W3C compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNWSRP-374: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-wsrp/pull/92 > Improve admin GUI to be W3C compliant > ------------------------------------- > > Key: GTNWSRP-374 > URL: https://issues.jboss.org/browse/GTNWSRP-374 > Project: GateIn WSRP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Admin GUI > Affects Versions: 2.2.11.Final > Reporter: Lucas Ponce > Assignee: Juraci Paix?o Kr?hling > Fix For: 2.2.12.Final > > > Admin GUI portlet has some issues incompatible with XHTML 1.0 spec: > - tags rendered inside tags. > - Repeated id attributes in generated JSF tags. > - Other minor enhancenemtns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Mar 9 23:08:33 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Sun, 9 Mar 2014 23:08:33 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran reassigned GTNPORTAL-3404: ------------------------------------- Assignee: Tuyen Nguyen The > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 10 10:51:11 2014 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Mon, 10 Mar 2014 10:51:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3416) UI error message instead of HTTP400 when trying to impersonate twice In-Reply-To: References: Message-ID: Vlastislav Ramik created GTNPORTAL-3416: ------------------------------------------- Summary: UI error message instead of HTTP400 when trying to impersonate twice Key: GTNPORTAL-3416 URL: https://issues.jboss.org/browse/GTNPORTAL-3416 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: 3.8.0.Beta01-SNAPSHOT Reporter: Vlastislav Ramik Assignee: Marek Posolda Steps to reproduce: 1. sign in as a root 2. go to users and group management 3. impersonate root user 4. go to users and group management 5. try to impersonate user actual results: HTTP400 + ERROR message in log expected results: UI error message (not sure what about ERROR message in log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 10 11:25:11 2014 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Mon, 10 Mar 2014 11:25:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse In-Reply-To: References: Message-ID: Vlastislav Ramik created GTNPORTAL-3417: ------------------------------------------- Summary: 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 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: Disabled User While disabled user icons is green and the tag is: Enabled User All functionality works as expected but both the icon and the title is very confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 10 18:35:10 2014 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Mon, 10 Mar 2014 18:35:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-372) Exception appears in log while using WSRP portlets with PortletBridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951800#comment-12951800 ] Vlastislav Ramik commented on GTNWSRP-372: ------------------------------------------ There are links to passed tests: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6.1/view/WSRP/job/epp6_ui_selenium_tests_wsrp1_epp6_vs_epp6/59/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6.1/view/WSRP/job/epp6_ui_selenium_tests_wsrp2_epp6_vs_epp6/70/ > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:03:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:03:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Sprint: Sprint 95, Sprint 96 (was: Sprint 95) > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:05:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:05:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Original Estimate: 4 hours (was: 30 minutes) Remaining Estimate: 4 hours (was: 30 minutes) > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:07:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:07:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3415: ---------------------------------- Fix Version/s: 3.8.0.Final > 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 > Fix For: 3.8.0.Final > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:09:11 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:09:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3415: ---------------------------------- Sprint: Sprint 94, Sprint 96 (was: Sprint 94) > 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 > Fix For: 3.8.0.Final > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:09:11 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:09:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3414: ---------------------------------- Sprint: Sprint 96 > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: linkedin-registration.png > > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 05:55:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 05:55:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3414: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 06:05:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 11 Mar 2014 06:05:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3415: ---------------------------------- Original Estimate: 3 hours (was: 0 minutes) Remaining Estimate: 3 hours (was: 0 minutes) > 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 > Fix For: 3.8.0.Final > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:07:13 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 11 Mar 2014 07:07:13 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3418) Improve Redirect Admin UI to be W3C compliant In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3418: -------------------------------------- Summary: Improve Redirect Admin UI to be W3C compliant Key: GTNPORTAL-3418 URL: https://issues.jboss.org/browse/GTNPORTAL-3418 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:23:10 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Tue, 11 Mar 2014 07:23:10 -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: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga resolved GTNPORTAL-3370. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done > 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.Final > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:25:10 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Tue, 11 Mar 2014 07:25:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated GTNPORTAL-3402: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.0.Final Resolution: Done > 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.Final > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:27:10 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Tue, 11 Mar 2014 07:27:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga resolved GTNPORTAL-3415. ------------------------------------- Assignee: Peter Palaga Resolution: Done > 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.Final > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:29:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 11 Mar 2014 07:29:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3389) URL query parameters are not propagated when going through the authentication process In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951883#comment-12951883 ] RH Bugzilla Integration commented on GTNPORTAL-3389: ---------------------------------------------------- Peter Palaga changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from MODIFIED to POST > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:29:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 11 Mar 2014 07:29:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951884#comment-12951884 ] RH Bugzilla Integration commented on GTNPORTAL-3415: ---------------------------------------------------- Peter Palaga changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from MODIFIED to POST > 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.Final > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:31:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 11 Mar 2014 07:31:10 -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: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3370: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=794359 > 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.Final > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:39:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 07:39:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNPORTAL-3419: ------------------------------------------------- Summary: Update GateIn to WSRP 2.2.12.Final Key: GTNPORTAL-3419 URL: https://issues.jboss.org/browse/GTNPORTAL-3419 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Juraci Paix?o Kr?hling WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 07:41:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3419: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/801 > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > > WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 07:41:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3419: ---------------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > > WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:43:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 07:43:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling reopened GTNPORTAL-3419: ----------------------------------------------- Wrongly marked as "Resolved", but should be done by Peter (as he's merging it) > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > > WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 07:43:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 07:43:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3419: ---------------------------------------------- Assignee: Peter Palaga > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > Assignee: Peter Palaga > > WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 11:59:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Tue, 11 Mar 2014 11:59:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3420) Compose Page API In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNPORTAL-3420: ------------------------------------------------- Summary: Compose Page API Key: GTNPORTAL-3420 URL: https://issues.jboss.org/browse/GTNPORTAL-3420 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 https://community.jboss.org/wiki/RFC-APIForComposingPages -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 11 23:25:10 2014 From: issues at jboss.org (Tran Trung Thanh (JIRA)) Date: Tue, 11 Mar 2014 23:25:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3421) Parameter to externalize jcr values of workspace gets confusing. In-Reply-To: References: Message-ID: Tran Trung Thanh created GTNPORTAL-3421: ------------------------------------------- Summary: Parameter to externalize jcr values of workspace gets confusing. Key: GTNPORTAL-3421 URL: https://issues.jboss.org/browse/GTNPORTAL-3421 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.5.8.Final Reporter: Tran Trung Thanh Priority: Minor As far as I know, [gatein.jcr.storage.enabled|https://github.com/gatein/gatein-portal/blob/3.5.x/web/portal/src/main/webapp/WEB-INF/conf/jcr/repository-configuration.xml#L48] is used to externalize jcr values of workspace. If it is true, jcr values will be stored in filesystem. On the other hand, jcr value can be found in database. But its name makes customer confusing. They might think that if this parameter is false, it means no storage for jcr data. It should be *gatein.jcr.binaries.filesystem.enable* or *gatein.jcr.values.externalization.enable* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 12 05:51:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 12 Mar 2014 05:51:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3420) Compose Page API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952211#comment-12952211 ] Juraci Paix?o Kr?hling commented on GTNPORTAL-3420: --------------------------------------------------- Quickstart: https://github.com/jpkrohling/jboss-portal-quickstarts/compare/GTNPORTAL-3420-ComposePageAPI GateIn Portal: https://github.com/jpkrohling/gatein-portal/compare/BZ1043858-ComposeAPI GateIn API: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 12 05:53:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 12 Mar 2014 05:53:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3420) Compose Page API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3420: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 12 05:56:05 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 12 Mar 2014 05:56:05 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3420) Compose Page API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3420: ---------------------------------------------- Git Pull Request: https://github.com/gatein/gatein-api-java/pull/9 (was: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI) > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 12 07:31:11 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Wed, 12 Mar 2014 07:31:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga resolved GTNPORTAL-3419. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paix?o Kr?hling > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > > WSRP was released, so, an update on GateIn is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 13 03:34:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Thu, 13 Mar 2014 03:34:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3415: ---------------------------------- Original Estimate: 0 minutes (was: 3 hours) Remaining Estimate: 0 minutes (was: 3 hours) > 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.Final > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 13 03:34:11 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Thu, 13 Mar 2014 03:34:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran reassigned GTNPORTAL-3414: ------------------------------------- Assignee: Trong Tran (was: Tuyen Nguyen The) > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 13 03:34:11 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Thu, 13 Mar 2014 03:34:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on GTNPORTAL-3414 started by Trong Tran. > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 13 13:48:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 13 Mar 2014 13:48:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3416) UI error message instead of HTTP400 when trying to impersonate twice In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3416: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1076173 > UI error message instead of HTTP400 when trying to impersonate twice > -------------------------------------------------------------------- > > Key: GTNPORTAL-3416 > URL: https://issues.jboss.org/browse/GTNPORTAL-3416 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: 3.8.0.Beta01-SNAPSHOT > Reporter: Vlastislav Ramik > Assignee: Marek Posolda > Labels: RHJP62 > > Steps to reproduce: > 1. sign in as a root > 2. go to users and group management > 3. impersonate root user > 4. go to users and group management > 5. try to impersonate user > actual results: HTTP400 + ERROR message in log > expected results: UI error message (not sure what about ERROR message in log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Mar 13 13:52:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 13 Mar 2014 13:52:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3417: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1076175 > 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 > 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: Disabled User While disabled user icons is green and the tag is: Enabled User All functionality works as expected but both the icon and the title is very confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 14 05:54:10 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Fri, 14 Mar 2014 05:54:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3422) Avoid use of class attribute on script elements on head In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3422: -------------------------------------- Summary: Avoid use of class attribute on script elements on head Key: GTNPORTAL-3422 URL: https://issues.jboss.org/browse/GTNPORTAL-3422 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce According with xhtml 1.0 dtd, class attribute is not valid in script tags. GateIn uses "class" attributes to in the context of a jquery selector. This use makes fail W3C tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 14 09:00:12 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Fri, 14 Mar 2014 09:00:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: Takayuki Konishi created GTNPORTAL-3423: ------------------------------------------- Summary: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters Key: GTNPORTAL-3423 URL: https://issues.jboss.org/browse/GTNPORTAL-3423 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 7 (Japanese Edition) Internet Explorer 9 Reporter: Takayuki Konishi Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character 1. As a root user, log in to GateIn Potal. 2. Move to the dashboard. 3. Add a tab named "????" and activate the tab page. 4. Click "Edit Page" Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[2]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 14 09:02:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Fri, 14 Mar 2014 09:02:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3423: ---------------------------------------- Description: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character 1. As a root user, log in to GateIn Potal. 2. Move to the dashboard. 3. Add a tab named "????" and activate the tab page. 4. Click "Edit Page" Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} was: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character 1. As a root user, log in to GateIn Potal. 2. Move to the dashboard. 3. Add a tab named "????" and activate the tab page. 4. Click "Edit Page" Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[2]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > 1. As a root user, log in to GateIn Potal. > 2. Move to the dashboard. > 3. Add a tab named "????" and activate the tab page. > 4. Click "Edit Page" > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 14 09:06:11 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Fri, 14 Mar 2014 09:06:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3423: ---------------------------------------- Description: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character See Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} was: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character 1. As a root user, log in to GateIn Potal. 2. Move to the dashboard. 3. Add a tab named "????" and activate the tab page. 4. Click "Edit Page" Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 14 09:06:11 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Fri, 14 Mar 2014 09:06:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3423: ---------------------------------------- Description: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character See "Steps to Reproduce". Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} was: Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character See Actual result: Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. Expected results: Open editor for second tab ("????") Additional info: After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) [1] {code} 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] 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.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] ... 54 more {code} [2] {code} =============================================================== REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 authType=null characterEncoding=UTF-8 contentLength=-1 contentType=text/plain;charset=UTF-8 contextPath=/portal cookie=gtn.site.preference=/zXAkOBtwlk= cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined header=accept=*/* header=content-type=text/plain;charset=UTF-8 header=x-requested-with=XMLHttpRequest header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 header=accept-language=ja header=accept-encoding=gzip, deflate header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) header=host=192.168.122.1:8080 header=connection=Keep-Alive header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined locale=ja method=GET parameter=portal:componentId=1642164311 parameter=ajaxRequest=true parameter=_=1394801693542 parameter=portal:action=EditCurrentPage pathInfo=null protocol=HTTP/1.1 queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 remoteAddr=192.168.122.10 remoteHost=192.168.122.10 remoteUser=null requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined scheme=http serverName=192.168.122.1 serverPort=8080 servletPath=/u/root/<82>?<82>?<82>?<82>? isSecure=false --------------------------------------------------------------- {code} > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See "Steps to Reproduce". > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Mar 16 22:52:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Sun, 16 Mar 2014 22:52:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?focusedWorklogId=12430917&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430917 ] Trong Tran logged work on GTNPORTAL-3414: ----------------------------------------- Author: Trong Tran Created on: 16/Mar/14 10:50 PM Start Date: 16/Mar/14 10:49 PM Worklog Time Spent: 5 hours Issue Time Tracking ------------------- Remaining Estimate: 1 hour (was: 4 hours) Time Spent: 5 hours Worklog Id: (was: 12430917) > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Time Spent: 5 hours > Remaining Estimate: 1 hour > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 06:54:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 17 Mar 2014 06:54:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Fix Version/s: 3.8.0.Final > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Fix For: 3.8.0.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 07:20:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 17 Mar 2014 07:20:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran resolved GTNPORTAL-3404. ----------------------------------- Resolution: Done > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Fix For: 3.8.0.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 07:20:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Mon, 17 Mar 2014 07:20:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3404?focusedWorklogId=12430920&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430920 ] Trong Tran logged work on GTNPORTAL-3404: ----------------------------------------- Author: Trong Tran Created on: 17/Mar/14 7:18 AM Start Date: 17/Mar/14 7:18 AM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 4 hours) Time Spent: 4 hours Worklog Id: (was: 12430920) > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Assignee: Tuyen Nguyen The > Priority: Minor > Fix For: 3.8.0.Final > > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 11:40:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 17 Mar 2014 11:40:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3416) UI error message instead of HTTP400 when trying to impersonate twice In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953570#comment-12953570 ] RH Bugzilla Integration commented on GTNPORTAL-3416: ---------------------------------------------------- Boleslaw Dawidowicz changed the Status of [bug 1076173|https://bugzilla.redhat.com/show_bug.cgi?id=1076173] from NEW to ASSIGNED > UI error message instead of HTTP400 when trying to impersonate twice > -------------------------------------------------------------------- > > Key: GTNPORTAL-3416 > URL: https://issues.jboss.org/browse/GTNPORTAL-3416 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: 3.8.0.Beta01-SNAPSHOT > Reporter: Vlastislav Ramik > Assignee: Marek Posolda > Labels: RHJP62 > > Steps to reproduce: > 1. sign in as a root > 2. go to users and group management > 3. impersonate root user > 4. go to users and group management > 5. try to impersonate user > actual results: HTTP400 + ERROR message in log > expected results: UI error message (not sure what about ERROR message in log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:08:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:08:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character issues in Dashboard tab name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3400: ---------------------------------------- Affects Version/s: 3.6.0.Final > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:10:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:10:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3400) Multibyte character issues in Dashboard tab name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953697#comment-12953697 ] Takayuki Konishi commented on GTNPORTAL-3400: --------------------------------------------- I found that issue 1 (tab name rename issue) duplicates GTNPORTAL-3366. > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:18:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:18:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3423: ---------------------------------------- Affects Version/s: 3.6.0.Final > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See "Steps to Reproduce". > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:18:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:18:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi updated GTNPORTAL-3423: ---------------------------------------- Component/s: WebUI > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Affects Versions: 3.6.0.Final > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See "Steps to Reproduce". > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:20:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:20:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953698#comment-12953698 ] Takayuki Konishi commented on GTNPORTAL-3423: --------------------------------------------- This issue fixed in JPP 6.1.1. It seems related to GTNPORTAL-3247 . > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Affects Versions: 3.6.0.Final > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See "Steps to Reproduce". > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Mar 17 23:22:10 2014 From: issues at jboss.org (Takayuki Konishi (JIRA)) Date: Mon, 17 Mar 2014 23:22:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3423) Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takayuki Konishi resolved GTNPORTAL-3423. ----------------------------------------- Resolution: Duplicate Issue > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte characters > ---------------------------------------------------------------------------------- > > Key: GTNPORTAL-3423 > URL: https://issues.jboss.org/browse/GTNPORTAL-3423 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Affects Versions: 3.6.0.Final > Environment: Windows 7 (Japanese Edition) > Internet Explorer 9 > Reporter: Takayuki Konishi > > Cannot edit page with IE when Dashboard 2nd tab name contains multibyte character > See "Steps to Reproduce". > Actual result: > Move to first tab ("Click & Type Page Name") and IllegalArgumentException is thrown[1]. > Expected results: > Open editor for second tab ("????") > Additional info: > After I clicked "Edit Page", IE sent this request [2]. The tab name is not url encoded in UTF-8 > Actual) %82%C8%82%A9%82%DE%82%E7 (SJIS) > Expected) %E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 (UTF-8) > [1] > {code} > 21:37:57,516 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8080-2) An error occured while cache user profile: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > 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.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:61) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66) [exo.portal.component.portal-3.6.0.Final.jar:3.6.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:] > at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.Final.jar:1.3.3.Final] > at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Final.jar:3.6.0.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.IllegalArgumentException: Invalid percent escape in /u/root/%82%C8%82%A9%82%DE%82%E7 > at org.exoplatform.web.controller.router.Path$Data.(Path.java:108) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path$Data.(Path.java:44) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Path.parse(Path.java:34) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Route.route(Route.java:425) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.controller.router.Router.matcher(Router.java:164) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.web.WebAppController.service(WebAppController.java:300) [exo.portal.component.web.controller-3.6.0.Final.jar:3.6.0.Final] > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Final.jar:3.6.0.Final] > ... 54 more > {code} > [2] > {code} > =============================================================== > REQUEST URI =/portal/u/root/%82%C8%82%A9%82%DE%82%E7 > authType=null > characterEncoding=UTF-8 > contentLength=-1 > contentType=text/plain;charset=UTF-8 > contextPath=/portal > cookie=gtn.site.preference=/zXAkOBtwlk= > cookie=JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > header=accept=*/* > header=content-type=text/plain;charset=UTF-8 > header=x-requested-with=XMLHttpRequest > header=referer=http://192.168.122.1:8080/portal/u/root/%E3%81%AA%E3%81%8B%E3%82%80%E3%82%89 > header=accept-language=ja > header=accept-encoding=gzip, deflate > header=user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > header=host=192.168.122.1:8080 > header=connection=Keep-Alive > header=cookie=gtn.site.preference="/zXAkOBtwlk="; JSESSIONID=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > locale=ja > method=GET > parameter=portal:componentId=1642164311 > parameter=ajaxRequest=true > parameter=_=1394801693542 > parameter=portal:action=EditCurrentPage > pathInfo=null > protocol=HTTP/1.1 > queryString=portal:componentId=1642164311&portal:action=EditCurrentPage&ajaxRequest=true&_=1394801693542 > remoteAddr=192.168.122.10 > remoteHost=192.168.122.10 > remoteUser=null > requestedSessionId=UB3vwkW4kz8G5s7P0NQpXvyW.undefined > scheme=http > serverName=192.168.122.1 > serverPort=8080 > servletPath=/u/root/<82>?<82>?<82>?<82>? > isSecure=false > --------------------------------------------------------------- > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 00:14:10 2014 From: issues at jboss.org (Tuyen Nguyen The (JIRA)) Date: Tue, 18 Mar 2014 00:14:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3414?focusedWorklogId=12430921&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430921 ] Tuyen Nguyen The logged work on GTNPORTAL-3414: ----------------------------------------------- Author: Tuyen Nguyen The Created on: 18/Mar/14 12:13 AM Start Date: 17/Mar/14 12:12 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 7 hours (was: 5 hours) Worklog Id: (was: 12430921) > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Time Spent: 7 hours > Remaining Estimate: 0 minutes > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 06:44:10 2014 From: issues at jboss.org (Marek Posolda (JIRA)) Date: Tue, 18 Mar 2014 06:44:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3416) UI error message instead of HTTP400 when trying to impersonate twice In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Posolda updated GTNPORTAL-3416: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/802 > UI error message instead of HTTP400 when trying to impersonate twice > -------------------------------------------------------------------- > > Key: GTNPORTAL-3416 > URL: https://issues.jboss.org/browse/GTNPORTAL-3416 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: 3.8.0.Beta01-SNAPSHOT > Reporter: Vlastislav Ramik > Assignee: Marek Posolda > Labels: RHJP62 > > Steps to reproduce: > 1. sign in as a root > 2. go to users and group management > 3. impersonate root user > 4. go to users and group management > 5. try to impersonate user > actual results: HTTP400 + ERROR message in log > expected results: UI error message (not sure what about ERROR message in log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:14:10 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:14:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3401) Encoding of "&" characters in URLs. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3401: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:14:11 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:14:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3406: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:12 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3407: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > 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 > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:12 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3409: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:13 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:13 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3411: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > 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 > > GateIn produces XHTML 1.0 Strict type documents. > There are some minor markups not compliant with XHTML specification (i.e. empty list
          , or bad use of tag inside a block element). > These issues don't affect to Portal behaviour but creates a non compliant markup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:13 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:13 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3418) Improve Redirect Admin UI to be W3C compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3418: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > Improve Redirect Admin UI to be W3C compliant > --------------------------------------------- > > Key: GTNPORTAL-3418 > URL: https://issues.jboss.org/browse/GTNPORTAL-3418 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:13 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:13 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3412) HTML5 data-* attributes not compatible with XHTML 1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3412: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > HTML5 data-* attributes not compatible with XHTML 1.0 > ----------------------------------------------------- > > Key: GTNPORTAL-3412 > URL: https://issues.jboss.org/browse/GTNPORTAL-3412 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > GateIn produces XHTML 1.0 Strict type documents. > mobile-integration/portlets/header portlet uses html5 data-* attributes not compliant with XHTML 1.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:16:13 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Tue, 18 Mar 2014 09:16:13 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3422) Avoid use of class attribute on script elements on head In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3422: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/803 > Avoid use of class attribute on script elements on head > ------------------------------------------------------- > > Key: GTNPORTAL-3422 > URL: https://issues.jboss.org/browse/GTNPORTAL-3422 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > According with xhtml 1.0 dtd, class attribute is not valid in script tags. > GateIn uses "class" attributes to in the context of a jquery selector. > This use makes fail W3C tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:28:11 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 18 Mar 2014 09:28:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3401) Encoding of "&" characters in URLs. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953811#comment-12953811 ] RH Bugzilla Integration commented on GTNPORTAL-3401: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065987|https://bugzilla.redhat.com/show_bug.cgi?id=1065987] from ASSIGNED to POST > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:30:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 18 Mar 2014 09:30:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3406) Avoid the use of custom attributes for portal navigation portlets. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953812#comment-12953812 ] RH Bugzilla Integration commented on GTNPORTAL-3406: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065991|https://bugzilla.redhat.com/show_bug.cgi?id=1065991] from ASSIGNED to POST > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:32:10 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 18 Mar 2014 09:32:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3407) Avoid ID elements starting with number In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953814#comment-12953814 ] RH Bugzilla Integration commented on GTNPORTAL-3407: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1065997|https://bugzilla.redhat.com/show_bug.cgi?id=1065997] from ASSIGNED to POST > 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 > > GateIn produces XHTML 1.0 Strict type documents. > For a w3c validation, elements ID should not start with number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:32:11 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 18 Mar 2014 09:32:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953815#comment-12953815 ] RH Bugzilla Integration commented on GTNPORTAL-3409: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1066001|https://bugzilla.redhat.com/show_bug.cgi?id=1066001] from ASSIGNED to POST > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 09:34:11 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 18 Mar 2014 09:34:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3411) Minor markup XHTML issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953816#comment-12953816 ] RH Bugzilla Integration commented on GTNPORTAL-3411: ---------------------------------------------------- Lucas Ponce changed the Status of [bug 1066010|https://bugzilla.redhat.com/show_bug.cgi?id=1066010] from ASSIGNED to POST > 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 > > GateIn produces XHTML 1.0 Strict type documents. > There are some minor markups not compliant with XHTML specification (i.e. empty list
            , or bad use of tag inside a block element). > These issues don't affect to Portal behaviour but creates a non compliant markup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 22:02:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 18 Mar 2014 22:02:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR dependencies to 1.16.0-CR1 In-Reply-To: References: Message-ID: Trong Tran created GTNPORTAL-3424: ------------------------------------- Summary: Upgrade JCR dependencies to 1.16.0-CR1 Key: GTNPORTAL-3424 URL: https://issues.jboss.org/browse/GTNPORTAL-3424 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Trong Tran Fix For: 3.7.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 22:02:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 18 Mar 2014 22:02:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR dependencies to 1.16.0-CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3424: ---------------------------------- Sprint: Sprint 96 > Upgrade JCR dependencies to 1.16.0-CR1 > -------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 22:04:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 18 Mar 2014 22:04:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR dependencies to 1.16.0-CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran reassigned GTNPORTAL-3424: ------------------------------------- Assignee: Trong Tran > Upgrade JCR dependencies to 1.16.0-CR1 > -------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 22:04:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 18 Mar 2014 22:04:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR dependencies to 1.16.0-CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on GTNPORTAL-3424 started by Trong Tran. > Upgrade JCR dependencies to 1.16.0-CR1 > -------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Mar 18 23:32:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Tue, 18 Mar 2014 23:32:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR 1.16.0-CR1 and component dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran updated GTNPORTAL-3424: ---------------------------------- Summary: Upgrade JCR 1.16.0-CR1 and component dependencies (was: Upgrade JCR dependencies to 1.16.0-CR1) > Upgrade JCR 1.16.0-CR1 and component dependencies > ------------------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 00:18:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Wed, 19 Mar 2014 00:18:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR 1.16.0-CR1 and component dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trong Tran resolved GTNPORTAL-3424. ----------------------------------- Resolution: Done > Upgrade JCR 1.16.0-CR1 and component dependencies > ------------------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 00:18:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Wed, 19 Mar 2014 00:18:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3424) Upgrade JCR 1.16.0-CR1 and component dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3424?focusedWorklogId=12430930&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12430930 ] Trong Tran logged work on GTNPORTAL-3424: ----------------------------------------- Author: Trong Tran Created on: 19/Mar/14 12:18 AM Start Date: 19/Mar/14 12:17 AM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 day) Time Spent: 3 hours Worklog Id: (was: 12430930) > Upgrade JCR 1.16.0-CR1 and component dependencies > ------------------------------------------------- > > Key: GTNPORTAL-3424 > URL: https://issues.jboss.org/browse/GTNPORTAL-3424 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Fix For: 3.7.0.Final > > Original Estimate: 1 day > Time Spent: 3 hours > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 07:30:10 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Wed, 19 Mar 2014 07:30:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3425) Error UI in Page Editor with PBR+Richfaces app In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3425: -------------------------------------- Summary: Error UI in Page Editor with PBR+Richfaces app Key: GTNPORTAL-3425 URL: https://issues.jboss.org/browse/GTNPORTAL-3425 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.6.3.Final Environment: - GateIn master. Head on commit: 69ecd42235bfbcc8c3853be80c20dd6eab7a3a10 Upgrade component versions Reporter: Lucas Ponce Assignee: Lucas Ponce Adding richfaces-simple-3.3.x.war into a page with other portlets creates a JavaScript error that makes request hanged. This error happens on Chrome browsers. Full description: https://issues.jboss.org/browse/PBR-563 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 07:40:10 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Wed, 19 Mar 2014 07:40:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3425) Error UI in Page Editor with PBR+Richfaces app In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Ponce updated GTNPORTAL-3425: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/804 > Error UI in Page Editor with PBR+Richfaces app > ---------------------------------------------- > > Key: GTNPORTAL-3425 > URL: https://issues.jboss.org/browse/GTNPORTAL-3425 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.3.Final > Environment: - GateIn master. Head on commit: > 69ecd42235bfbcc8c3853be80c20dd6eab7a3a10 Upgrade component versions > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > Adding richfaces-simple-3.3.x.war into a page with other portlets creates a JavaScript error that makes request hanged. > This error happens on Chrome browsers. > Full description: > https://issues.jboss.org/browse/PBR-563 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 11:50:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 11:50:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: Juraci Paix?o Kr?hling created GTNPORTAL-3426: ------------------------------------------------- Summary: CDI portlet throws an exception during deployment Key: GTNPORTAL-3426 URL: https://issues.jboss.org/browse/GTNPORTAL-3426 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 >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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 11:50:12 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Mar 2014 11:50:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated GTNPORTAL-3426: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1075588 > CDI portlet throws an exception during deployment > -------------------------------------------------- > > Key: GTNPORTAL-3426 > URL: https://issues.jboss.org/browse/GTNPORTAL-3426 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 11:50:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 11:50:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954282#comment-12954282 ] Juraci Paix?o Kr?hling commented on GTNPORTAL-3426: --------------------------------------------------- According to git bisect, this is the culprit: {code}0ff17d4a3a577320bf27199ee0ba2b55ee5fbacd is the first bad commit{code} > CDI portlet throws an exception during deployment > -------------------------------------------------- > > Key: GTNPORTAL-3426 > URL: https://issues.jboss.org/browse/GTNPORTAL-3426 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 13:36:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 13:36:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3426: ---------------------------------------------- Issue Type: Bug (was: Feature Request) > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 13:36:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 13:36:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling reassigned GTNPORTAL-3368: ------------------------------------------------- Assignee: Juraci Paix?o Kr?hling (was: Peter Palaga) > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 13:36:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 13:36:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954317#comment-12954317 ] Juraci Paix?o Kr?hling commented on GTNPORTAL-3368: --------------------------------------------------- I believe GTNPORTAL-3426 is a duplicate of this one, caused by the commit 0ff17d4a3a577320bf27199ee0ba2b55ee5fbacd. > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 14:00:11 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 19 Mar 2014 14:00:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954329#comment-12954329 ] RH Bugzilla Integration commented on GTNPORTAL-3426: ---------------------------------------------------- Juraci Paixao Krohling changed the Status of [bug 1075588|https://bugzilla.redhat.com/show_bug.cgi?id=1075588] from ASSIGNED to POST > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 14:00:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 14:00:12 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3426) CDI portlet throws an exception during deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3426: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/805 > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 14:04:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 14:04:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954330#comment-12954330 ] Juraci Paix?o Kr?hling commented on GTNPORTAL-3368: --------------------------------------------------- [~trong.tran], would you please test the linked PR, to see if it fixes this issue? Thanks! > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 14:04:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraci_Paix=C3=A3o_Kr=C3=B6hling_=28JIRA=29?=) Date: Wed, 19 Mar 2014 14:04:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraci Paix?o Kr?hling updated GTNPORTAL-3368: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/805 > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 22:48:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Wed, 19 Mar 2014 22:48:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954460#comment-12954460 ] Trong Tran commented on GTNPORTAL-3368: --------------------------------------- I confirm the PR fixes this issue. Thanks > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Mar 19 23:50:10 2014 From: issues at jboss.org (Trong Tran (JIRA)) Date: Wed, 19 Mar 2014 23:50:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNPORTAL-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954463#comment-12954463 ] Trong Tran commented on GTNPORTAL-3368: --------------------------------------- I merged the PR to 3.7.0.Final (3.7.x branch). > CDI Portlet Deployment is not working anymore in latest master > -------------------------------------------------------------- > > Key: GTNPORTAL-3368 > URL: https://issues.jboss.org/browse/GTNPORTAL-3368 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Juraci Paix?o Kr?hling > Fix For: 3.7.0.Final > > > Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup: > {code} > 13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war > 13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71) > 13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war > 13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers [] > at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > 13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}} > 13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war > 13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms > 13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service > 13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}} > {code} > I confirm that it is still working well in latest gatein 3.7.0.Alpha01. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 21 06:14:10 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Fri, 21 Mar 2014 06:14:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNWSRP-372) Exception appears in log while using WSRP portlets with PortletBridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GTNWSRP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954883#comment-12954883 ] Petr Mensik commented on GTNWSRP-372: ------------------------------------- I was manually able to verify that WSRP now works fine together with PBR without any exceptions in the log. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 21 06:20:10 2014 From: issues at jboss.org (Peter Palaga (JIRA)) Date: Fri, 21 Mar 2014 06:20:10 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3427) Internationalize alt attribute of captcha In-Reply-To: References: Message-ID: Peter Palaga created GTNPORTAL-3427: --------------------------------------- Summary: Internationalize alt attribute of captcha Key: GTNPORTAL-3427 URL: https://issues.jboss.org/browse/GTNPORTAL-3427 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Peter Palaga Assignee: Peter Palaga Fix For: 3.8.0.Final In org.exoplatform.portal.webui.register.UICaptcha -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Mar 21 08:56:11 2014 From: issues at jboss.org (Lucas Ponce (JIRA)) Date: Fri, 21 Mar 2014 08:56:11 -0400 (EDT) Subject: [gatein-issues] [JBoss JIRA] (GTNPORTAL-3428) Unify CDATA uses In-Reply-To: References: Message-ID: Lucas Ponce created GTNPORTAL-3428: -------------------------------------- Summary: 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 Review and unify the use of CDATA for