Navigation controller cannot use path as query parameter -------------------------------------------------------- Key: GTNPORTAL-2303 URL: https://issues.jboss.org/browse/GTNPORTAL-2303 Project: GateIn Portal Issue Type: Bug Security Level: Public(Everyone can see) Reporter: Hai Nguyen Assignee: Vu Viet Phuong Labels: portal-s65, synced Changing the route configuration to use an url like /classic?path=home instead of /classic/home has severe bugs. On the first access there is an NPE: java.lang.NullPointerException: No null path accepted at org.exoplatform.portal.mop.user.UserPortalImpl.resolvePath(UserPortalImpl.java:429) at org.exoplatform.portal.webui.page.UIPageActionListener$ChangeNodeActionListener.execute(UIPageActionListener.java:80) at org.exoplatform.webui.core.UIComponent.broadcast(UIComponent.java:360) at org.exoplatform.portal.webui.workspace.UIPortalApplication.processAction(UIPortalApplication.java:563) at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:177) at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:150) On other access the NPE does not appear anymore but the navigation on the classic site works partially. Here is the route I changed in the configuration: <!-- The portal access --> <route path="/{gtn:lang}/{gtn:sitename}"> <route-param qname="gtn:sitetype"> <value>portal</value> </route-param> <path-param qname="gtn:lang" encoding="preserve-path"> <pattern>([A-Za-z]{2}(-[A-Za-z]{2})?)?</pattern> </path-param> <request-param qname="gtn:path" name="path" value-mapping="never-empty"/> </route>

Navigation controller cannot use path as query parameter -------------------------------------------------------- Key: GTNPORTAL-2303 URL: https://issues.jboss.org/browse/GTNPORTAL-2303 Project: GateIn Portal Issue Type: Bug Security Level: Public(Everyone can see) Reporter: Hai Nguyen Assignee: Vu Viet Phuong Labels: portal-s65, synced Fix For: 3.2.0-CR01 Time Spent: 30 minutes Remaining Estimate: 0 minutes Changing the route configuration to use an url like /classic?path=home instead of /classic/home has severe bugs. On the first access there is an NPE: java.lang.NullPointerException: No null path accepted at org.exoplatform.portal.mop.user.UserPortalImpl.resolvePath(UserPortalImpl.java:429) at org.exoplatform.portal.webui.page.UIPageActionListener$ChangeNodeActionListener.execute(UIPageActionListener.java:80) at org.exoplatform.webui.core.UIComponent.broadcast(UIComponent.java:360) at org.exoplatform.portal.webui.workspace.UIPortalApplication.processAction(UIPortalApplication.java:563) at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:177) at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:150) On other access the NPE does not appear anymore but the navigation on the classic site works partially. Here is the route I changed in the configuration: <!-- The portal access --> <route path="/{gtn:lang}/{gtn:sitename}"> <route-param qname="gtn:sitetype"> <value>portal</value> </route-param> <path-param qname="gtn:lang" encoding="preserve-path"> <pattern>([A-Za-z]{2}(-[A-Za-z]{2})?)?</pattern> </path-param> <request-param qname="gtn:path" name="path" value-mapping="never-empty"/> </route>