April 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3448?page=com.atlassian.jira.pl... ] Tuyen Nguyen The updated GTNPORTAL-3448: ---------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/829 > Failed authentication on service REST after a session timeout > ------------------------------------------------------------- > > Key: GTNPORTAL-3448 > URL: https://issues.jboss.org/browse/GTNPORTAL-3448 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > > Customer does not sometimes use /rest after session timeout. He also propose a workaround which adds "restoreIdentity" of the filter "SetCurrentIdentityFilter" into web.xml of rest.war, this parameter is added to almost war files but this param is not available in rest.war. > So, we should add this param into web.xml of rest.war -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout

by Tuyen Nguyen The (JIRA)

Tuyen Nguyen The created GTNPORTAL-3448: ------------------------------------------- Summary: Failed authentication on service REST after a session timeout Key: GTNPORTAL-3448 URL: https://issues.jboss.org/browse/GTNPORTAL-3448 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tuyen Nguyen The Assignee: Tuyen Nguyen The Customer does not sometimes use /rest after session timeout. He also propose a workaround which adds "restoreIdentity" of the filter "SetCurrentIdentityFilter" into web.xml of rest.war, this parameter is added to almost war files but this param is not available in rest.war. So, we should add this param into web.xml of rest.war -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3435) Import .zip REST API broken with EAP 6.3.0.Alpha1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3435?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3435: ---------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1083054|https://bugzilla.redhat.com/show_bug.cgi?id=1083054] from MODIFIED to ON_QA > Import .zip REST API broken with EAP 6.3.0.Alpha1 > ------------------------------------------------- > > Key: GTNPORTAL-3435 > URL: https://issues.jboss.org/browse/GTNPORTAL-3435 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Attachments: jbossweb-7.4.1.Final.jar, portal_classic_2014-03-28_16-59-29.zip > > > A curl operation over template/user API: > curl -i -H "Content-Type: application/zip" -u root:gtn -X PUT -T examples/user.zip "http://localhost:8080/rest/private/managed-components/template/user" > hangs with: > 16:35:16,466 INFO [org.exoplatform.portal.mop.management.operations.TemplateImportResource] (http-/127.0.0.1:8080-4) Import successful ! > 16:35:16,475 ERROR [org.apache.catalina.connector] (http-/127.0.0.1:8080-4) JBWEB001018: An exception or error occurred in the container during the request processing: java.nio.BufferOverflowException > at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:357) [rt.jar:1.7.0_25] > at org.apache.coyote.http11.InternalNioOutputBuffer.commit(InternalNioOutputBuffer.java:666) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.http11.Http11NioProcessor.commit(Http11NioProcessor.java:480) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.http11.Http11NioProcessor.action(Http11NioProcessor.java:798) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.Response.action(Response.java:190) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.Response.sendHeaders(Response.java:390) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:352) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:318) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.catalina.connector.Response.finishResponse(Response.java:487) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:371) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] -- This message 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.pl... ] Vu Viet Phuong updated GTNPORTAL-3410: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.5.9.Final 3.7.1.Final 3.8.0.Final Resolution: Done > 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 > Fix For: 3.5.9.Final, 3.7.1.Final, 3.8.0.Final > > > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3403) Custom validator of page node name

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3403?page=com.atlassian.jira.pl... ] Vu Viet Phuong updated GTNPORTAL-3403: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.5.9.Final 3.7.1.Final 3.8.0.Final Resolution: Done > Custom validator of page node name > ---------------------------------- > > Key: GTNPORTAL-3403 > URL: https://issues.jboss.org/browse/GTNPORTAL-3403 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Tran Trung Thanh > Fix For: 3.5.9.Final, 3.7.1.Final, 3.8.0.Final > > > Please provide a way to customize page name pattern. In current code, it is hardcoded. for example: https://github.com/gatein/gatein-portal/blob/3.5.x/portlet/exoadmin/src/m... -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3403) Custom validator of page node name

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3403?page=com.atlassian.jira.pl... ] Tuyen Nguyen The commented on GTNPORTAL-3403: --------------------------------------------- We should apply PR https://github.com/gatein/gatein-portal/pull/793 It only change pagename validator and do not change validation of Portal Name, User group name and Application's category name > Custom validator of page node name > ---------------------------------- > > Key: GTNPORTAL-3403 > URL: https://issues.jboss.org/browse/GTNPORTAL-3403 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Tran Trung Thanh > > Please provide a way to customize page name pattern. In current code, it is hardcoded. for example: https://github.com/gatein/gatein-portal/blob/3.5.x/portlet/exoadmin/src/m... -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3227) Implement disabled User feature

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3227?page=com.atlassian.jira.pl... ] Peter Palaga commented on GTNPORTAL-3227: ----------------------------------------- A related PR was merged to master https://github.com/gatein/gatein-portal/pull/826 > Implement disabled User feature > ------------------------------- > > Key: GTNPORTAL-3227 > URL: https://issues.jboss.org/browse/GTNPORTAL-3227 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Vu Viet Phuong > Assignee: Tuyen Nguyen The > Priority: Minor > Labels: backlogs, plan_3.7.0 > Fix For: 3.7.0.Final > > Original Estimate: 4 hours > Time Spent: 2 days, 4 hours > Remaining Estimate: 0 minutes > > Refer to the spec at http://community.jboss.org/wiki/DisabledUser -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3444) "Invalid Application Id" thrown for all apps in Application Registry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3444?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3444: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1085792|https://bugzilla.redhat.com/show_bug.cgi?id=1085792] from NEW to MODIFIED > "Invalid Application Id" thrown for all apps in Application Registry > -------------------------------------------------------------------- > > Key: GTNPORTAL-3444 > URL: https://issues.jboss.org/browse/GTNPORTAL-3444 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: master, head on commit: > 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > The following exception is logged when when clicking on any Application in Application Registry: > Error during the processAction phase: java.lang.Exception: Invalid Application Id: [dashboard_slash_DashboardPortlet] -- This message 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3444) "Invalid Application Id" thrown for all apps in Application Registry

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3444?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3444: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.0.Final Resolution: Done > "Invalid Application Id" thrown for all apps in Application Registry > -------------------------------------------------------------------- > > Key: GTNPORTAL-3444 > URL: https://issues.jboss.org/browse/GTNPORTAL-3444 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: master, head on commit: > 257dab7e927711acb365885d9e34f66d6ac93073 [maven-release-plugin] prepare for next development iteration > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > The following exception is logged when when clicking on any Application in Application Registry: > Error during the processAction phase: java.lang.Exception: Invalid Application Id: [dashboard_slash_DashboardPortlet] -- This message 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3447) Move 7.4.0.Final-redhat-4/* to jboss

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3447?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3447. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done > Move 7.4.0.Final-redhat-4/* to jboss > ------------------------------------ > > Key: GTNPORTAL-3447 > URL: https://issues.jboss.org/browse/GTNPORTAL-3447 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > > {{packaging/jboss/pkg/src/main/resources/7.4.0.Final-redhat-4/*}} should be moved to {{packaging/jboss/pkg/src/main/resources/jboss}}. Getting rid of {{7.4.0.Final-redhat-4}} directory will make the maintenance of the prod branch much easier and less error prone. -- 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

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2014