Announcement

Collapse
No announcement yet.
X
Collapse
  • Page of 1
  • Filter
  • Time
Clear All
new posts
Previous template Next
    #1

    Jasperreport was working perfectly in Smartclient 10.0 but not working in 11.0

    When we are upgrading to Smartclient 11.0p, jasperreport pdf generation is not working which is working completely fine in 10.0p.

    Below are the list of jars used for 10.0 and 11.0 versions.
    ISC10: ISC11:
    barbecue-1.5-beta1.jar barbecue-1.5-beta1.jar
    barcode4j-light.jar barcode4j-light.jar
    commons-beanutils-1.8.3.jar commons-beanutils-1.8.3.jar
    CurrencyFormatter.jar CurrencyFormatter.jar
    groovy-all-1.8.7.jar groovy-all-1.8.7.jar
    isc_activation.jar isc_activation.jar
    isc_ant.jar isc_ant.jar
    isc_asm-3.1.jar isc_asm-5.0.4.jar
    isc_batik-anim.jar isc_batik-anim.jar
    isc_batik-awt-util.jar isc_batik-awt-util.jar
    isc_batik-bridge.jar isc_batik-bridge.jar
    isc_batik-css.jar isc_batik-css.jar
    isc_batik-dom.jar isc_batik-dom.jar
    isc_batik-ext.jar isc_batik-ext.jar
    isc_batik-gvt.jar isc_batik-gvt.jar
    isc_batik-parser.jar isc_batik-parser.jar
    isc_batik-script.jar isc_batik-script.jar
    isc_batik-svg-dom.jar isc_batik-svg-dom.jar
    isc_batik-util.jar isc_batik-util.jar
    isc_batik-xml.jar isc_batik-xml.jar
    isc_commons-cli-1.2.jar isc_commons-cli-1.3.1.jar
    isc_commons-codec-1.6.jar isc_commons-codec-1.10.jar
    isc_commons-collections-3.2.1.jar isc_commons-collections-3.2.2.jar
    isc_commons-dbcp-1.3.jar isc_commons-dbcp-1.3.jar
    isc_commons-digester.jar isc_commons-digester.jar
    isc_commons-fileupload-1.3.1.jar isc_commons-fileupload-1.3.1.jar
    isc_commons-io-2.2.jar isc_commons-io-2.4.jar
    isc_commons-jxpath-1.3.jar isc_commons-jxpath-1.3.jar
    isc_commons-lang-2.6.jar isc_commons-lang-2.6.jar
    isc_commons-pool-1.6.jar isc_commons-pool-1.6.jar
    isc_commons-vfs-1.0.jar isc_commons-vfs2-2.0.jar
    isc_dom4j-1.6.1.jar isc_dom4j-1.6.1.jar
    isc_hibernate-validator-4.1.0.Final.jar isc_hibernate-validator-4.1.0.Final.jar
    isc_hibernate3.jar isc_hibernate3.jar
    isc_httpclient-4.3.5.jar isc_httpclient-4.5.2.jar
    isc_httpcore-4.3.2.jar isc_httpcore-4.4.4.jar
    isc_isc-jakarta-oro-2.0.6.jar isc_isc-jakarta-oro-2.0.6.jar
    isc_isomorphic_assembly.jar isc_isomorphic_assembly.jar
    isc_isomorphic_compression.jar isc_isomorphic_compression.jar
    isc_isomorphic_core_rpc.jar isc_isomorphic_core_rpc.jar
    isc_isomorphic_hibernate.jar isc_isomorphic_hibernate.jar
    isc_isomorphic_js_parser.jar isc_isomorphic_js_parser.jar
    isc_isomorphic_realtime_messaging.jar isc_isomorphic_realtime_messaging.jar
    isc_isomorphic_sql.jar isc_isomorphic_sql.jar
    joda-time-2.2.jar isc_joda-time-2.9.2.jar
    isc_log4j-1.2.17.jar isc_log4j-1.2.17.jar
    isc_mail.jar isc_mail.jar
    isc_poi-3.9-20121203.jar isc_poi-3.14-20160307.jar
    isc_poi-ooxml-3.9-20121203.jar isc_poi-ooxml-3.14-20160307.jar
    isc_poi-ooxml-schemas-3.9-20121203.jar isc_poi-ooxml-schemas-3.14-20160307.jar
    isc_slf4j-api-1.7.7.jar isc_slf4j-api-1.7.12.jar
    isc_validation-api-1.0.0.GA.jar isc_validation-api-1.0.0.GA.jar
    isc_velocity-1.7.jar isc_velocity-1.7.jar
    isc_xercesImpl-2.9.1.jar isc_xercesImpl-2.11.0.jar
    isc_xml-apis-1.3.04.jar isc_xml-apis-1.4.01.jar
    isc_xml-apis-ext.jar isc_xml-apis-ext.jar
    isc_xbean.jar isc_xmlbeans-2.6.0.jar
    isdutility.jar isdutility.jar
    itext-2.1.7.jar itext-2.1.7.jar
    jasperreports-6.2.1.jar jasperreports-6.2.1.jar
    jasperreports-fonts-6.1.1.jar jasperreports-fonts-6.1.1.jar
    jasperreports-functions-6.2.1.jar jasperreports-fonts-moi.jar
    jasperreports-fonts-moi.jar jasperreports-functions-6.2.1.jar
    logback-access-1.0.9.jar logback-access-1.0.9.jar
    logback-classic-1.0.9.jar logback-classic-1.0.9.jar
    logback-core-1.0.9.jar logback-core-1.0.9.jar
    moi_utilities.jar moi_utilities.jar
    slf4j-api-1.7.2.jar
    We are completely clueless as it was working with 10.0 version jars. Please could you help us in resolving this issue.
    Tags: None
    #2
    Not specifically related to changing classpath, but last time I checked the Jasperreports community version is not compatible with a JVM > 7. Beyond that, you'd have to provide error message(s) to debug this or to a guess-check to find conflicting jars.

    Comment

      #3
      Thanks nitroamos for your input.

      There is no specific error occurred. But the generated pdf is not the same as before. There are some fields alignment issue and some fields not printing. Also the pdf generation is going into infinite loop as there is some fields shifted downwards and not fitting into the page size properly to print.

      There is one more change in this smartclient 11.0 upgradation is that jvm argument -Dfile.encoding=UTF-8 setting in IBM WAS server to show arabic data properly. This was not the case in 10.0 version. In 10.0 version, arabic data was showing correctly without this setting.

      In this thread https://forums.smartclient.com/forum...dered-properly
      It is mentioned that where the arabic data is disturbed and why the above mentioned jvm setting required.
      Last edited by sathish.gdis; 18 Sep 2017, 11:17.

      Comment

        #4
        We would advise showing some of the differences you're seeing in the rendering here, in case other users of SmartGWT happen to have encountered the same issue. If you can do that, we will also check if any of our consultants, who may have encountered Jasper Reports on customer projects, happen to have seen the same issue.

        However overall you are probably better off posting on forums related to Jasper Reports.

        Note also, if you don't find other users with the same issue, carefully revisit whether something other than the .jars was changed. We receive reports of changing in behavior on upgrade a lot that turn out to be changes to the environment and/or to data.

        Comment

          #5
          Hi Isomorphic

          One more information is that this problem is occuring only in test/prod environment (mainframe env) not in developement environment (Windows 10 machine).
          This was not the case in smartclient 10.0p version.

          Comment

            #6
            Click image for larger version Name: Test_with_ISC11.jpg Views: 67 Size: 186.4 KB ID: 249283


            Click image for larger version Name: Production_with_ISC10.jpg Views: 71 Size: 167.6 KB ID: 249284

            These files are difference in pdf generation.
            Attached Files

            Comment

              #7
              Hi Isomorphic

              This is an urgent issue which needs to be fixed before smartclient 11.0 rollout to production environment.

              I have given already few more information regarding this issue.

              Comment

                #8
                As we've covered above, this is not an issue with our product, so if you need prioritized support, you should seek out the vendor of Jasper. And we would also recommend using forums that focus on Jasper Reports.

                We did, as promised, send your PDFs around to our consulting team, on the unlikely chance that they've seen a similar issue with Jasper Reports when dependencies were upgraded. So far, no one has seen anything like this before.

                As far as the PDF differences, some of the differences hear appear to be presence/absence of data, and it seems like absence of data could possibly explain differences in alignment as well. We'd strongly encourage you to look at whether the actual problem is that the data being provided to Jasper Reports differs.

                Comment

                Previous template Next
                Working...
                X