* visible in the container.
* </p>
* <p>
- * When an {@link com.vaadin.data.Ordered} or
- * {@link com.vaadin.data.Indexed} container is filtered, all operations of
- * these interfaces should only use the filtered contents and the filtered
- * indices to the container.
+ * When an {@link Ordered} or {@link Indexed} container is filtered, all
+ * operations of these interfaces should only use the filtered contents and
+ * the filtered indices to the container.
* </p>
* <p>
* How filtering is performed when a {@link Hierarchical} container
* documented in the implementing class.
* </p>
* <p>
- * Adding items (if supported) to a filtered {@link com.vaadin.data.Ordered}
- * or {@link com.vaadin.data.Indexed} container should insert them
- * immediately after the indicated visible item. The unfiltered position of
- * items added at index 0, at index {@link com.vaadin.data.Container#size()}
- * or at an undefined position is up to the implementation.
+ * Adding items (if supported) to a filtered {@link Ordered} or
+ * {@link Indexed} container should insert them immediately after the
+ * indicated visible item. The unfiltered position of items added at index
+ * 0, at index {@link com.vaadin.data.Container#size()} or at an undefined
+ * position is up to the implementation.
* </p>
*
* @since 5.0
* (identified by its Id) and optionally also a property identifier (e.g. a
* table column identifier when transferring a single table cell).
*
- * The component must implement the interface {@link Container.Viewer}.
+ * The component must implement the interface
+ * {@link com.vaadin.data.Container.Viewer}.
*
* In most cases, receivers of data transfers should depend on this class
* instead of its concrete subclasses.
/**
* Returns the container data source from which the transfer occurs.
*
- * {@link Container.Viewer#getContainerDataSource()} is used to obtain the
- * underlying container of the source component.
+ * {@link com.vaadin.data.Container.Viewer#getContainerDataSource()} is used
+ * to obtain the underlying container of the source component.
*
* @return Container
*/
public Container getSourceContainer() {
- Component sourceComponent = getSourceComponent();
+ Component sourceComponent = getSourceComponent();
if (sourceComponent instanceof Container.Viewer) {
return ((Container.Viewer) sourceComponent)
.getContainerDataSource();
* DropHandlers contain the actual business logic for drag and drop operations.
* <p>
* The {@link #drop(DragAndDropEvent)} method is used to receive the transferred
- * data and the #getAcceptCriterion()} method contains the (possibly client side
- * verifiable) criterion whether the dragged data will be handled at all.
+ * data and the {@link #getAcceptCriterion()} method contains the (possibly
+ * client side verifiable) criterion whether the dragged data will be handled at
+ * all.
*
* @since 6.3
*
* {@link DropHandler}. Implementation may for exmaple translate the drop
* target details provided by the client side (drop target) to meaningful
* server side values. If null is returned the terminal implementation will
- * automatically create a {@link TargetDetails} with raw client side
- * data.
+ * automatically create a {@link TargetDetails} with raw client side data.
*
* @see DragSource#getTransferable(Map)
*
- * @param rawVariables
+ * @param clientVariables
* data passed from the DropTargets client side counterpart.
* @return A DropTargetDetails object with the translated data or null to
* use a default implementation.
public interface TargetDetails extends Serializable {
/**
- * Gets target data associated to given string key
+ * Gets target data associated with the given string key
*
* @param key
- * @return
+ * @return The data associated with the key
*/
public Object getData(String key);
public void paintResponse(PaintTarget target) throws PaintException;
/**
- * Validates the data in event to be appropriate for
- * {@link DropHandler#drop(com.vaadin.event.dd.DropEvent)} method.
+ * Validates the data in event to be appropriate for the
+ * {@link DropHandler#drop(DragAndDropEvent)} method.
* <p>
- * Note that even if your criterion is matched on client side, it is a very
- * good manner to validate the data on server side too.
+ * Note that even if your criterion is validated on client side, you should
+ * always validate the data on server side too.
*
* @param dragEvent
* @return