[JBoss JIRA] Created: (JBPORTAL-1133) after created a new window & placed he page, the 'Preview link' in management portlet cause exception
by Boleslaw Dawidowicz (JIRA)
after created a new window & placed he page, the 'Preview link' in management portlet cause exception
-----------------------------------------------------------------------------------------------------
Key: JBPORTAL-1133
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1133
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Theme
Affects Versions: 2.6.DR1
Reporter: Boleslaw Dawidowicz
Assigned To: Julien Viet
Priority: Critical
Fix For: 2.6.Alpha1
Also, after we have created a new window & placed it on the page, when following the 'Preview link' we receive the following error:
javax.servlet.ServletException
org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:405)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.NullPointerException
org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl.stateChanged(MaximizingStrategyImpl.java:103)
org.jboss.portal.core.aspects.controller.PageNavigationInterceptor.updatePageNavigationalState(PageNavigationInterceptor.java:138)
org.jboss.portal.core.controller.command.InvokeWindowRenderCommand.execute(InvokeWindowRenderCommand.java:115)
org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:134)
org.jboss.portal.core.aspects.controller.WindowCacheInterceptor.invoke(WindowCacheInterceptor.java:129)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:183)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 6 months
[JBoss JIRA] Created: (JBCACHE-880) Add expiration policy for nodes based on a node's expiration key
by Elias Ross (JIRA)
Add expiration policy for nodes based on a node's expiration key
----------------------------------------------------------------
Key: JBCACHE-880
URL: http://jira.jboss.com/jira/browse/JBCACHE-880
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
It is useful to specify an expiration time (TTL) for cache values individually. For example, in caching web page contents, the data should be retained based on the HTTP header "Expires". Or, for caching session data, it should be kept based on the user's preference, e.g. Yahoo! Mail allows the authentication credentials to be cached from 1-24 hours.
Example usage:
TreeCache cache;
Fqn fqn1 = new Fqn("node1");
Fqn fqn2 = new Fqn("node2");
cache.put(fqn1, "expiration", new Long( ... ));
cache.put(fqn1, "data", ... );
cache.put(fqn2, "expiration", new Long( ... ));
cache.put(fqn2, "data", ... );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 6 months