Jmix 2.5 release candidate

Announcements
1

Hi everyone,

We are happy to announce that the release candidate of Jmix v.2.5 is published in our artifact repositories! To try out the RC, please restart your IDE and select “Show unstable versions” when creating or upgrading a project.

Jmix Studio 2.5 can be downloaded from the nightly channel.

For more information on the new features, improvements, and upgrade instructions, please refer to the release notes. The documentation for this release is currently incomplete, but we are actively working on it.

We would greatly appreciate your feedback on the RC. If you encounter any issues, please let us know.

The final release 2.5 is expected by the end of February.

4 Likes
3

Clean and Re-Import Gradle Project did solve the problem, sorry.

4

Hi everyone

image

If I want to logout, nothing happens.

I have to close the Browser Window and see the following messages in the console


2025-02-11T16:06:59.603+01:00 DEBUG 15764 --- [nio-8080-exec-9] o.a.websocket.DefaultWebSocketProcessor  : Delaying closing operation for firefox and resource c4690720-7e9e-45ef-97a9-f25c1b77aa1c
2025-02-11T16:06:59.603+01:00 DEBUG 15764 --- [nio-8080-exec-4] o.a.websocket.DefaultWebSocketProcessor  : Delaying closing operation for firefox and resource 266ee828-b1a8-45c1-bef3-54e0d327ffb6

But the application is still running …

It seems everything is started twice ?

2025-02-11T16:05:22.279+01:00 DEBUG 15764 --- [           main] io.jmix.core.impl.JmixMessageSource      : Loading properties [messages_en.properties] with encoding 'UTF-8'
2025-02-11T16:05:22.279+01:00  INFO 15764 --- [           main] ag.myself.crm.CRMApplication             : Started CRMApplication in 16.296 seconds (process running for 16.675)
2025-02-11T16:05:22.284+01:00  INFO 15764 --- [           main] ag.myself.crm.CRMApplication             : Application started at http://localhost:8080
2025-02-11T16:05:22.284+01:00  INFO 15764 --- [           main] c.v.b.d.DevModeHandlerManagerImpl        : Application running at http://localhost:8080/
2025-02-11T16:05:23.297+01:00  INFO 15764 --- [nio-8080-exec-3] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2025-02-11T16:05:23.297+01:00  INFO 15764 --- [nio-8080-exec-3] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2025-02-11T16:05:23.297+01:00  INFO 15764 --- [nio-8080-exec-3] o.s.web.servlet.DispatcherServlet        : Completed initialization in 0 ms
2025-02-11T16:05:23.329+01:00  INFO 15764 --- [nio-8080-exec-3] i.j.core.impl.FetchPlanRepositoryImpl    : Initializing fetch plans

Do you need some more information ?

Best regards

Felix

6

Hi,

Unfortunately, I cannot reproduce the issue. I have successfully logged out on all browsers.

Regards,
Gleb

7

Thank you for your try.

I see, that I do not have the standard loginview and will investigate further.

Regards

Felix

8

When a potential new customer is trying JMix with MariaDB he will just fail.

To find the solution for this error and after downgrading to an older liquibase AND deleting the wrong database, you need a lot of experience.

I understand, that this error should be solved with JMix 2.5 but don’t see it in the 2.5 RC1 ?

Regards

Felix

1 Like
9

This issue is planned for Jmix 2.5.x, but not for 2.5.0.

10 
  <script type="text/javascript">
    jmixBeforeUnloadListener = (event) => {
      event.preventDefault();
      return (event.returnValue = "");
    };
  </script>

Was missing in the index.html … see other thread

11

Hi @gorelov

Error creating UUID from database value when trying log in application (mariaDB)

It seems, this is still not solved. When will this happen ?

Regards

Felix

12

Hi,

Currently, it’s planned as a possible candidate for one of the 2.6 bug fix releases. Like and comment help to prioritize issues :wink:

Regards,
Gleb

1 Like
13

Hi @gorelov

I do not understand, why this simple bug is not fixed long time ago as promised !!

EVERY new client who wants to use Jmix with MariaDB will just FAIL !

Regards

Felix

14

Hi Felix, copy here the answer for community:
The workaround is described in the documentation and the update is expected in October release.

image
image720×304 51.4 KB

1 Like
15

Looks like this essential update did not happen in 2.7 ?

16

It did, see Error creating UUID from database value when trying log in application (mariaDB) · Issue #3888 · jmix-framework/jmix · GitHub
In the next feature release we’ll change the solution: MariaDB: use char(36) in Liquibase scripts instead of uuid · Issue #4838 · jmix-framework/jmix · GitHub