Jmix 1.3 released

Hi @mortoza_khan ,

The non-UI layer like entities will be completely untouched when you switch the UI technology.

So the Entities, all business logic and all UI code that does not depend on Jmix UI code will work without any changes.

The actual effort for a migration to the new UI layer will be during porting over all your UI logic.

You can generate new FlowUI screens for entities, but all the controller logic you put on your old UI controllers will be lost in any case.

So if you have a big code base with a lot of UI logic, it might make sense to try to introduce own abstractions, or simply pull out as much possible logic outside your controllers into dedicated beans and avoid a lot of compile time dependencies in those beans to Jmix UI code. With that you have prepared a lot and decoupled quite a bit of UI code from the old Vaadin UI.

If you have a small code base in terms of customizations, then regenerating and replicating functionality might be the faster way to go.

In both cases having a good automated test suite in place will help you. If you went the UI integration test route, you will need a lot of adjustments to the tests (depending on how much abstractions you put into your test suite).

For selenium based E2E tests it might be less, but since the DOM elements also changed there will also be changes needed.


Hi Mario
This is what i was referring to. Since we have to create as a new project when we want to use FlowUI, how can we migrate the Entities? Copy it to the new project? I didn’t see the Entities are compatible as is.

Hi Gleb
I have added the Reports ad Application Settings add-on to this application from the Market place but it is not added to the menu. Thanks for giving hints on how we can add it to the menu.

I’m not sure if there will be any support from the studio plugin, probably other can tell you more about such plans.

Practically speaking you can just create a new blank project with flow UI with the same root package name, project ID etc. and then open up both projects in IDEA.

Then you can simply do a single copy and paste of the whole project tree without the UI controllers and then generate the UIs one by one and do the migration.

Alternatively you can copy your whole project, and manually add the dependencies to the flow UI. Then Studio will also recognize the new UI module and you can go ahead and generate the new screens - or simply change the dependencies in place directly.


Hi Mario
I tried to copy, but It didn’t work. Looks like the Entity definition is a bit different that needs some kind of conversion. That’s why I was asking if there will be studio support to do that. Otherwise, whole things need to be recreated. For example, I already have started to recreate a small project that I originally started in the previous version. However, I have a large project (Entity > 1000) for which some automation in the studio will greatly help.

Looking forward to the comments from the JMIX team.

It is working for me. Just copied entities from old project in jmix (not cuba) and changed the abc in

Manually anything is possible. Question is, which one is optimal! My project is a very large one!!

For me it worked when I tried it for the Petclinic example project quite well. Nothing needs to be changed in the entity definition. I simply copy & pasted the entities and generate new CRUD screens and this was about it (of course in a real world scenario it would also require i18n messages, liquibase migration scripts and more).

Here you can see how I did it: Jmix Flow UI Migration - Petclinic Entities - YouTube

It is also independent of how much entities you have in you application, since the copy & paste operation will be a one-time effort anyways. Simply select all of them and copy them over.

I think there is no need to have any kind of support for this particular operation from the plugin side, since copying over the entities is definitively the smallest effort of the migration.

The effort of creating a 1-to-1 replication of the UI functionality for each UI screen will probably be a 100x effort compared to copying over those classes.

So if there should be any migration support, then it would probably is this area. But I would assume that is quite a heavy lifting, as it would require to transform arbitrary UI Java code (+XML) programmatically through the plugin, which is closer to rocket science than to a CRUD generator.

At the end I think there is no magic bullet here. Vaadin 23 is a different UI framework compared to Vaadin 8. If you want to switch to this new UI technology there will be manual migration effort involved. This migration effort might be less compared to e.g. switching from Vaadin 8 to React, but it still will be a non-trivial effort when the UI makes up a big part of your application.

I personally would not count on any kind of tool to do such a transformation automagically as it is just that: a tool. Of course such effort is painful and brings less business value compared to the next business feature, but probably this is just an amount of work that you simply have to book under “infrastructure maintenance work” that every custom software development effort has in particular if it is about software that is supposed to still exists in 3, 5 or 10 years.

1 Like

Thank you Mario.

I’m playing around with the Flow UI in Jmix 1.3, and it makes me really excited about Jmix 1.5! :grin:

I building a proof-of-concept to migrate an application from a niche legacy technology, and I needed to wait for Jmix to make a decision on the future UI platform. Now I can start developing and expect that in a year, it will have the features I need.

I’m looking forward to:

  • tab sheet!
  • entity suggestion fields
  • data grid pagination
  • documentation on custom Flow UI components (I want to build a SurveyJS component)
  • documentation/examples for theming (not working as I expected)

Planned for Jmix 1.5 (February 2023)

Work in progress: Implement the Pagination UI component · Issue #941 · jmix-framework/jmix · GitHub, should be included in Jmix 1.4 (October).

We strive to be as close to stock Vaadin as possible, so integration of thirdparty components and theming should be easy and as described in Vaadin docs.
Of course, integration of components into XML layout and data binding is a specific thing, but apart form that you can take any Vaadin component and use it in view controllers as is, without any wrappers, etc.