Using Component instead of VerticalLayout removes TextFields

[chufgard]

Description of the bug
Instead of using public CreateTab(CustomerData customerData, ChapterSelection chapterSelection, Download download) { I used public CreateTab(Component customerData, ChapterSelection chapterSelection, Download download) {.

Spring was able to find the import since the parameter name was identical to the bean name automatically generated from the class.

After running mvn install -P production running the application (even local) show a UI without any TextField

Minimal reproducible example

@UIScope
@Route(value = "")
public class CreateTab extends VerticalLayout {

    public CreateTab(Component customerData) {
        //new TextField();
        add(customerData);
    }
}

@UIScope
public class CustomerData extends VerticalLayout {
    
    CustomerData() {
        add(new TextField());
    }
}

Add this two classes to a clean vaadin starter project and remove the default ui elements.

If you do a mvn install -P production the UI is broken. If you enable the TextField in CreateTab it works again.

Expected behavior
A TextField should be rendered even if injected with Component instead of VerticalLayout

• Actual behavior
  TextField is not rendered if injected with Component instead of VerticalLayout

Versions
- Vaadin / Flow version
14.2.5
- Java version
11

https://vaadin.com/forum/thread/18215575/production-mode-breaks-textfield

[caalador]

Should the Vaadin version be 14.1.5?
14.2 series is only out as a prerelease 14.2.0.alpha11 with the beta1 coming soon.

If using 14.1.5 could you update to 14.1.25 to see if the issue still persists.

[musikpirat]

Should the Flow version be 14.1.5?
14.2 series is only out as a prerelease 14.2.0.alpha11 with the beta1 coming soon.

If using 14.1.5 could you update to 14.1.25 to see if the issue still persists.

Sorry for the confusion, 14.2.5 is the Vaadin version (LTS).

[caalador]

I'm also miss typing. Vaadin 14.1.25 is the newest LTS that is out. Vaadin 14.2.0.beta1 is on its way, but not yet out.

[musikpirat]

You're totally right. Of couse I meant 14.1.25.

Martin Israelsen guesed in the forum, that the issue might be related to the optimizer.

[caalador]

How did you get Spring to accept Component in the constructor as it's not a bean?

[musikpirat]

Once again I have to beg for pardon. This is my worst bug report ever...

Of course CustomerData ist annotated with @component. Should have uploaded my test project.

[caalador]

That's fine I got it to replicate as described.

[musikpirat]

Great! Thanks for your patience!

[cdir]

As far as I can see, this problem got worse with Vaadin 24.1. We use injection to make certain parts of the UI configurable by downstream projects. All components that are only referenced in the downstream project are no longer part of the delivered bundle.

We can't use @Uses annotation here because the classes annotated with @Route are already defined in the upstream project. However, the component scan will only find classes that are referenced by a class annotated with @Route.

It would be helpful if we can specify other classes, e.g. at AppShellConfigurator, which are also considered in the Component Scan. Also, since we often work with configuration interfaces that provide methods for the various components used, it would be helpful if the @Uses annotation accepted arbitrary classes and not just classes of type Component.

[Artur-]

You should be able to use

flow/flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildFrontendMojo.java

Lines 92 to 97 in 8ba35da

	/**
	* Whether to use byte code scanner strategy to discover frontend
	* components.
	*/
	@Parameter(defaultValue = "true")
	private boolean optimizeBundle;

to make it include all components it finds on the classpath