[JBoss JIRA] (GTNPORTAL-3322) Improvements of handling of <priority> in navigation.xml
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3322?focusedWorklogId=12430416&... ]
Trong Tran logged work on GTNPORTAL-3322:
-----------------------------------------
Author: Trong Tran
Created on: 18/Dec/13 4:00 AM
Start Date: 18/Dec/13 4:00 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 3 hours (was: 4 hours)
Time Spent: 1 hour
Worklog Id: (was: 12430416)
> Improvements of handling of <priority> in navigation.xml
> --------------------------------------------------------
>
> Key: GTNPORTAL-3322
> URL: https://issues.jboss.org/browse/GTNPORTAL-3322
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 3 hours
>
> This is followup of GTNPORTAL-2751, GTNPORTAL-3324 and GTNPORTAL-3350.
> (1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
> (2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
> (3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3322) Improvements of handling of <priority> in navigation.xml
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3322?page=com.atlassian.jira.pl... ]
Trong Tran logged work on GTNPORTAL-3322:
-----------------------------------------
Author: Trong Tran
Edited by: Trong Tran
Created on: 18/Dec/13 4:00 AM
Edited on: 18/Dec/13 4:00 AM
Start Date: 18/Dec/13 4:00 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 3 hours)
Worklog Id: (was: 12430416)
> Improvements of handling of <priority> in navigation.xml
> --------------------------------------------------------
>
> Key: GTNPORTAL-3322
> URL: https://issues.jboss.org/browse/GTNPORTAL-3322
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
> Original Estimate: 4 hours
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> This is followup of GTNPORTAL-2751, GTNPORTAL-3324 and GTNPORTAL-3350.
> (1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
> (2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
> (3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3337) User disables himself
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3337?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3337:
----------------------------------
Remaining Estimate: 1 hour (was: 0 minutes)
> User disables himself
> ---------------------
>
> Key: GTNPORTAL-3337
> URL: https://issues.jboss.org/browse/GTNPORTAL-3337
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Trong Tran
> Assignee: Tuyen Nguyen The
> Fix For: 3.7.0.Final
>
> Original Estimate: 2 hours
> Time Spent: 4 hours
> Remaining Estimate: 1 hour
>
> - Login by John
> - Go to User and Group management
> - Disable John himself
> => He still can do other action ( edit/delete user / Add page/Add/edit portal) but can't edit for him -> NOK
> Expectation:
> - Session should be invalidated immediately, like the delete action
> or
> - Show confirmation message, then disable
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3336) Exception when detele portal which selected for Site Redirects
by Alexandre Mendonça (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3336?page=com.atlassian.jira.pl... ]
Alexandre Mendonça updated GTNPORTAL-3336:
------------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/742
> Exception when detele portal which selected for Site Redirects
> --------------------------------------------------------------
>
> Key: GTNPORTAL-3336
> URL: https://issues.jboss.org/browse/GTNPORTAL-3336
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Trong Tran
> Assignee: Alexandre Mendonça
> Fix For: 3.7.0.Final
>
>
> - Login portal
> - Go to Manage Sites
> - Delete Mobile Portal
> - Go to Site Direction and import export
> - Select classic and click configure
> - Click Save
> => Show exception in console.
> {noformat}
> Dec 3, 2013 3:00:12 PM org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback logException
> SEVERE: /admin/redirects/index.xhtml: /admin/redirects/index.xhtml @54,97 value="#{rdrEdit.checkSiteExists(r.redirectSite)}": org.gatein.api.ApiException: Failed to load navigation
> javax.el.ELException: /admin/redirects/index.xhtml: /admin/redirects/index.xhtml @54,97 value="#{rdrEdit.checkSiteExists(r.redirectSite)}": org.gatein.api.ApiException: Failed to load navigation
> at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94)
> at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82)
> at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:183)
> at com.sun.faces.facelets.component.RepeatRenderer.encodeChildren(RepeatRenderer.java:104)
> at com.sun.faces.facelets.component.UIRepeat.process(UIRepeat.java:527)
> at com.sun.faces.facelets.component.UIRepeat.encodeChildren(UIRepeat.java:988)
> at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304)
> at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779)
> at javax.faces.render.Renderer.encodeChildren(Renderer.java:168)
> at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779)
> at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:538)
> at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612)
> at javax.faces.component.UIForm.visitTree(UIForm.java:371)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623)
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:291)
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:194)
> at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981)
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779)
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:409)
> at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
> at org.jboss.portletbridge.application.PortletViewHandler.renderView(PortletViewHandler.java:212)
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> at org.jboss.portletbridge.bridge.controller.Jsf20ControllerImpl.renderFaces(Jsf20ControllerImpl.java:410)
> at org.jboss.portletbridge.bridge.controller.Jsf20ControllerImpl.renderFacesResource(Jsf20ControllerImpl.java:586)
> at org.jboss.portletbridge.bridge.controller.Jsf20ControllerImpl.renderResource(Jsf20ControllerImpl.java:289)
> at org.jboss.portletbridge.PortletBridgeImpl.doFacesRequest(PortletBridgeImpl.java:278)
> at javax.portlet.faces.GenericFacesPortlet.serveResource(GenericFacesPortlet.java:467)
> at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:598)
> at org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:184)
> at org.exoplatform.portal.application.ApplicationMonitoringFilter.doFilter(ApplicationMonitoringFilter.java:77)
> at org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:184)
> at org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:84)
> at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:529)
> at org.gatein.pc.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatcher.java:42)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.EventPayloadInterceptor.invoke(EventPayloadInterceptor.java:197)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.RequestAttributeConversationInterceptor.invoke(RequestAttributeConversationInterceptor.java:119)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.CCPPInterceptor.invoke(CCPPInterceptor.java:65)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:49)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:55)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor.access$201(ContextDispatcherInterceptor.java:46)
> at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor$CallableImpl.call(ContextDispatcherInterceptor.java:119)
> at org.exoplatform.portal.webui.application.ExoServerContext$1.doCallback(ExoServerContext.java:49)
> at org.gatein.wci.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:82)
> at org.gatein.wci.command.TomcatCommandDispatcher$1.execute(TomcatCommandDispatcher.java:61)
> at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.gatein.wci.command.CommandServlet.doGet(CommandServlet.java:135)
> at org.gatein.wci.command.CommandServlet.doPost(CommandServlet.java:166)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:605)
> at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:544)
> at org.gatein.wci.command.CommandServlet.include(CommandServlet.java:84)
> at org.gatein.wci.command.TomcatCommandDispatcher.include(TomcatCommandDispatcher.java:97)
> at org.gatein.wci.tomcat.TC7ServletContainerContext.include(TC7ServletContainerContext.java:111)
> at org.gatein.wci.ServletContainer.include(ServletContainer.java:393)
> at org.exoplatform.portal.webui.application.ExoServerContext.dispatch(ExoServerContext.java:45)
> at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:65)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.exoplatform.portal.pc.aspects.PortletLifecyclePhaseInterceptor.invoke(PortletLifecyclePhaseInterceptor.java:30)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.SecureTransportInterceptor.invoke(SecureTransportInterceptor.java:69)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.ValveInterceptor.invoke(ValveInterceptor.java:84)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.container.ContainerPortletInvoker.invoke(ContainerPortletInvoker.java:131)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java:263)
> at org.gatein.pc.federation.impl.FederatedPortletInvokerService.invoke(FederatedPortletInvokerService.java:163)
> at org.gatein.pc.federation.impl.FederatingPortletInvokerService.invoke(FederatingPortletInvokerService.java:246)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.PortletCustomizationInterceptor.invoke(PortletCustomizationInterceptor.java:76)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.gatein.pc.portlet.aspects.ConsumerCacheInterceptor.invoke(ConsumerCacheInterceptor.java:247)
> at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:111)
> at org.exoplatform.portal.webui.application.UIPortlet.invoke(UIPortlet.java:981)
> at org.exoplatform.portal.webui.application.UIPortletActionListener$ServeResourceActionListener.execute(UIPortletActionListener.java:340)
> at org.exoplatform.webui.event.Event.broadcast(Event.java:97)
> at org.exoplatform.portal.webui.application.UIPortletLifecycle.processAction(UIPortletLifecycle.java:116)
> at org.exoplatform.portal.webui.application.UIPortletLifecycle.processAction(UIPortletLifecycle.java:55)
> at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:119)
> at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processAction(UIPortalApplicationLifecycle.java:73)
> at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processAction(UIPortalApplicationLifecycle.java:36)
> at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:119)
> at org.exoplatform.webui.core.UIApplication.processAction(UIApplication.java:123)
> at org.exoplatform.portal.webui.workspace.UIPortalApplication.processAction(UIPortalApplication.java:748)
> at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:210)
> at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:167)
> at org.exoplatform.web.WebAppController.service(WebAppController.java:340)
> at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110)
> at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:133)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96)
> at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71)
> at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81)
> at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:62)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.gatein.portal.init.PortalCheckInitFilter.doFilter(PortalCheckInitFilter.java:66)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at org.gatein.sso.agent.tomcat.ServletAccessValve.invoke(ServletAccessValve.java:55)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.gatein.api.ApiException: Failed to load navigation
> at org.gatein.api.PortalImpl.getNavigation(PortalImpl.java:254)
> at org.gatein.ui.admin.redirect.beans.EditRedirectBean.checkSiteExists(EditRedirectBean.java:619)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at javax.el.BeanELResolver.invoke(BeanELResolver.java:484)
> at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:161)
> at org.apache.el.parser.AstValue.getValue(AstValue.java:173)
> at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:185)
> at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
> at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:68)
> at org.apache.el.parser.AstChoice.getValue(AstChoice.java:45)
> at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:185)
> at com.sun.faces.facelets.el.ELText$ELTextVariable.toString(ELText.java:217)
> at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:89)
> ... 167 more
> Caused by: org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: Illegal path entry: "mop:": Illegal path entry: "mop:": Illegal path entry: "mop:"
> at org.chromattic.core.DomainSession.getChild(DomainSession.java:364)
> at org.chromattic.core.ObjectContext.getChild(ObjectContext.java:241)
> at org.chromattic.core.mapper.onetomany.hierarchical.AnyChildMap.get(AnyChildMap.java:60)
> at org.gatein.mop.core.api.workspace.SiteContainer.getSite(SiteContainer.java:59)
> at org.gatein.mop.core.api.workspace.WorkspaceImpl.getSite(WorkspaceImpl.java:102)
> at org.exoplatform.portal.mop.navigation.DataCache.loadNavigation(DataCache.java:92)
> at org.exoplatform.portal.mop.navigation.DataCache.getNavigationData(DataCache.java:63)
> at org.exoplatform.portal.mop.navigation.NavigationServiceImpl.loadNavigation(NavigationServiceImpl.java:89)
> at org.exoplatform.portal.mop.navigation.NavigationServiceWrapper.loadNavigation(NavigationServiceWrapper.java:93)
> at org.gatein.api.PortalImpl.getNavigation(PortalImpl.java:249)
> ... 182 more
> Caused by: javax.jcr.RepositoryException: Illegal path entry: "mop:": Illegal path entry: "mop:": Illegal path entry: "mop:"
> at org.exoplatform.services.jcr.impl.core.LocationFactory.parsePathEntry(LocationFactory.java:239)
> at org.exoplatform.services.jcr.impl.core.LocationFactory.parseNames(LocationFactory.java:281)
> at org.exoplatform.services.jcr.impl.core.LocationFactory.parseRelPath(LocationFactory.java:112)
> at org.exoplatform.services.jcr.impl.core.NodeImpl.hasNode(NodeImpl.java:1448)
> at org.chromattic.core.jcr.SessionWrapperImpl.getChild(SessionWrapperImpl.java:190)
> at org.chromattic.core.DomainSessionImpl._getChild(DomainSessionImpl.java:774)
> at org.chromattic.core.DomainSession.getChild(DomainSession.java:361)
> ... 191 more
> Caused by: javax.jcr.RepositoryException: Illegal path entry: "mop:"
> at org.exoplatform.services.jcr.impl.core.LocationFactory.parsePathEntry(LocationFactory.java:230)
> ... 197 more
> {noformat}
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3292) Services Management - Invalid parameters lead to methods failing with exceptions
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3292?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3292:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/741
The linked pull request is only one part of if the solution. A fix is needed also in WS.
> Services Management - Invalid parameters lead to methods failing with exceptions
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3292
> URL: https://issues.jboss.org/browse/GTNPORTAL-3292
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Reporter: Miroslav Cupak
> Assignee: Peter Palaga
> Priority: Minor
>
> Description of problem:
> Methods in "templatestatistics" and "portalcontroller" section of the Services Management gadget fail with exception (NPE/MalformedURLException) if they are called with an invalid parameter. The exception is visible in the server log, but in the UI, you only see the message "Method's executed, return no result", which might be a bit confusing.
> For example methods "reloadConfiguration" without a parameter and "loadConfiguration" called with an invalid path both lead to the same message being shown in the gadget, whereas only one of them really failed with exception.
>
> Actual results:
> Exception is logged, message "Method's executed, return no result" is displayed.
> Expected results:
> It would be nice to have these two situations (failure/no return value) distinguished in a consistent way (methods in other sections don't log an exception and usually return at least some value).
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3292) Services Management - Invalid parameters lead to methods failing with exceptions
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3292?page=com.atlassian.jira.pl... ]
Peter Palaga edited comment on GTNPORTAL-3292 at 12/17/13 3:35 PM:
-------------------------------------------------------------------
The linked pull request is only one part of of the solution. A fix is needed also in WS.
was (Author: ppalaga):
The linked pull request is only one part of if the solution. A fix is needed also in WS.
> Services Management - Invalid parameters lead to methods failing with exceptions
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3292
> URL: https://issues.jboss.org/browse/GTNPORTAL-3292
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Reporter: Miroslav Cupak
> Assignee: Peter Palaga
> Priority: Minor
>
> Description of problem:
> Methods in "templatestatistics" and "portalcontroller" section of the Services Management gadget fail with exception (NPE/MalformedURLException) if they are called with an invalid parameter. The exception is visible in the server log, but in the UI, you only see the message "Method's executed, return no result", which might be a bit confusing.
> For example methods "reloadConfiguration" without a parameter and "loadConfiguration" called with an invalid path both lead to the same message being shown in the gadget, whereas only one of them really failed with exception.
>
> Actual results:
> Exception is logged, message "Method's executed, return no result" is displayed.
> Expected results:
> It would be nice to have these two situations (failure/no return value) distinguished in a consistent way (methods in other sections don't log an exception and usually return at least some value).
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3292) Services Management - Invalid parameters lead to methods failing with exceptions
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3292?page=com.atlassian.jira.pl... ]
Peter Palaga edited comment on GTNPORTAL-3292 at 12/17/13 11:49 AM:
--------------------------------------------------------------------
This issue is valid with the present GateIn master.
After a little bit of debugging, I can state the following:
(1) The {{NullPointerException}} is thrown in {{TemplateStatisticService.getExecutionCount(TemplateStatisticService.java:120)}}
(2) The {{NullPointerException}} is catched in {{RestResource.safeInvoke(MethodInvoker, Map<String, List<String>>)}} where {{Response.serverError()}} is returned, see [here|https://github.com/gatein/gatein-portal/blob/master/component/manage...]. This is probably incorrect, {{Response.serverError().build()}} or {{Response.serverError().entity(e.getMessage()).build()}} would probably be better.
(3) However, this return value is not handled properly in {{RequestDispatcher.processResponse(...)}}. There, the result is handled only based on the expected return type, in this case {{java.lang.Object}}, which boils down to the last {{else}}, see [here|https://github.com/exoplatform/ws/blob/master/exo.ws.rest.core/src/m...].
Hence, the main question is if this can be fixed in {{RequestDispatcher}}. Could perhaps the {{Resource}} type check ([here|https://github.com/exoplatform/ws/blob/master/exo.ws.rest.core/src/m...]) be applied also on {{o}}, like this:
{code}
else if (Response.class.isAssignableFrom(returnType) || o instanceof Response)
{code}
was (Author: ppalaga):
This issue is valid with the present GateIn master.
After a little bit of debugging, I can state the following:
(1) The {{NullPointerException}} is thrown in {{TemplateStatisticService.getExecutionCount(TemplateStatisticService.java:120)}}
(2) The {{NullPointerException}} is catched in {{RestResource.safeInvoke(MethodInvoker, Map<String, List<String>>)}} where {{Response.serverError()}} is returned, see [here|https://github.com/gatein/gatein-portal/blob/master/component/manage...]. This is probably incorrect, {{Response.serverError().build()}} or {{Response.serverError().entity(e.getMessage()).build()}} would probably be better.
(3) However, this return value is not handled properly in {{RequestDispatcher.processResponse(...)}}. There, the result is handled only based on the expected return type, in this case {{java.lang.Object}}, which boils down to the last {{else}}, see [here|https://github.com/exoplatform/ws/blob/master/exo.ws.rest.core/src/m...].
Hence, the main question is if this can be fixed in {{RequestDispatcher}}.
> Services Management - Invalid parameters lead to methods failing with exceptions
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3292
> URL: https://issues.jboss.org/browse/GTNPORTAL-3292
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Reporter: Miroslav Cupak
> Assignee: Peter Palaga
> Priority: Minor
>
> Description of problem:
> Methods in "templatestatistics" and "portalcontroller" section of the Services Management gadget fail with exception (NPE/MalformedURLException) if they are called with an invalid parameter. The exception is visible in the server log, but in the UI, you only see the message "Method's executed, return no result", which might be a bit confusing.
> For example methods "reloadConfiguration" without a parameter and "loadConfiguration" called with an invalid path both lead to the same message being shown in the gadget, whereas only one of them really failed with exception.
>
> Actual results:
> Exception is logged, message "Method's executed, return no result" is displayed.
> Expected results:
> It would be nice to have these two situations (failure/no return value) distinguished in a consistent way (methods in other sections don't log an exception and usually return at least some value).
--
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, 10 months
[JBoss JIRA] (GTNPORTAL-3292) Services Management - Invalid parameters lead to methods failing with exceptions
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3292?page=com.atlassian.jira.pl... ]
Peter Palaga commented on GTNPORTAL-3292:
-----------------------------------------
This issue is valid with the present GateIn master.
After a little bit of debugging, I can state the following:
(1) The {{NullPointerException}} is thrown in {{TemplateStatisticService.getExecutionCount(TemplateStatisticService.java:120)}}
(2) The {{NullPointerException}} is catched in {{RestResource.safeInvoke(MethodInvoker, Map<String, List<String>>)}} where {{Response.serverError()}} is returned, see [here|https://github.com/gatein/gatein-portal/blob/master/component/manage...]. This is probably incorrect, {{Response.serverError().build()}} or {{Response.serverError().entity(e.getMessage()).build()}} would probably be better.
(3) However, this return value is not handled properly in {{RequestDispatcher.processResponse(...)}}. There, the result is handled only based on the expected return type, in this case {{java.lang.Object}}, which boils down to the last {{else}}, see [here|https://github.com/exoplatform/ws/blob/master/exo.ws.rest.core/src/m...].
Hence, the main question is if this can be fixed in {{RequestDispatcher}}.
> Services Management - Invalid parameters lead to methods failing with exceptions
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3292
> URL: https://issues.jboss.org/browse/GTNPORTAL-3292
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Reporter: Miroslav Cupak
> Assignee: Peter Palaga
> Priority: Minor
>
> Description of problem:
> Methods in "templatestatistics" and "portalcontroller" section of the Services Management gadget fail with exception (NPE/MalformedURLException) if they are called with an invalid parameter. The exception is visible in the server log, but in the UI, you only see the message "Method's executed, return no result", which might be a bit confusing.
> For example methods "reloadConfiguration" without a parameter and "loadConfiguration" called with an invalid path both lead to the same message being shown in the gadget, whereas only one of them really failed with exception.
>
> Actual results:
> Exception is logged, message "Method's executed, return no result" is displayed.
> Expected results:
> It would be nice to have these two situations (failure/no return value) distinguished in a consistent way (methods in other sections don't log an exception and usually return at least some value).
--
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, 10 months