Vaadin Bot
Vaadin Bot
**Originally by @peterl1084** --- Creating CDI based error view provider is currently quite difficult and involves hacks and copy pasting code. There should be an abstraction that can be extended...
**Originally by @Legioth** --- As discussed in #19975, there are some cases where there isn't an 1-to-1 mapping between `@SessionScoped` and the lifecycle of `VaadinSession`. For his reason, it would...
**Originally by _nahkh_** --- When implementing a more complicated view management system (in our case based on an xml file describing the view structure), it would be beneficial if we...
**Originally by _hreise_** --- In `JaasAccessControl.getCurrentRequest()` the current request is being logged with INFO-Level.\ This method is called several times when switching the view.\ IMHO even DEBUG-Level would be too...
**Originally by @Artur-** --- From https://github.com/vaadin/cdi/issues/5 Vaadin components are already bundles. Weld was ported to OSGi also. so to be able to use vaadin plus cdi in a OSGi environment...
**Originally by @Legioth** --- When using CDI, there is no trivial way of configuring the servlet to e.g. change the `productionMode` setting. It might be desirable to configure this using...
**Originally by @hesara** --- The CDI add-on tests should be organized in packages by deployment (+some common UI/view/bean classes) and should reuse code and use utility where possible rather than...
**Originally by @hesara** --- A @NormalScope (like the current @UIScoped and @ViewScoped) results in the creation of a proxy class by the CDI implementation. This is not possible e.g. when...
**Originally by @hesara** --- Arquillian tests for the CDI add-on should be run with the most common free JEE servers, not only with TomEE. --- Imported from https://dev.vaadin.com/ issue #14718
**Originally by @Artur-** --- --- Imported from https://dev.vaadin.com/ issue #11504