We use cookies to serve our customers and website visitors in the best possible way. Cookies are used for the proper functioning of the website and for improving the user experience, monitoring visitor traffic and marketing purposes. By continuing to browse the site, you agree to our use of cookies. You can read more about cookies here.
-
Terminally Deprecated ElementsElementDescriptionThis constructor is not compatible with serializationcom.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 serializationUsage 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 avoidedUseAbstractColumn.getFooterText()
orAbstractColumn.getFooterComponent()
directlyUseNativeLabel
instead, 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. ThisLabel
component /<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
.UseNativeLabelElement
instead.for annotation based view security useNavigationAccessControl
withAnnotatedViewAccessChecker
.to be removed, useOptions.withBuildResultFolders(File, File)
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)
.ViewAccessChecker is not used anymore by VaadinWebSecurity, and has been replaced byNavigationAccessControl
. Calling this method will get a stub implementation that delegates to theNavigationAccessControl
instance.ViewAccessChecker has been replaced byNavigationAccessControl
.ViewAccessChecker has been replaced byNavigationAccessControl
.
-
Deprecated InterfacesInterfaceDescriptionPolymer template support is deprecated - we recommend you to use
LitTemplate
instead. Read more details from the Vaadin blog.Polymer template support is deprecated - we recommend you to useLitTemplate
instead. Read more details from the Vaadin blog.
-
Deprecated ClassesClassDescriptionUse
NativeLabel
instead, 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. ThisLabel
component /<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
.UseNativeLabelElement
instead.UseBrowserLiveReloadAccessor
insteadPolymer template support is deprecated - we recommend you to useLitTemplate
instead. Read more details from the Vaadin blog.for annotation based view security useNavigationAccessControl
withAnnotatedViewAccessChecker
.ViewAccessChecker has been replaced byNavigationAccessControl
.ViewAccessChecker has been replaced byNavigationAccessControl
.
-
Deprecated Fields
-
Deprecated MethodsMethodDescriptionThe method does not work with the collaboration binder. Use
CollaborationBinder.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)
.as of 4.0. UseAbstractSeriesItem.setX(Instant)
as of 4.0. UseAreaOptions.setPointStart(Instant)
as of 4.0. Use#setPointStart(Instant)
as of 4.0. Use#setPointStart(Instant)
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 avoidedThis method should not be used outside.since 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.UseAbstractColumn.getFooterText()
orAbstractColumn.getFooterComponent()
directlyUseAbstractColumn.getHeaderText()
orAbstractColumn.getHeaderComponent()
since v24 the RichTextEditor uses the HTML value by default. UseRichTextEditor.getValue()
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.0, useTabs.indexOf(Tab)
instead.since 24.0, useTabs.remove(Tab...)
instead.since 24.0, useTabs.replace(Tab, Tab)
instead.not 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 25since 24.4. UseUpload.fireUpdateProgress(long, long, String)
UseAbstractConfiguration.getMode()
insteadthis method does not resolve theme assets, useCssBundler.inlineImports(File, File, JsonObject)
instead.to be removed, useOptions.withBuildResultFolders(File, File)
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)
.ViewAccessChecker is not used anymore by VaadinWebSecurity, and has been replaced byNavigationAccessControl
. Calling this method will get a stub implementation that delegates to theNavigationAccessControl
instance.
-
Deprecated ConstructorsConstructorDescriptionThis constructor is not compatible with serializationcom.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.4. UseFileRejectedEvent(Upload, String, String)
since 24.4. UseProgressUpdateEvent(Upload, long, long, String)
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.