Our application has a feature to create Workorder to update the devices. As part of our spring jars uplift, we uplift spring framework jars to v6.1.8, spring boot jars to v3.3.0 and spring data jpa/commons jars to v3.3.0. Now when we tried with only the uplift of spring framework + spring boot our feature didn’t break but as soon as we uplifted data-jpa/commons jar we went into this issue.

Caused by: java.lang.NoSuchMethodError: 'void com.org.application.server.services.workorder.database.dao.OfflineConfigWorkOrder._persistence_checkFetchedForSet(java.lang.String)'
    at com.org.application.server.services.workorder.database.dao.OfflineConfigWorkOrder._persistence_set_ocConfigId(OfflineConfigWorkOrder.java) ~

This issue came when we specifically uplifted spring data-jpa/commons jars.. We didn’t see this issue before with the previous version of spring jars

One thing to note here is that when I turned off weaving in our properties file then the issue got fixed even with the latest version of data-jpa jars… So I wanted to know whether setting weaving to false is the right way to move forward or is there any fix that we can do while weaving is set to true…

PS – we are using apache ant to built our project and moving from it currently is not possible and we tried the uplift with both eclipselink version 4.0.2 and 4.0.3