Skip navigation links
  • Overview
  • Package
  • Class
  • Use
  • Tree
  • Deprecated
  • Index
  • Help

Deprecated API

Contents

  • Terminally Deprecated
  • Interfaces
  • Classes
  • Methods
  • Constructors
  • Terminally Deprecated Elements
    Element
    Description
    com.vaadin.flow.data.provider.hierarchy.HierarchicalArrayUpdater
    since 24.9 and will be replaced by ArrayUpdater in Vaadin 25.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalArrayUpdater.HierarchicalUpdate
    since 24.9 and will be replaced by ArrayUpdater.Update in Vaadin 25.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalCommunicationController
    since 24.9 and will be removed in Vaadin 25.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.collapse(T, boolean)
    since 24.9 and will be removed in Vaadin 25. Use HierarchicalDataCommunicator.collapse(T) instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.confirmUpdate(int, String)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side and DataCommunicator.confirmUpdate(int) will be the only method called for confirming updates.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.createHierarchyMapper(HierarchicalDataProvider<T, F>)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.doUnregister(Integer)
    since 24.9 and will no longer be called in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.expand(T, boolean)
    since 24.9 and will be removed in Vaadin 25. Use HierarchicalDataCommunicator.expand(T) instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getHierarchyMapper()
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getIndex(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getParentIndex(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getParentItem(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getPassivatedKeys(Set<String>)
    since 24.9 and will no longer be called in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.setFilter(F)
    since 24.9 and will be removed in Vaadin 25. To control the filter from HierarchicalDataCommunicator, override HierarchicalDataCommunicator.setDataProvider(HierarchicalDataProvider, Object) and store the returned filter consumer.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.setParentRequestedRange(int, int, T)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side and DataCommunicator.setViewportRange(int, int) will be the method responsible for managing the entire viewport range.
    com.vaadin.flow.data.provider.hierarchy.HierarchyMapper
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
  • Deprecated Interfaces
    Interface
    Description
    com.vaadin.flow.data.provider.hierarchy.HierarchicalArrayUpdater
    since 24.9 and will be replaced by ArrayUpdater in Vaadin 25.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalArrayUpdater.HierarchicalUpdate
    since 24.9 and will be replaced by ArrayUpdater.Update in Vaadin 25.
  • Deprecated Classes
    Class
    Description
    com.vaadin.flow.data.provider.hierarchy.HierarchicalCommunicationController
    since 24.9 and will be removed in Vaadin 25.
    com.vaadin.flow.data.provider.hierarchy.HierarchyMapper
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
  • Deprecated Methods
    Method
    Description
    com.vaadin.flow.data.provider.DataCommunicator.computeRequestedRange(int, int)
    since 24.9 and will be removed in Vaadin 26. Use DataCommunicator.computeViewportRange(int, int) instead.
    com.vaadin.flow.data.provider.DataCommunicator.setRequestedRange(int, int)
    since 24.9 and will be removed in Vaadin 26. Use DataCommunicator.setViewportRange(int, int) instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.collapse(T, boolean)
    since 24.9 and will be removed in Vaadin 25. Use HierarchicalDataCommunicator.collapse(T) instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.confirmUpdate(int, String)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side and DataCommunicator.confirmUpdate(int) will be the only method called for confirming updates.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.createHierarchyMapper(HierarchicalDataProvider<T, F>)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.doUnregister(Integer)
    since 24.9 and will no longer be called in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.expand(T, boolean)
    since 24.9 and will be removed in Vaadin 25. Use HierarchicalDataCommunicator.expand(T) instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getHierarchyMapper()
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side, requiring data to be stored in a different cache structure.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getIndex(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getParentIndex(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getParentItem(T)
    since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.getPassivatedKeys(Set<String>)
    since 24.9 and will no longer be called in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.setFilter(F)
    since 24.9 and will be removed in Vaadin 25. To control the filter from HierarchicalDataCommunicator, override HierarchicalDataCommunicator.setDataProvider(HierarchicalDataProvider, Object) and store the returned filter consumer.
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator.setParentRequestedRange(int, int, T)
    since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side and DataCommunicator.setViewportRange(int, int) will be the method responsible for managing the entire viewport range.
  • Deprecated Constructors
    Constructor
    Description
    com.vaadin.flow.data.binder.ValueContext()
    Use the version with binder reference instead
    com.vaadin.flow.data.binder.ValueContext(Component)
    Use the version with binder reference instead
    com.vaadin.flow.data.binder.ValueContext(Component, HasValue<?, ?>)
    Use the version with binder reference instead
    com.vaadin.flow.data.binder.ValueContext(Component, HasValue<?, ?>, Locale)
    Use the version with binder reference instead
    com.vaadin.flow.data.binder.ValueContext(Locale)
    Use the version with binder reference instead
    com.vaadin.flow.data.provider.hierarchy.HierarchicalDataCommunicator(CompositeDataGenerator<T>, HierarchicalArrayUpdater, SerializableConsumer<JsonArray>, StateNode, SerializableSupplier<ValueProvider<T, String>>)
    since 24.9. In Vaadin 25, the type of arrayUpdater will change to ArrayUpdater and the dataUpdater parameter will be removed. Instead, the communicator will use ArrayUpdater.Update.set(int, List) to re-render refreshed items.

Copyright © 2000–2026 Vaadin Ltd. All rights reserved.