nxu

Facelet tag handler that exposes an expression as a variable, and makes it possible to cache it.

This is very close to the c:set tag, but allows caching, and the variable is only exposed inside the tag. Note that this tag will not work as expected when used with iteration variables inside a standard table, for instance.

        <nxu:set var="actions" value="#{webActions.getActionsList('SUBVIEW_UPPER_LIST')}" cache="true">
          <nxu:dataList var="action" value="#{actions}">
            ...
          </nxu:dataList>
        </nxu:set>
      

Facelet tag handler that performs an iteration.

This handler is very close to the facelets c:forEach tag handler. It holds additional configuration to handle ajax re-rendering of lists, avoiding potential JSF duplicate id issues, as well as cache issue, when the iteration list changes.

        <nxu:repeat items="#{layoutNames}" var="layout">
          <nxl:layout name="#{layout}" value="#{document}" />
        </nxu:repeat>
      

This tag is similar to the f:selectItems tag, except that it allows to iterate on any kind of data, and have control on the resulting selection values and labels.

It has been adapted to work with datamodel lists wrapped by Seam (when using the Datamodel annotation).

        <nxu:selectItems value="#{myBean.myList}" var="item"
          itemValue="#{item.id}" itemLabel="#{item.title}" />

        <nxu:selectItems value="#{documentList}" var="document"
          itemValue="#{document.ref}" itemLabel="#{document.dublincore.title}" />
      

Util tag to perform a complex file upload dealing with edition and deletion.

It only deals with Nuxeo Core blobs.

This tag uses a component that will handle its rendering using other existing components. It will present a radio menu with existing choices: upload a file, keep it (eventually change its filename), delete it, or do nothing. Choices will be presented automatically given values and tag attributes (is there a blob set, is there a filename, is the blob required, etc...).

It uses the nxu:outputFile related component rendering for the "keep" option and the tomahwak t:inputFileUpload tag for the "upload" option.

It is possible to use a facet named "download" to override the default "keep" option rendering (e.g the document download presentation).

        <nxu:inputFile value="#{document.file.content"
          filename="#{document.file.filename}"
          editFilename="true" />
      

Register an InputFileMimetypeValidator instance on the UIComponent associated with the closest parent UIComponent custom action.

        <nxu:inputFile value="#{document.file.content}"
          filename="#{document.file.filename}"
          editFilename="true">
          <nxu:validateFileMimetype extensions=".jpg, .png" />
        </nxu:inputFile>
      

Util tag to perform a blob rendering, useful if a rest URL cannot be provided (on a JSF form postback for instance).

It only deals with Nuxeo Core blobs.

Display is an immediate link to the blob, with filename as link value if provided, together with the blob mimetype icon.

        <nxu:outputFile value="#{document.file.content}"
          filename="#{document.file.filename}" />
      

Tag that perform edition of a list of items. Note that this tag is deprecated since Nuxeo 7.2: use nxu:jsInputList instead.

It only deals with lists or arrays of serializable objects.

This tags puts a model in the request which can be accessed to get information about each list item value.

Examples make extensive use of ajax4jsf so that validation of other components that may be on the page does not occur while adding and deleting items in the list.

        <a4j:region renderRegionOnly="false">
          <a4j:outputPanel ajaxRendered="true">
            <nxu:inputList value="#{currentDocument.files.files}"
              id="files" model="model" diff="true"
              template="#{nxd:defaultValue('files', 'files')}">
              <h:panelGrid columns="2">
                <a4j:commandLink immediate="true"
                  actionListener="#{editableListBean.performAction}"
                  reRender="fichiers" bypassUpdates="true">
                  <h:graphicImage value="/icons/delete.png" />
                  <f:param name="for" value="fichiers" />
                  <f:param name="index" value="#{model.rowIndex}" />
                  <f:param name="type" value="remove" />
                </a4j:commandLink>
                <h:panelGroup>
                  <nxu:inputFile value="#{model.rowData.file}"
                    filename="#{model.rowData.fileName}" editFilename="false"
                    id="file" />
                  <h:message for="file" />
                </h:panelGroup>
              </h:panelGrid>
            </nxu:inputList>
          </a4j:outputPanel>
          <a4j:commandLink immediate="true"
            actionListener="#{editableListBean.performAction}"
            reRender="fichiers">
            <h:graphicImage value="/icons/action_add.gif" />
            <f:param name="for" value="fichiers" />
            <f:param name="type" value="add" />
          </a4j:commandLink>
        </a4j:region>
      

Calendar with date and time chosing.

        <nxu:inputDateTime
          value="#{document.project.dueDate}"
          format="mm/dd/YY"
          required="false" />
      

Allows creating radio checkboxes, that will be referenced for display in another part of the page when used in conjunction with nxu:radio.

          <nxu:selectOneRadio id="objectType"
            value="#{relationActions.objectType}" layout="spread">
            <f:selectItem
              itemLabel="#{messages['label.relation.object.text']}"
              itemValue="literal" />
            <f:selectItem itemLabel="#{messages['label.relation.object.uri']}"
              itemValue="uri" />
            <f:selectItem
              itemLabel="#{messages['label.relation.object.documentUid']}"
              itemValue="document" />
          </nxu:selectOneRadio>
          [...]
          <nxu:radio for="objectType" index="0" id="literal" />
          [...]
          <nxu:radio for="objectType" index="1" id="uri" />
          [...]
          <nxu:radio for="objectType" index="2" id="document" />
        

Tag handler generating a form (or not) depending on attributes values, useful when handling widgets that may need to be surrounded by a form (or not) depending on their configuration.

Available since 8.2

        <nxu:form id="#{widget.id}_form"
          useAjaxForm="#{useAjaxForm and supportAjax}"
          disableDoubleClickShield="#{disableDoubleClickShield}">
          <nxl:widget widget="#{widget}" value="#{fieldOrValue}" />
        </nxu:form>
      

Returns a translated message with optional given parameters, to be used when formatting the message value.

Equivalent to using the h:outputFormat tag, with f:param subtags as parameters.

Returns the target component absolute id given an anchor in the tree and a local id.

WARNING: this resolution is costly and can affect your page performances.

If given targetId parameter contains spaces, consider that several ids should be resolved, and split them.