nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

browse.jsp - Cannot retrieve current Node if NodeId is null!

stk137

I have a problem where if a user go directly to browse.jsp when starting errors are thrown because the there's no current Node.

I am using JOSSO with an auth filter patterned after
NovellIChainsHTTPRequestAuthenticationFilter
http://forums.alfresco.com/viewtopic.php?t=8307&highlight=
(and guest access is not allowed)

I think that is somehow relevant as it doesn't happen with the standard auth filter from what I can tell.

What can I do to handle this? Should something be added to my auth filter (and NovellIChainsHTTPRequestAuthenticationFilter)? Or where can I make a change to handle this?

I'd like for users to be directed to My Dashboard in such a case (no current node yet), which is what would happen if they went to /alfresco/ instead of browse.jsp.

here's a more complete error:

javax.faces.FacesException: Cannot get value for expression '/images/icons/#{NavigationBean.nodeProperties.icon}.gif'
caused by:
org.apache.jasper.JasperException: Cannot get value for expression '/images/icons/#{NavigationBean.nodeProperties.icon}.gif'
caused by:
javax.faces.el.EvaluationException: Cannot get value for expression '/images/icons/#{NavigationBean.nodeProperties.icon}.gif'
caused by:
javax.faces.el.EvaluationException: Exception getting value of property nodeProperties of base of type : org.alfresco.web.bean.NavigationBean
caused by:
javax.faces.el.EvaluationException: Bean: org.alfresco.web.bean.NavigationBean, property: nodeProperties
caused by:
java.lang.reflect.InvocationTargetException
caused by:
org.alfresco.error.AlfrescoRuntimeException: Cannot retrieve current Node if NodeId is null!‍‍‍‍‍‍‍‍‍‍‍‍‍

Find more posts tagged with

Comments

gavinc

If you are going directly to the browse.jsp page due to the filter none of the logic in LoginBean.login() is going to be executed. You could therefore try adding this to your filter.

Hope this helps.

stk137

If you are going directly to the browse.jsp page due to the filter none of the logic in LoginBean.login() is going to be executed. You could therefore try adding this to your filter.

Hope this helps.

I don't think that's it LoginBean.login() does not do anything to set current node and I have the same logic that NovellIChainsHTTPRequestAuthenticationFilter
(http://forums.alfresco.com/viewtopic.php?t=8307&highlight= )
which seems to handle the relevant login stuff like setting the user home and that works ok.

gavinc

Fair point!

The whole UI context is setup as browse.jsp gets hit for the first time. The page references the beans which in turn setup everything needed.

One of the key bits is the processToolbarLocation() method in NavigationBean. Take a look at the code in there…

stk137

Fair point!

The whole UI context is setup as browse.jsp gets hit for the first time. The page references the beans which in turn setup everything needed.

One of the key bits is the processToolbarLocation() method in NavigationBean. Take a look at the code in there…

thanks,

that helped me get back on the right track
I was wrong to think this was related to my authentication filter, but I think I figured it out now.

I had removed the breadcrumbs at the top of the page (and displayed location path there instead). The breadcrumbs value expression will eventually cause the current node to be set to the configured default if the location is null.

IMHO this is some awkard dependency that should be reconsidered. I don't think removing the breadcrumbs should cause the rest of the page to fail like that. Also, I don't understand the logic behind why if the location is null, it will get set to the default, but if the current node is null it will throw an error instead. Maybe, if I knew it was safe to do, I'd change the getCurrentNode to return the default instead of an error when null.