I looked at many examples of Vaadin and all of them use Vaadin servlet. Is it possible to use Vaadin framework outside a servlet container? If yes, how to achieve that? A sample code would be most welcome.
Vaadin needs a Servlet Environment. Notice however that the Servlet Specification is just a tiny (but essential) part of Java EE. A Servlet Container is typically very light-weight.
So use Undertow, Jetty, Tomcat or any other Servlet Container. Note that these products are all embeddable, ideal for micro services.
Web Components
In recent years, the Vaadin company has been producing versions of their widgets that can run outside of their server-side Java framework. They are taking advantage of advancements being made in Web Components and the Google Polymer project.
The company has launched their Vaadin Elements program.
Vaadin Elements is a set of custom HTML elements tailored for business applications. It extends the Google Polymer library with elements like data grid, charts and combo box so you can build the app your business needs. The elements are actively maintained and tested to ensure compatibility with the latest Polymer releases.
For example, their excellent rows-and-columns Vaadin Grid component is available in three editions:
Vaadin FrameworkThe Vaadin server-side Java framework based on Java Servlet technology.
Vaadin GWT Polymer ElementsFor Google Web Toolkit developers.
Vaadin ElementsFor JavaScript developers.
Be forewarned: the Vaadin team is pushing the envelope in these new web technologies. But they are very excited by their successes and eagerly invite people to try out the new editions of their products.
See the Vaadin company blog for announcements of their success with various components in this effort.
Just yesterday (2016-04) they described a Date Picker widget and a file-uploader widget, both being available as betas in their Vaadin Elements collection.
The week before that they described a beta of a ComboBox widget for Polymer.
The week before that was an entry about their Vaadin Charts 3.0 product being finalized and shipping, both for the Vaadin Framework (server-side, Java) as well as for client-side developers using Polymer, AngularJS, React, or other HTML5 library.
For a very technical discussion, see the video and slides from a meeting at the Seattle Java Users Group (SeaJUG) in 2016-03 in a presentation by Vaadin staffer, Marcus Hellberg.
Related
I would like to ask what is the free component for diagram/chart/graph in Vaadin 14?
I am using Vaadin14 and Spring boot in my project,
Available third party add-ons shared by users can be found at the Vaadin directory. You should search if there is any that suits you :)
I have never tried this add-on, but it seems to be widely used and actively maintained : ApexCharts.js
SO Charts - this add-on is a wrapper around the echarts Javascript library for using it with Vaadin Flow.
I'm new to Angular and I'm a bit confused whether the implementation of the angular components reflects the recent (2018) material design system changes or they are just updating the old version of the system?
the Angular components version is been updated:
https://trimox.github.io/angular-mdc-web/#/angular-mdc-web/home
But it seems to me that the Angular Dart components version is still using the old system:
https://dart-lang.github.io/angular_components/
Am I missing something or the Angular components will not get the latest material design updates?
(I think the Angular team is using foundations and adapters to adapt the vanilla web version of the updated material design system, is the Angular Dart team doing the same?)
The specs and M2 components are still being worked on. We have some ready, but I don't see us releasing them until after internal teams have shaken out most of the bugs. They are still going through big API changes to make sure they work well in our products.
There is one that is released which is the material_card.
Does anybody know how to build a dynamic vaadin grid like here:
https://cdn.vaadin.com/vaadin-grid/2.0.0-alpha3/demo/data.html#dynamic-height
It is strange because I have never seen that vaadin allow to write code as it is in the link above. Where to put this template? Is it possible that in a standard vaadin code?
This is the demo page for Vaadin Grid Element, not the Grid from Vaadin Framework.
Grid element is a part of so-called Vaadin Elements - set of client-side widgets which can be used from other javascript frameworks (e.g. React, Angular, etc.).
Vaadin released Elements separately from their Framework, so in order to use them from a traditional Vaadin application, you'll need to take additional steps. See this blog post for the detailed walkthrough: Using Vaadin Elements with Vaadin Framework.
You also might want to look through this similar question: Is Vaadin Elements meant to be used with the Vaadin Framework?.
I am using spring framework for my java enterprise application .
I felt javascript / jquery is hard to maintain for larger enterprise application.
Classes and Objects makes code maintenance easier.
how can i use dart with spring framework / JSP?.
The HTML code can be generate with JSP. However, we cannot debug with Dart Editor anymore.
It would be nice and more encourage people to start to use Dart by just by support debugging a HTML with dart from non-standard dart editor debug server.
For example: The HTML part is served by a Jetty server which contains links to dart
and we should be able to debug in Dart Editor.
Personally, This is the most needed feature otherwise, it's difficult to ask people to migrate old sytem with JSP, PHP to start to use Dart
We are listening to Dartian reponse.
I found one issue in Dart issue list: https://code.google.com/p/dart/issues/detail?id=3748
The best way to use dart with springframework and JSP is to create rich client app (RCP) in dart and use springframework and JSP for implementing a service layer that should be used by the RCP.
There are various disadvantages if you chose to mix the application state between the client (browser) and the server. Much more scalable model is to build on service oriented architecture (SOA) and keep the UI logic solely on the client side.
Hope it helps ;-)
Could someone please explain something for me.
I am confused. Currently Polymer and Web UI seems to be two separate projects with a lot of similarities.
Is Polymer to succeed Web UI - meaning Web UI will be discontinued in favour of Polymer?
Yes, Polymer is the successor to Web UI. At some point in the future, once Polymer is more stable, Web UI will be abandoned.
For now though, it still may make sense to use Web UI if you need it for a production app.
As mentioned already, yes Polymer is the next version of web_ui. It is being developed in conjunction with the JavaScript version of Polymer. web_ui is currently in extended support mode, in which bug fixes are applied to keep the library functional (particularly as new SDK releases are made), however there will be no new functionality added to web_ui.
As of yesterday, the integrated build reached 0.8.1, and with Polymer 0.8.1, Polymer has virtually reached parity with web_ui and in some areas already surpassed with additional functionality.
Google has committed to maintaining web_ui for existing projects, however I would highly recommend that any new projects be started with Polymer. It is also the time to look at porting any old web_ui projects over to the new libraries (something I'm in the process of doing myself).