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.

Node type not available through BrowseBean?

davidpisaac

Hello-

I cannot seem to access a node's "type" property through the BrowseBean in a JSP through a richList. That is:

<h

utputText id="col10-nodeinfo" value="#{NavigationBean.currentNode.type}" />

correctly shows a node's type, but:

<h

utputText id="col10-nodeinfo2" value="#{r.type}" />

where r is bound to a node in a richList displays nothing. Aren't these both Node objects? I can display name and ID, but not type or path.

I am trying to implement a custom action tied directly to an item in the browse page list based on the object type. Since the link on the object's icon and name are not configurable Actions, I must perform this test in a modified browse JSP rather than through an Alfresco config with evaluator for an action.

Find more posts tagged with

Comments

davidpisaac

I think I just found the answer to my own question, but I'll leave this post for others. BrowseBean.nodes apparently returns a list of lightweight MapNodes, that have some but not all properties of a Node populated.

dhalupa

If I may add, I think that all properties from Node are also present in TransientMapNode. The difference comes from the fact that TransientMapNode is implementing Map interface. Therefore, in the first case, JSF will call method getType() which will return Qname of node type, while in the second case JSF will not invoke getType() method, but rather, get("type") method of Map interface which will return null.

kevinr

If I may add, I think that all properties from Node are also present in TransientMapNode. The difference comes from the fact that TransientMapNode is implementing Map interface. Therefore, in the first case, JSF will call method getType() which will return Qname of node type, while in the second case JSF will not invoke getType() method, but rather, get("type") method of Map interface which will return null.

You are correct.

Kevin

gilles

Did you suceed in getting the type of your beans in the richlist?