March 2010 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-821) remove bookmark.jsp

by Patrice Lamarque (JIRA)

remove bookmark.jsp ------------------- Key: GTNPORTAL-821 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-821 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.0.0-CR01 Reporter: Patrice Lamarque Priority: Optional Fix For: 3.0.0-GA I doubt bookmark.jsp is used in gatein : Looking inside I find references to eXo's legacy portlet container : <%@ page import="org.exoplatform.services.portletcontainer.PortletContainerService"%> <%@ page import="org.exoplatform.services.portletcontainer.pci.PortletData"%> So I think it should be safe to just remove that file : http://anonsvn.jboss.org/repos/gatein/portal/trunk/web/portal/src/main/we... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-822) Improper redirect after login

by Chris Laprun (JIRA)

Improper redirect after login ----------------------------- Key: GTNPORTAL-822 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-822 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, User Interface Affects Versions: 3.0.0-CR01 Reporter: Chris Laprun Assignee: Julien Viet Fix For: 3.0.0-GA Trying to access http://localhost:8080/portal/private/classic/administration/registry directly without being logged in. The login dialog correctly appears. However, once logged in, portal redirects to http://localhost:8080/portal/private/classic instead of the requested page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-823) WSRP portlets should also have a category named after the configured consumer name

by Chris Laprun (JIRA)

WSRP portlets should also have a category named after the configured consumer name ---------------------------------------------------------------------------------- Key: GTNPORTAL-823 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-823 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface, WSRP integration Affects Versions: 3.0.0-CR01 Reporter: Chris Laprun Assignee: Chris Laprun Priority: Optional Fix For: 3.0.0-GA ... so that it's easy to see which remote portlets come from which remote producer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPC-18) Portlet content not shown when using RenderResponse.getPortletOutputStream()

by Henri Sara (JIRA)

Portlet content not shown when using RenderResponse.getPortletOutputStream() ---------------------------------------------------------------------------- Key: GTNPC-18 URL: https://jira.jboss.org/jira/browse/GTNPC-18 Project: GateIn Portlet Container Issue Type: Bug Components: Simple Portal Affects Versions: 2.1.0-CR02 Reporter: Henri Sara When using RenderRequest.getPortletOutputStream() instead of RenderResponse.getWriter() to write the portlet contents, only a memory reference (like "[B@1234abcd") is shown as the portlet content. This is caused by the use of byte[].toString() in org.gatein.pc.portal.jsp.taglib.PortletMarkupTag.doTag(), line "frag = fragment.getBytes().toString();". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (GTNMOP-6) Portlet preferences layering

by Julien Viet (JIRA)

[ https://jira.jboss.org/jira/browse/GTNMOP-6?page=com.atlassian.jira.plugi... ] Julien Viet resolved GTNMOP-6. ------------------------------ Resolution: Done > Portlet preferences layering > ---------------------------- > > Key: GTNMOP-6 > URL: https://jira.jboss.org/jira/browse/GTNMOP-6 > Project: GateIn Model Object for Portal > Issue Type: Task > Reporter: Julien Viet > Assignee: Julien Viet > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-338) tune getAllPortalNames method in UserPortalConfigService

by Prabhat Jha (JIRA)

tune getAllPortalNames method in UserPortalConfigService -------------------------------------------------------- Key: GTNPORTAL-338 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-338 Project: GateIn Portal Issue Type: Bug Affects Versions: 3.0.0-Beta03 Reporter: Prabhat Jha Fix For: 3.0.0-Beta04 Related jira is https://jira.jboss.org/jira/browse/JBQA-2887 which may not be accessible to all of you so here are details: I did some profiling with JProfiler. There is no difference between the case with different users and same users test. The biggest bottleneck is the "getAllPortalNames" bottleneck. During processing of HTTP request to the sample page, then about 90% of time is spent in method "getAllPortalNames" from class "org.exoplatfrom.portal.config.UserPortalConfigService". Each call to this method performs several calls to eXo JCR DB. There is no caching here. Please let me know if a separate jira is needed for following profiling: I tried to do the test and profiling with Chromattic options disabled and enabled. Chromattic options are four JVM options which can be added to server JVM args to optimize Chromattic library to use caching and avoid calls to eXo JCR DB. Namely these options are here: -Dorg.chromattic.api.Option.optimize.jcr.enabled=true -Dorg.chromattic.api.Option.optimize.jcr.has_property.enabled=true -Dorg.chromattic.api.Option.optimize.jcr.has_node.enabled=true -Dorg.chromattic.api.Option.cache.state.enabled=true I verified that there is no any performance improvement with these options enabled and calls to eXo JCR SB are still here. I did some profling and debugging and here are the more detailed results: 1) Significant amount of time is spent in the method getProperty in class org.chromattic.core.jcr.SessionWrapperImpl. public Property getProperty(Node node, String relPath) throws RepositoryException { if (hasPropertyOptimized) { return node.getProperty(relPath); } else { if (node.hasProperty(relPath)) { return node.getProperty(relPath); } 1.a) if chromattic options are disabled (hasPropertyOptimized==false to be more precise), then method node.hasProperty(relPath) performs call to eXo DB but method node.getProperty(relPath) doesn't perform any additional calls to DB, because data are cached inside of cache in org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager. 1.b) if chromattic options are enabled, then only method node.getProperty(relPath) is called but this method performs calls to DB because these data are not cached inside CacheableWorkspaceDataManager. So the conclusion is, that there is no any benefit when hasPropertyOptimized is true. 2) If cacheState is enabled (option -Dorg.chromattic.api.Option.cache.state.enabled=true) then there is non-null variable "propertyCache" inside "org.chromattic.core.PersistentEntityContextState". When method "getPropertyValue" on class "PersistentEntityContextState" is called, then nothing is found inside the cache and founded items are not saved to propertyCache. New items are put to propertyCache only when "setPropertyValue" is called, but this method is not called during HTTP request processing. So the propertyCache is always empty. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-752) Build a maven project with mandatory stuffs for a skin

by Trong Tran (JIRA)

Build a maven project with mandatory stuffs for a skin ------------------------------------------------------ Key: GTNPORTAL-752 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-752 Project: GateIn Portal Issue Type: Sub-task Reporter: Trong Tran -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-814) ClientAbortExceptions should not be logged.

by Matt Wringe (JIRA)

ClientAbortExceptions should not be logged. ------------------------------------------- Key: GTNPORTAL-814 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-814 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe When using GateIn, its possible for the UIPortalApplication to throw an org.apache.catalina.connector.ClientAbortException when handling portlet markup headers. This exception should be ignored since it signifies that the clients browser has closed the connection prematurely. This exception happens sporadically, and can usually be triggered by reloading the same page rapidly in a browser. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-712) Remote portlet keep getting cloned on each edit request

by Chris Laprun (JIRA)

Remote portlet keep getting cloned on each edit request ------------------------------------------------------- Key: GTNPORTAL-712 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-712 Project: GateIn Portal Issue Type: Bug Components: WSRP integration Affects Versions: 3.0.0-CR01 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 3.0.0-GA The issue boils down to the fact that the cloned state is not properly persisted and the portlet therefore keeps requesting a CLONE_BEFORE_WRITE AccessMode instead of READ_WRITE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-737) WSRP producer doesn't properly persist clone states

by Chris Laprun (JIRA)

WSRP producer doesn't properly persist clone states --------------------------------------------------- Key: GTNPORTAL-737 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-737 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WSRP integration Affects Versions: 3.0.0-CR01 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 3.0.0-GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2010