Vaadin Migration from 7 to 8

Vaadin 6 / 7 / 8
21

Is there any way to make sure BeanManager is available and instantiated???

Bean manager is setup by the container, e.g. Wildfly, so if it is not there, something has gone wrong earlier in the startup of the app. You may find hints by reading the log.

Also did you remember to add beans.xml https://github.com/TatuLund/cdi-demo/tree/master/src/main/webapp/WEB-INF ?

22

I have followed the below document, added the Default and alternative annotations into more than one classes which are implemented the same interface. Also, added alternative entries in beans.xml file and still getting same error. If an interface implemented in only one class, Should I mark Default annotation for that too? Please advise.
https://vaadin.com/docs/flow/cdi/tutorial-cdi-service-beans.html


<?xml version="1.0" encoding="UTF-8"?>
<beans>
   <alternatives>
      <class>com.aic.aim.preauth.wizard.pages.MedicalDecisionTable</class>
      <class>com.aic.aim.clearcashless.ClearCashlessViewImpl</class>
    
   </alternatives>
</beans>

17874926.log (300 KB)

23

The documentation you linked is for Vaadin 14

The documentation about Vaadin 8 version of CDI add-on is here: https://vaadin.com/docs/v8/framework/advanced/advanced-cdi.html

Normaly you do not need to add anything to beans.xml

24

Okay! Let me check and revert you back.

25

Regarding annotation they have mentioned in Version 8 also.
https://vaadin.com/docs/v8/framework/articles/IIInjectionAndScopes.html

26

As per documentation “The application should not have a servlet extending VaadinServlet, as Vaadin servlet has its own VaadinCDIServlet that is deployed automatically.” https://vaadin.com/docs/v8/framework/advanced/advanced-cdi.html)
Changed VaadinServlet to VaadinCDIServlet and application working fine now.
public class CreateIntServlet extends VaadinCDIServlet {
public class MSServlet extends VaadinCDIServlet {