1 Reply Latest reply on May 3, 2016 2:51 AM by disabled_morkus

    Issues with java application using driver FM14.0v1_xDBC_14.0.10 to fms v14.4.413

    kiwikaty

      Issue with java sync after migration from fms v13 to fms v14 and v14 xbdc driver: - Application code identical - only change is fms server version and XBDC driver packaging of application.

       

      Data

       

      mailAddress1: 12 Tennis Street

      mailAddress2:

      mailAddress3:

      mailAddress4: Riverside

      mailAddressCity: Wellington

      mailAddressCountry: New Zealand

      mailAddressState:

      mailAddressPostcode: 1234

       

       

      v13 result -  leaves expected nulls in 2 and 3

       

      mailAddress1: 12 Tennis Street

      mailAddress2:

      mailAddress3:

      mailAddress4: Riverside

      mailAddressCity: Wellington

      mailAddressCountry: New Zealand

      mailAddressState:

      mailAddressPostcode: 1234

       

      v14 result - moves 4 into 2!

      mailAddress1: 12 Tennis Street

      mailAddress2: Riverside

      mailAddress3:

      mailAddress4:

      mailAddressCity: Wellington

      mailAddressCountry: New Zealand

      mailAddressState:

      mailAddressPostcode: 1234

       

      Same issue if 1 & 2 & 4 are populated. v13 will leave fields as expected with 3 empty. V14 will move line 4 to line 3!

       

      Only appears to be happening where fields names are the same except for end suffix. E.g "City "does not slide to Address2 if is empty.

       

      Same issue happening for Home, Mail, Work address lines.

       

      Advice with this urgently required.

        • 1. Re: Issues with java application using driver FM14.0v1_xDBC_14.0.10 to fms v14.4.413

          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.

           

          - m