BUG rich:tree selectionType=server not working

[bcn]

The component reference for RichFaces 4 states that rich:tree selectionType can be "server", but:

17:35:25,373 GRAVE [javax.enterprise.resource.webcontainer.jsf.application] Error Rendering View[/searchestab.xhtml]: java.lang.IllegalArgumentException: server

    at org.richfaces.renderkit.TreeRendererBase.getSelectionType(TreeRendererBase.java:164) [:4.0.0-SNAPSHOT]

    at org.richfaces.renderkit.html.TreeRenderer.encodeEnd(TreeRenderer.java:154) [:4.0.0-SNAPSHOT]

    at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:879) [:2.0.3-]

which is obvious in the code:

    protected SwitchType getSelectionType(FacesContext context, UIComponent component) {

        AbstractTree tree = (AbstractTree) component;

        SwitchType selectionType = getSelectionTypeOrDefault(tree);

        if (selectionType != SwitchType.ajax && selectionType != SwitchType.client) {

            //TODO - better message

            throw new IllegalArgumentException(String.valueOf(selectionType));

        }

        return selectionType;

    }

Apart from the obvious bug, my question is: if I overwrite the code and allow "server", will the server mode work?

[bcn]

I created a jira bug:

https://issues.jboss.org/browse/RF-10984

[nbelaevski]

Hi,

'server' mode in this context means that the whole page will be reloaded immediately on each selection change in tree - so, just to confirm, is this exactly what you need? If you set 'ajax' mode, server listeners will get events for selection changes.

[bcn]

Well, I use ajax mode now, together with the "render" attribute, and that works ok for me.

Maybe you want to implement "server" for the sake of completeness, like there is for the collapsable panel switch type,

but that depends on your priorities.

Anyway, the documentation should match the code :-)

Thanks