Deprecated API
Contents
-
Terminally Deprecated ElementsElementDescriptionThis constructor is not compatible with serializationthis method is deprecated and now the callback always receives a response that resolves to
truecom.vaadin.collaborationengine.CollaborationEngine.requestAccess(UserInfo, Consumer<AccessResponse>) this method is deprecated and now the callback always receives a response that resolves totruethe provided handler won't receive any events, please prefer using the default constructor with no parametersthe data-directory is not used since 6.3the handler is not used since 6.3license storage is not needed since 6.3the data-directory is not used since 6.3license storage is not needed since 6.3com.vaadin.collaborationengine.FormManager(ConnectionContext, UserInfo, String, CollaborationEngine) This constructor is not compatible with serializationlicense events will not be received by any listenerlicense events will not be received by any listenerany implementation of this interface won't receive any events, prefer using the defaultCollaborationEngineConfigurationconstructorlicense storage is not needed since 6.3This constructor is not compatible with serializationThis constructor is not compatible with serializationThis constructor is not compatible with serializationThis constructor is not compatible with serializationUseAvatar.setImageHandler(DownloadHandler)insteadUseColumnOptions.setPointStart(Instant)instead.Usage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedCookieConsent is deprecated and will be removed without a replacement in Vaadin 25.since 24.9 and will be removed in Vaadin 25. UseGrid(int, DataCommunicatorBuilder)instead.since 24.9 and will be removed in Vaadin 25. UseGrid(Class, DataCommunicatorBuilder, boolean)instead.since 24.9 and will be removed in Vaadin 25since 24.9 and will be removed in Vaadin 25com.vaadin.flow.component.grid.GridArrayUpdater.setUpdateQueueData(GridArrayUpdater.UpdateQueueData) since 24.9 and will be removed in Vaadin 25since 24.9 and will be removed in Vaadin 25UseAbstractColumn.getFooterText()orAbstractColumn.getFooterComponent()directlysince 24.9 and will be removed in Vaadin 25 where expanded items will no longer be available on the client-side, as hierarchy management is being moved to the server-side. Instead, it's recommended to assert the actual presence of expanded rows in the grid by checking row content.since 24.9 and will be removed in Vaadin 25 where explicit waiting for expanded rows to load will no longer be required, as full hierarchy will be returned in a single batch from the server.useAnchor(DownloadHandler, String)insteaduseAnchor.setHref(DownloadHandler)insteaduseHtmlObject(DownloadHandler)insteaduseHtmlObject(DownloadHandler,Param...)insteaduseHtmlObject(DownloadHandler,String)insteaduseHtmlObject(DownloadHandler,String, Param...)insteaduseHtmlObject.setData(DownloadHandler)insteaduseIFrame.setSrc(DownloadHandler)insteaduseImage(DownloadHandler, String)insteaduseImage.setSrc(DownloadHandler)insteadUseNativeLabelinstead, if you need the HTML<label>element, which is normally not needed within a Vaadin Flow application's high-level components. To use a Label that works in the older style of Vaadin 8 or Java Swing, and can be used both to label a component and to display loose text, an alternative is the Label available in Classic Components. ThisLabelcomponent /<label>element is not meant for loose text in the page - it should only be coupled with another component by using theLabel.setFor(Component)or by adding them to it with theHasComponents.add(Component...)method, for example if you useInput.UseNativeLabelElementinstead.UseSvgIcon(DownloadHandler)insteadUseSvgIcon(DownloadHandler, String)insteadUseSvgIcon.setSrc(DownloadHandler)insteadUseSvgIcon.setSrc(DownloadHandler, String)insteadsince 24.9 and will be removed in Vaadin 25. UseGridArrayUpdaterinstead.UseUploadHandlerinsteadUseUploadHandlerinsteadUseUploadHandlerinsteadUseFileFactoryinsteadUseUploadHandlerinsteadUseUploadHandlerinsteadUseUploadHandlerinsteaduseUpload(UploadHandler)insteaduseTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.com.vaadin.flow.component.upload.Upload.addSucceededListener(ComponentEventListener<SucceededEvent>) useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useUpload.setUploadHandler(UploadHandler)insteadsince 24.9 and will be replaced byArrayUpdaterin Vaadin 25.since 24.9 and will be replaced byArrayUpdater.Updatein Vaadin 25.since 24.9 and will be removed in Vaadin 25.since 24.9 and will be removed in Vaadin 25. UseHierarchicalDataCommunicator.collapse(T)instead.since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side andDataCommunicator.confirmUpdate(int)will be the only method called for confirming updates.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.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.since 24.9 and will be removed in Vaadin 25. UseHierarchicalDataCommunicator.expand(T)instead.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.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.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.since 24.9 and will be removed in Vaadin 25. To control the filter fromHierarchicalDataCommunicator, overrideHierarchicalDataCommunicator.setDataProvider(HierarchicalDataProvider, Object)and store the returned filter consumer.since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side andDataCommunicator.setViewportRange(int, int)will be the method responsible for managing the entire viewport range.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.Provider is deprecated, useFrontendUtils.getClientRoutes()instead.UseMenuData(String, Double, boolean, String, Class)instead.for annotation based view security useNavigationAccessControlwithAnnotatedViewAccessChecker.Webpack is not used anymore, this method is obsolete and have no replacements.to be removed, useOptions.withBuildResultFolders(File, File)instead.useUploadHandlerinsteaduseDownloadHandlerinsteaduseUploadHandlerinsteadwith no replacement. There should only be one DeploymentConfiguration per VaadinService, no VaadinSession-specific instances.AntPathRequestMatcheris deprecated and marked for removal. This method is deprecated without direct replacement; usePathPatternRequestMatcherinstead.AntPathRequestMatcheris deprecated and marked for removal. This method is deprecated without direct replacement; usePathPatternRequestMatcherinstead.usehttp.with(new VaadinStatelessSecurityConfigurer(), customizer)instead.to be removed. There is no direct replacement for this method. Shared object setup must be done along with other required configurations by callingVaadinStatelessSecurityConfigurer.apply(HttpSecurity, Customizer).UseVaadinSecurityConfigurerinstead. It follows the Spring's SecurityConfigurer pattern and we recommend use it to configure Spring Security with Vaadin:
Read more details in Security Configurer documentation.@Configuration @EnableWebSecurity @Import(VaadinAwareSecurityContextHolderStrategyConfiguration.class) public class SecurityConfig { @Bean SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception { return http.with(VaadinSecurityConfigurer.vaadin(), configurer -> {}).build(); } }AntPathRequestMatcher is deprecated and will be removed, useVaadinWebSecurity.pathMatchers(String...)instead.ViewAccessChecker is not used anymore by VaadinWebSecurity, and has been replaced byNavigationAccessControl. Calling this method will get a stub implementation that delegates to theNavigationAccessControlinstance.AntPathRequestMatcher is deprecated and will be removed, useVaadinWebSecurity.routePathMatchers(String...)instead.ViewAccessChecker has been replaced byNavigationAccessControl.No replacement plannedViewAccessChecker has been replaced byNavigationAccessControl.use the standardizedNonNullinsteaduse the standardizedNullableinsteadtesters for commercial components have been moved to a separated class to avoid class loading issues when using only Vaadin free tier. Make the test class implementCommercialTestWrappersand useCommercialTestWrappers.test(Chart)instead.
-
Deprecated InterfacesInterfaceDescriptionany implementation of this interface won't receive any events, prefer using the default
CollaborationEngineConfigurationconstructorlicense storage is not needed since 6.3Since 24.6, this interface is no longer supported. ConsiderHasValidationorHasValidatoras an alternative.Polymer template support is deprecated - we recommend you to useLitTemplateinstead. Read more details from the Vaadin blog.Polymer template support is deprecated - we recommend you to useLitTemplateinstead. Read more details from the Vaadin blog.since 24.9 and will be removed in Vaadin 25. UseGridArrayUpdaterinstead.UseUploadHandlerinsteadUseFileFactoryinsteadsince 24.9 and will be replaced byArrayUpdaterin Vaadin 25.since 24.9 and will be replaced byArrayUpdater.Updatein Vaadin 25.Provider is deprecated, useFrontendUtils.getClientRoutes()instead.useUploadHandlerinstead
-
Deprecated ClassesClassDescriptionlicense events will not be received by any listenerCookieConsent is deprecated and will be removed without a replacement in Vaadin 25.since 24.9 and will be removed in Vaadin 25Use
NativeLabelinstead, if you need the HTML<label>element, which is normally not needed within a Vaadin Flow application's high-level components. To use a Label that works in the older style of Vaadin 8 or Java Swing, and can be used both to label a component and to display loose text, an alternative is the Label available in Classic Components. ThisLabelcomponent /<label>element is not meant for loose text in the page - it should only be coupled with another component by using theLabel.setFor(Component)or by adding them to it with theHasComponents.add(Component...)method, for example if you useInput.UseNativeLabelElementinstead.since 24.8, usegetElement().setProperty("manualValidation", true)instead.Since 24.6, this event is no longer supported. Consider subscribing toValidationStatusChangeEventto get notified when the user enters input that cannot be parsed.UseUploadHandlerinsteadUseUploadHandlerinsteadUseUploadHandlerinsteadUseUploadHandlerinsteadUseUploadHandlerinsteadsince 24.9 and will be removed in Vaadin 25.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.UseBrowserLiveReloadAccessorinsteadPolymer template support is deprecated - we recommend you to useLitTemplateinstead. Read more details from the Vaadin blog.for annotation based view security useNavigationAccessControlwithAnnotatedViewAccessChecker.useUploadHandlerinsteaduseDownloadHandlerinsteadUseVaadinSecurityConfigurerinstead. It follows the Spring's SecurityConfigurer pattern and we recommend use it to configure Spring Security with Vaadin:
Read more details in Security Configurer documentation.@Configuration @EnableWebSecurity @Import(VaadinAwareSecurityContextHolderStrategyConfiguration.class) public class SecurityConfig { @Bean SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception { return http.with(VaadinSecurityConfigurer.vaadin(), configurer -> {}).build(); } }ViewAccessChecker has been replaced byNavigationAccessControl.No replacement plannedViewAccessChecker has been replaced byNavigationAccessControl.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.
-
Deprecated Enum ClassesEnum ClassDescriptionlicense events will not be received by any listener
-
Deprecated ExceptionsExceptionsDescription
-
Deprecated Annotation InterfacesAnnotation InterfaceDescriptionuse the standardized
NonNullinsteaduse the standardizedNullableinstead
-
Deprecated FieldsFieldDescriptionUse
FeatureFlags.SYSTEM_PROPERTY_PREFIX_EXPERIMENTALinstead.useElementConstants.ARIA_LABEL_ATTRIBUTE_NAMEinstead
-
Deprecated MethodsMethodDescriptionUse
DebugWindowConnection.broadcast(ObjectNode)instead.useDevModeInitializer.initDevModeHandler(Set, VaadinContext, Executor)providing a custom executor.The method does not work with the collaboration binder. UseCollaborationBinder.bind(HasValue, String)instead.This operation, along withCollaborationBinder.setBean(Object), is not supported by the collaboration binder. Instead ofCollaborationBinder.setBean(Object), you can provide the bean for populating the fields usingCollaborationBinder.setTopic(java.lang.String, com.vaadin.flow.function.SerializableSupplier<BEAN>), and write the values back to the bean usingBinder.writeBean(BEAN).This operation is not supported by the collaboration binder. You can instead provide the bean for populating the fields usingCollaborationBinder.setTopic(java.lang.String, com.vaadin.flow.function.SerializableSupplier<BEAN>)to avoid overriding currently edited values. If you explicitly want to reset the field values for every user currently editing the fields, you can useCollaborationBinder.reset(BEAN).This operation is not supported by the collaboration binder. You can instead provide the bean for populating the fields usingCollaborationBinder.setTopic(java.lang.String, com.vaadin.flow.function.SerializableSupplier<BEAN>), and write the values back to the bean usingBinder.writeBean(BEAN).this method is deprecated and now the callback always receives a response that resolves totruecom.vaadin.collaborationengine.CollaborationEngine.requestAccess(UserInfo, Consumer<AccessResponse>) this method is deprecated and now the callback always receives a response that resolves totruethe data-directory is not used since 6.3the handler is not used since 6.3license storage is not needed since 6.3the data-directory is not used since 6.3license storage is not needed since 6.3UseAvatar.setImageHandler(DownloadHandler)insteadas of 4.0. UseAbstractSeriesItem.setX(Instant)as of 4.0. UseAreaOptions.setPointStart(Instant)use setMax(Instant) insteaduse setMin(Instant) insteadas of 4.0. Use#setPointStart(Instant)as of 4.0. Use#setPointStart(Instant)UseColumnOptions.setPointStart(Instant)instead.as of 4.0. UseOhlcOptions.setPointStart(Instant)as of 4.0. Use#setPointStart(Instant)as of 4.0. Use#setPointStart(Instant)as of 4.0. UsePlotOptionsArea.setPointStart(Instant)as of 4.0. UsePlotOptionsArearange.setPointStart(Instant)as of 4.0. UsePlotOptionsAreaspline.setPointStart(Instant)as of 4.0. UsePlotOptionsAreasplinerange.setPointStart(Instant)as of 4.0. UsePlotOptionsBar.setPointStart(Instant)as of 4.0. UsePlotOptionsBoxplot.setPointStart(Instant)as of 4.0. UsePlotOptionsBubble.setPointStart(Instant)as of 4.0. UsePlotOptionsCandlestick.setPointStart(Instant)as of 4.0. UsePlotOptionsColumn.setPointStart(Instant)as of 4.0. UsePlotOptionsColumnrange.setPointStart(Instant)as of 4.0. UsePlotOptionsErrorbar.setPointStart(Instant)as of 4.0. UsePlotOptionsLine.setPointStart(Instant)as of 4.0. UsePlotOptionsOhlc.setPointStart(Instant)as of 4.0. UsePlotOptionsPolygon.setPointStart(Instant)as of 4.0. UsePlotOptionsScatter.setPointStart(Instant)as of 4.0. UsePlotOptionsSeries.setPointStart(Instant)as of 4.0. UsePlotOptionsSpline.setPointStart(Instant)as of 4.0. UsePlotOptionsWaterfall.setPointStart(Instant)as of 4.0. UseUtil.toHighchartsTS(Instant)as of 4.0. UseUtil.toServerInstant(double)does not work so don't usesince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedsince v24.4, not supportedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedUsage of Element API at Component level should be avoidedSince 24.8, useContextMenuBase.addComponent(Component...)insteadSince 24.8, useMenuManager.addComponent(Component...)insteadSince 24.8, useSubMenuBase.addComponent(Component...)insteadThis method should not be used outside.Since v24.8since v24.2, useHasComponents.add(Component...)instead.since v24.2, useDetails.removeAll()andHasComponents.add(Component...)instead.This method should not be used outside.Grid.getDefaultColumnFactory()should be used instead.since 24.9. In Vaadin 25, this method will continue to exist without theupdateQueueFactoryparameter.Grid.setPartNameGenerator(com.vaadin.flow.function.SerializableFunction<T, java.lang.String>)should be used instead.since 24.9 and will be removed in Vaadin 25since 24.9 and will be removed in Vaadin 25com.vaadin.flow.component.grid.GridArrayUpdater.setUpdateQueueData(GridArrayUpdater.UpdateQueueData) since 24.9 and will be removed in Vaadin 25UseAbstractColumn.getFooterText()orAbstractColumn.getFooterComponent()directlyUseAbstractColumn.getHeaderText()orAbstractColumn.getHeaderComponent()since 24.9 and will be removed in Vaadin 25 where expanded items will no longer be available on the client-side, as hierarchy management is being moved to the server-side. Instead, it's recommended to assert the actual presence of expanded rows in the grid by checking row content.since 24.9 and will be removed in Vaadin 25 where explicit waiting for expanded rows to load will no longer be required, as full hierarchy will be returned in a single batch from the server.useAnchor.setHref(DownloadHandler)insteaduseHtmlObject.setData(DownloadHandler)insteaduseIFrame.setSrc(DownloadHandler)insteaduseImage.setSrc(DownloadHandler)insteadUseSvgIcon.setSrc(DownloadHandler)insteadUseSvgIcon.setSrc(DownloadHandler, String)insteaduse findSourceFileuseIcon.getImg()insteaduseIcon.Options.setImg(DownloadHandler)insteadsince v24 the RichTextEditor uses the HTML value by default. UseRichTextEditor.getValue()instead.since 24.8, usegetElement().setProperty("manualValidation", true)instead.Since 24.6, this event is no longer supported. Consider subscribing toValidationStatusChangeEventto get notified when the user enters input that cannot be parsed.since 24.5, useValidationUtil.validateMaxConstraint(String, Comparable, Comparable)instead.since 24.5, useValidationUtil.validateRequiredConstraint(String, boolean, Object, Object)instead.since 24.5, useValidationUtil.validateMinConstraint(String, Comparable, Comparable)instead.This component has now multiple owners so this method has been replaced by #getOwners().since 24.0, useTabs.add(Tab...)instead.since 24.0, useTabs.addTabAsFirst(Tab)instead.since 24.0, useTabs.addTabAtIndex(int, Tab)instead.since 24.0, useTabs.getTabAt(int)instead.since 24.5, useTabs.getTabCount()instead.since 24.0, useTabs.indexOf(Tab)instead.since 24.0, useTabs.remove(Tab...)instead.since 24.0, useTabs.replace(Tab, Tab)instead.Since v24.8not supportednot supportednot supported(forRemoval=true) method is not enabled for client side anymore and connectClient is triggered by DOM event, to be removed in next major 25UseUI.doInit(VaadinRequest, int, String)insteadFor internal use only. Will be removed in the future.(forRemoval=true) method is not enabled for client side anymore and leave navigation is triggered by DOM event, to be removed in next major 25useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.com.vaadin.flow.component.upload.Upload.addSucceededListener(ComponentEventListener<SucceededEvent>) useTransferProgressListenerwithUploadHandlerimplementing theTransferProgressAwareHandlerinterface.since 24.4. UseUpload.fireUpdateProgress(long, long, String)useUpload.setUploadHandler(UploadHandler)insteadsince 24.9 and will be removed in Vaadin 26. UseDataCommunicator.computeViewportRange(int, int)instead.since 24.9 and will be removed in Vaadin 26. UseDataCommunicator.setViewportRange(int, int)instead.since 24.9 and will be removed in Vaadin 25. UseHierarchicalDataCommunicator.collapse(T)instead.since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side andDataCommunicator.confirmUpdate(int)will be the only method called for confirming updates.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.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.since 24.9 and will be removed in Vaadin 25. UseHierarchicalDataCommunicator.expand(T)instead.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.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.since 24.9 and will be removed in Vaadin 25. Use direct queries to the data source instead.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.since 24.9 and will be removed in Vaadin 25. To control the filter fromHierarchicalDataCommunicator, overrideHierarchicalDataCommunicator.setDataProvider(HierarchicalDataProvider, Object)and store the returned filter consumer.since 24.9 and will be removed in Vaadin 25 where HierarchicalDataCommunicator will be refactored to handle hierarchy management entirely on the server side andDataCommunicator.setViewportRange(int, int)will be the method responsible for managing the entire viewport range.com.vaadin.flow.router.Router.navigate(UI, Location, NavigationTrigger, JsonValue, boolean, boolean) UseAbstractConfiguration.getMode()insteadthis method does not resolve theme assets, useCssBundler.inlineImports(File, File, JsonNode)instead.Webpack is not used anymore, this method is obsolete and have no replacements.to be removed, useOptions.withBuildResultFolders(File, File)instead.with no replacement. There should only be one DeploymentConfiguration per VaadinService, no VaadinSession-specific instances.AntPathRequestMatcheris deprecated and marked for removal. This method is deprecated without direct replacement; usePathPatternRequestMatcherinstead.AntPathRequestMatcheris deprecated and marked for removal. This method is deprecated without direct replacement; usePathPatternRequestMatcherinstead.usehttp.with(new VaadinStatelessSecurityConfigurer(), customizer)instead.to be removed. There is no direct replacement for this method. Shared object setup must be done along with other required configurations by callingVaadinStatelessSecurityConfigurer.apply(HttpSecurity, Customizer).AntPathRequestMatcher is deprecated and will be removed, useVaadinWebSecurity.pathMatchers(String...)instead.ViewAccessChecker is not used anymore by VaadinWebSecurity, and has been replaced byNavigationAccessControl. Calling this method will get a stub implementation that delegates to theNavigationAccessControlinstance.AntPathRequestMatcher is deprecated and will be removed, useVaadinWebSecurity.routePathMatchers(String...)instead.This method is deprecated. Use$instead to find elements in the shadow root.testers for commercial components have been moved to a separated class to avoid class loading issues when using only Vaadin free tier. Make the test class implementCommercialTestWrappersand useCommercialTestWrappers.test(Chart)instead.
-
Deprecated ConstructorsConstructorDescriptionThis constructor is not compatible with serializationthe provided handler won't receive any events, please prefer using the default constructor with no parameterscom.vaadin.collaborationengine.FormManager
(ConnectionContext, UserInfo, String, CollaborationEngine) This constructor is not compatible with serializationThis constructor is not compatible with serializationThis constructor is not compatible with serializationThis constructor is not compatible with serializationThis constructor is not compatible with serializationas of 4.0. UseDataSeriesItem(Instant, Number)as of 4.0. UseDataSeriesItem(Instant, Number,Number)as of 4.0. UseFlagItem(Instant, String)as of 4.0. UseFlagItem(Instant, String, String)as of 4.0. UseOhlcItem(Instant, Number, Number, Number, Number)since 24.9 and will be removed in Vaadin 25. UseGrid(int, DataCommunicatorBuilder)instead.since 24.9 and will be removed in Vaadin 25. UseGrid(Class, DataCommunicatorBuilder)instead.since 24.9 and will be removed in Vaadin 25. UseGrid(Class, DataCommunicatorBuilder, boolean)instead.since 24.9 and will be replaced byUpdateQueue(Element element, int size)useAnchor(DownloadHandler, String)insteaduseHtmlObject(DownloadHandler)insteaduseHtmlObject(DownloadHandler,Param...)insteaduseHtmlObject(DownloadHandler,String)insteaduseHtmlObject(DownloadHandler,String, Param...)insteaduseImage(DownloadHandler, String)insteadUseSvgIcon(DownloadHandler)insteadUseSvgIcon(DownloadHandler, String)insteadsince 24.9. In Vaadin 25, the type of thedataCommunicatorBuilderparameter will useGridArrayUpdaterinstead ofTreeGridArrayUpdater.since 24.9. In Vaadin 25, the type of thedataCommunicatorBuilderparameter will useGridArrayUpdaterinstead ofTreeGridArrayUpdater.since 24.4. UseFileRejectedEvent(Upload, String, String)since 24.4. UseProgressUpdateEvent(Upload, long, long, String)useUpload(UploadHandler)insteadUse the version with binder reference insteadUse the version with binder reference insteadUse the version with binder reference insteadUse the version with binder reference insteadUse the version with binder reference insteadsince 24.9. In Vaadin 25, the type ofarrayUpdaterwill change toArrayUpdaterand thedataUpdaterparameter will be removed. Instead, the communicator will useArrayUpdater.Update.set(int, List)to re-render refreshed items.UseMenuData(String, Double, boolean, String, Class)instead.useFrontendTools(FrontendToolsSettings)instead, as it simplifies configuring the frontend tools and gives the default values to configuration parameters.useFrontendTools(FrontendToolsSettings)instead, as it simplifies configuring the frontend tools and gives the default values to configuration parameters.useFrontendTools(FrontendToolsSettings)instead, as it simplifies configuring the frontend tools and gives the default values to configuration parameters.useFrontendTools(FrontendToolsSettings)instead, as it simplifies configuring the frontend tools and gives the default values to configuration parameters.
-
Deprecated Enum ConstantsEnum ConstantDescriptionSince 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Use
TabVariant.LUMO_ICON_ON_TOPon individualTabinstances instead.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.UseTabVariant.LUMO_ICON_ON_TOPon individualTabinstances instead.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.Since 24.7, the Material theme is deprecated and will be removed in Vaadin 25.
DevModeInitializer.initDevModeHandler(Set, VaadinContext, Executor)providing a custom executor.