Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
Hi, is there any performance paper available comparing Vaadin 8 and 14? I remember reading few words there and there for Vaadin 10+ but I would love an official paper.
Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
I have not been able to resolve it, I finally gave up and have tried copying my files over into a new 14 starter app to see if that works. But, considering that the only starter project that works on my machine is the spring app and we don’t use spring for our application it’s kind of a pointless effort.
yes, after multiple tries and no chances to get it run, also the startup-app with run:jetty where problems appears with missing js, i fall back to vaadin 13. that runs with no probs
Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
I have not been able to resolve it, I finally gave up and have tried copying my files over into a new 14 starter app to see if that works. But, considering that the only starter project that works on my machine is the spring app and we don’t use spring for our application it’s kind of a pointless effort.
Yes, I already checked that one but it is a migration of 8 to 10.
Is Mirgration of 8 to 10 and 8 to 14 similar ?
Actually I want to use MPR methodology for my project. Currently i am using vaadin 8 with spring boot in my project.
and I want to also use spring in vaadin 14.
Yes, I already checked that one but it is a migration of 8 to 10.
Is Mirgration of 8 to 10 and 8 to 14 similar ?
Actually I want to use MPR methodology for my project. Currently i am using vaadin 8 with spring boot in my project.
and I want to also use spring in vaadin 14.
The guide has been revised for V14. The document is for some reason named *v8-v10.html
Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
I have not been able to resolve it, I finally gave up and have tried copying my files over into a new 14 starter app to see if that works. But, considering that the only starter project that works on my machine is the spring app and we don’t use spring for our application it’s kind of a pointless effort.
I updated the vaadin version and copied the maven front end plugin in formation into my pom. I also added and removed the compatibility portion at various times. The rest of the guide does not apply to this application.
Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
I have not been able to resolve it, I finally gave up and have tried copying my files over into a new 14 starter app to see if that works. But, considering that the only starter project that works on my machine is the spring app and we don’t use spring for our application it’s kind of a pointless effort.
I updated the vaadin version and copied the maven front end plugin in formation into my pom. I also added and removed the compatibility portion at various times. The rest of the guide does not apply to this application.
Sabas Gonzales:
I am also receiving the same errors as above in addition to the following:
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) ERROR in …/target/frontend/generated-flow-imports.js
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) Module not found: Error: Can’t resolve ‘@vaadin/flow-frontend/comboBoxConnector-es6.js’ in ‘C:\code\tcifv14\target\frontend’
2019-08-15 14:54:42,007 ERROR [dev-webpack]
(webpack) @ …/target/frontend/generated-flow-imports.js 28:0-56
I have tried cleaning, rebuilding, installing globally to no effect
I am facing the same problem. How we can resolve the issue?
I have not been able to resolve it, I finally gave up and have tried copying my files over into a new 14 starter app to see if that works. But, considering that the only starter project that works on my machine is the spring app and we don’t use spring for our application it’s kind of a pointless effort.
I updated the vaadin version and copied the maven front end plugin in formation into my pom. I also added and removed the compatibility portion at various times. The rest of the guide does not apply to this application.
Yes, I already checked that one but it is a migration of 8 to 10.
Is Mirgration of 8 to 10 and 8 to 14 similar ?
Actually I want to use MPR methodology for my project. Currently i am using vaadin 8 with spring boot in my project.
and I want to also use spring in vaadin 14.
The guide has been revised for V14. The document is for some reason named *v8-v10.html
I created the demo of vaadin 8 and did the migration of vaadin 8 to 14 (Without using Vaadin Spring) and it’s work.
But I created my original project in spring boot where i am using vaadin spring. Here, there are lot of dependency issues if i changed the version to vaadin 14 than my vaadin spring version will also change and i also want to run the application as MPR.
So i need vaadin spring for version 8 and version 14.
and I also try to keep only the vaadin-spring version 2 (For vaadin 8) to run the application but in this case my vaadin8 code is not working but for vaadin 14 code is working.
For anyone having the same weird module not found issue with webpack, try adding the build-front goal in addition to prepare-frontend to your pom.xml (not just in your production goal section). According to my manager there was an older version of the migration/ugprade guide that had that line included and once he added that line it fixed the issue I was having.
It’s really nice to hear that Vaadin 14 is out. But it is not understandable why The Book of Vaadin 14 is unavailable for those people using email addresses from web.de, gmx.net, gmail.com, outlook.de and maybe many more.
I started using Vaadin 14 with excitement about 2 weeks ago for a web platform project. I have successfully created an app using AppLayout, multi lingual that currently allows for a self service account sign up and sign in process that runs well on my development machine using localhost:8080 with Spring Boot.
However, despite reading the materials and following instructions, I am unable to successfully deploy my app as a War file to a Tomcat 9 server I have just built on a cloud service.
Can someone try the following and tell me the correct steps for a successful outcome:
Create a project using the Vaadim 14 Starter new project in Eclipse.
Verify it works on your local machine.
Build and deploy to a separate web server
Successfully run it on the server
Report back the actual steps that made it successful.
I will then compare to what I was doing and adjust (even rebuild) my app.
Note: I have read book of vaadin 14 on deployment. I have also read the Spring boot deployment instructions. I have been stumbling with old vaadin 8 documentations and questions, so I am trying to work with a pristine vaadin 14 only method.
The issues I have been hitting on the server side vary depending on what I try to fix in eclipse:
Vaadin jars not deployed. Fixed by a “Quick Fix” on a classpath issue in eclipse.
Server says MainView. does not exist: Solved by removing the parameter in MainView constructor.
Server says that my app is not a Servlet; I am using @WebServlet annotation on the MainView class that extends a VerticalLayout. So , I created a new class just to be the @WebServlet extending VaadinServlet and instanciating MainView.
I am still not succeeding after 2 days of this. I am hoping to get feedback on a end-to-end test using the Vaadin starter project.
