JSF and Vaadin Grid

[ would like to use my data for my continued education of Vaadin - how can I use my data instead of the array data in the example ]

I have a JSF web app

  1. managed bean – MODEL
  2. managed bean – CONTROLLER
  3. remote MySql connection pool – CONTEXT.xml
  4. remote data source resource ref – WEB.xml
  5. mapping data calls – DAO implementation using JDBC

Would I follow the same example as in the first tutorial: https://vaadin.com/docs/-/part/framework/tutorial.html
and replace CUSTOMERSERVICE.java (controller) with my controller
OR
would there be a better tutorial that demonstrates remote data connectivity to Vaadin Grid from within an existing JSF application?

Any suggestions greatly appreciated.

RE-WORDING… I mean to ask … HOW to move from JSF to Vaadin.

from JSF to Vaadin

OPPOSITE (Vaadin into JSF) of what I am seeking (JSF migrate to Vaadin) … found a webinar by Matt and Alejandro:
https://vaadin.com/blog/-/blogs/migrating-from-jsp-and-jsf-to-vaadin-made-easy

Is there an update for Vaadin 8?

I have a MODEL, CONTROLLER, DAO with the connection pool defined in the content and web XML files.

I created a vanilla Vaadin SPA with the It Works button. Following the example for Vaadin 8, which runs ok.

I am going to copy my three beans and include them within my vanilla Vaadin SPA.
I assume I would follow: “the most common way to populate a grid”

https://www.voxxed.com/blog/2017/03/21-improvements-vaadin-8/

The Vaadin approach… HOW do I reference the connection pool for my remote data URL, DRIVER, USERNAME, PASSWORD, etc…

Any suggestions greatly appreciated.

Well, Vaadin and JSF are not that different. The connection pool is (usually) defined on the appserver but instead of writing a template with EL pulling in the data, you write the view and stick the data directly to it. If you CDI-enable Vaadin you could @Inject a DAO which has an injected DataSource or PersistenceContext etc or whatever you did in JSF.

Thank you, Nicklas, would you have a Vaadin example, please?

Nicklas Karlsson:
Well, Vaadin and JSF are not that different. The connection pool is (usually) defined on the appserver but instead of writing a template with EL pulling in the data, you write the view and stick the data directly to it. If you CDI-enable Vaadin you could @Inject a DAO which has an injected DataSource or PersistenceContext etc or whatever you did in JSF.

Can We also inject managed-bean in the vaadin flow view?
If yes, how can we then add remove the value of our managed-bean fields?