I'm guessing this is a coding issue that now just appears in the current version.
Did you step through your Java code in debug mode to look at the returned ResultSet values? If not, I bet you'll quickly see what's happening.
Are you using ResultSetMetaData to get DB table/field info?
Are you using PreparedStatements or just regular SQL?
Are you using any kind of Java persistence framework?
Are you doing a "flush()" or other data clean-up techniques?
I would also recommend you install "PMD" into your Java IDE. PMD is a (FREE, of course) source code analyzer. it will help you find memory leaks (like resources not properly closed) and many, many other coding issues. We use PMD in all our projects as part of our developer workflow. There's another (FREE, of course) source code analyzer called "FindBugs". Both these tools work in the popular Java IDEs like Eclipse or Intellij.
Once you can confirm your actual Java code is "identical", but your fields are not being correctly populated/saved, I would then report this issue to FM support. Include screenshots of your debugging session, your Java code, a sample FMP project with some data, and information for the FM developers (at the highest possible detail level). If FM can reproduce it, they'll fix it.
However, without you posting your Java code and a representative FMS application, it's impossible to help you debug this here.
HOPE THIS HELPS.