Config interfaces not implemented yet?

Support
1

So our app makes heavy use of config interfaces, since in CUBA it was highly recommended to do so. According to this CUBA forum Jmix subforum topic - Configuration Interfaces feature jmix details - #3 by albudarov - CUBA.Platform - it’s not implemented yet. In the linked ticket (Application settings stored in database · Issue #56 · jmix-framework/jmix · GitHub) it seems to be planned for the 1.2.0 release? :frowning:

We’ll be unable to even compile until that is done as we use so many of them. Guys, you recommended heavy use of config interfaces in CUBA. Releasing Jmix without the feature was maybe a little premature? :frowning:

Jmix replacements for CUBA Configuration Interfaces and built-in Freemarker functionality?
2

Config interfaces are available in the jmix-cuba compatibility module, so you’ll be able to use them in a migrated application in the same way as you did before.

For new Jmix projects, we are going to implement this feature differently, and this is what the issue is about.

Regards,
Konstantin

3

Odd. I wonder why then I’m getting red lines on all my config interface injections, with the message: “Could not autowire. No beans of type ‘config interface type here’ found.”

4

It’s a false warning from IntelliJ Ultimate, ignore it.

5

What was the ultimate resolution to this? It seems the item was removed from the roadmap.

1 Like
6

It’d be good to get an answer here as this is a capability that any sufficiently large business app will need.

7

The equivalent of CUBA Config Interfaces functionality in Jmix is the Application Settings add-on. Available since v.1.2.

8

Aha. Thank you. The CUBA way feels more natural, so I’ll just continue to use the CUBA-Jmix bridge implementation of the “old way.”