JPQL Filter ignores the value component for the custom condition case

[KremnevDmitry]

Environment

Jmix version: 1.5.4, 2.1.1 (#2662)
Jmix Studio plugin version: 2.1.1-233
IntelliJ version: IntelliJ IDEA 2023.3 (Ultimate Edition)

Bug Description

See: https://forum.jmix.io/t/jpqlfilter-custom-filter-field/4157
For some reason, the JPQL filter in the custom condition of the Filter component ignores the custom component.

Steps To Reproduce

1. Run the attached project
2. Open the PetBrowser screen
3. Open the tab with the filter component
4. Add both custom conditions for the filter

Current Behavior

The property filter has options:

The jpql filterhas no options:

Expected Behavior

Both filters have the same set of options.

Sample Project

jmix-petclinic.zip

[KremnevDmitry]

Using valueComponents as they are is impossible for filter conditions and configurations.
This is a consequence of the fact that valueComponents are stored in the entity [FilterValueComponent] for conversion into the model representation of the filter.
See: io.jmix.ui.component.propertyfilter.PropertyFilterConverter#convertValueComponentToComponent

Thus, a valueComponent can only be described by a limited set of properties (componentName and styleName).

Incorrect loading of options was due to an incorrect component generation strategy for the JpqlFilter, fixed in #2516

Closed.