Using the "typeMapping" attribute. Previous example shows that a drop zone could accept a dragable item or not. Special markers, which are placed at <rich:dragIndicator> , inform user about drop zone’s possible behaviors: "checkmark" appears if drop is accepted and "No" symbol if it is not. Moreover, some extra information (e.g. text message) could be put into the Indicator to reinforce the signal about drop zone’s behavior or pass some other additional sense. This reinforcement could be programmed and attributed to drop zone via "typeMapping" attribute using JSON syntax. The type of dragged zone (dragType) should be passed as "key" and name of <rich:dndParam> that gives needed message to Indicator as "value":

...

<rich:panel styleClass="dropTargetPanel">

     <f:facet name="header">

          <h:outputText value="PHP Frameworks" />

     </f:facet>

     

     <rich:dropSupport id="php" acceptedTypes="PHP" dropValue="PHP" dropListener="#{eventBean.processDrop}" reRender="phptable, src" 

                              typeMapping="{PHP: text_for_accepting, DNET: text_for_rejecting}">

          <rich:dndParam name="text_for_accepting" value="Drop accepted!" />

          <rich:dndParam name="text_for_rejecting" value="Drop is not accepted!" />

     </rich:dropSupport>

     ...

</rich:panel>

...

What happens on the page:

In examples above dropping a dragable item triggers the use a parameter in the event processing; Ajax request is sent and dropListener defined for the component is called.

Here is an example of moving records between tables. The example describes all the pieces for drag-and-drop. (To get extra information on these components, read the sections for these components.)

As draggable items, this table contains a list of such items designated as being of type "text" :

Example:

...

<rich:dataTable value="#{capitalsBean.capitals}" var="caps">

        <f:facet name="caption">Capitals List</f:facet>

        <h:column>

                <a4j:outputPanel>

                        <rich:dragSupport dragIndicator=":form:ind" dragType="text">

                                <a4j:actionparam value="#{caps.name}" name="name"/>

                        </rich:dragSupport>

                        <h:outputText value="#{caps.name}"/> 

                </a4j:outputPanel>

        </h:column>

</rich:dataTable>

...

As a drop zone, this panel will accept draggable items of type text and then rerender an element with the ID of box :

Example:

...

<rich:panel style="width:100px;height:100px;">

        <f:facet name="header">Drop Zone</f:facet>

        <rich:dropSupport acceptedTypes="text" reRender="box" 

                        dropListener="#{capitalsBean.addCapital2}"/>

</rich:panel>

...

As a part of the page that can be updated in a partial page update, this table has an ID of box :

Example:

...

<rich:dataTable value="#{capitalsBean.capitals2}" var="cap2" id="box">

        <f:facet name="caption">Capitals chosen</f:facet>

        <h:column>

                <h:outputText value="#{cap2.name}"/>

        </h:column>

</rich:dataTable>

...

And finally, as a listener, this listener will implement the dropped element:

Example:

...

public void addCapital2(DropEvent event) {

        FacesContext context = FacesContext.getCurrentInstance();

        Capital cap = new Capital();

        cap.setName(context.getExternalContext().getRequestParameterMap().get("name").toString());

        capitals2.add(cap);

}

...

Here is the result after a few drops of items from the first table:

In this example, items are dragged element-by-element from the rendered list in the first table and dropped on a panel in the middle. After each drop, a drop event is generated and a common Ajax request is performed that renders results in the third table.

As with every Ajax action component, <rich:dropSupport> has all the common attributes ( "timeout" , "limitToList" , "reRender" , etc.) for Ajax request customization.

Finally, the component has the following extra attributes for event processing on the client:

Developers can use their own custom JavaScript functions to handle these events.