From 5fc51c61fa3e2f98da293966d73cc1b7f1c7627c Mon Sep 17 00:00:00 2001 From: =?utf8?q?Pekka=20Hyv=C3=B6nen?= Date: Wed, 27 Mar 2019 07:32:59 +0200 Subject: [PATCH] Do not recommend crappy old containers in tutorial (#11514) Removed link to and recommendation for SQLContainer --- .../articles/VaadinTutorialForSwingDevelopers.asciidoc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/documentation/articles/VaadinTutorialForSwingDevelopers.asciidoc b/documentation/articles/VaadinTutorialForSwingDevelopers.asciidoc index d7bc0702dd..59f4af1402 100644 --- a/documentation/articles/VaadinTutorialForSwingDevelopers.asciidoc +++ b/documentation/articles/VaadinTutorialForSwingDevelopers.asciidoc @@ -505,11 +505,7 @@ You can pretty easily write a totally custom version for your specific use case, but the strongly suggested method is to use helpers like https://vaadin.com/web/matti/blog/-/blogs/connecting-large-amounts-of-data-to-ui[LazyList] or https://vaadin.com/addon/lazy-query-container[LazyQueryContainer] -instead. In most lazy loading cases, those are the tools that you really -should use, but in some architectures you can also consider using -https://vaadin.com/api/com/vaadin/data/util/sqlcontainer/SQLContainer.html[SqlContainer] -or https://vaadin.com/addon/vaadin-jpacontainer[JPAContainer] which do -rather optimized lazy loading automatically as well. +instead. [[structuring_your_ui_code]] Structuring your UI code -- 2.39.5