Jump to content
Changes to the Jaspersoft community edition download ×

Massimo Rabbi

Jaspersoft Staff
  • Posts

    613
  • Joined

  • Last visited

  • Days Won

    1

Massimo Rabbi last won the day on December 4 2023

Massimo Rabbi had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Massimo Rabbi's Achievements

  1. Did you give it a try to my information above? Regards, Massimo.
  2. Hi, another more clean solution is to force the following JR property in the Jaspersoft Studio preferences. This will allow you to use the old POI data source and be able to create the report as usual without triggering the exception. net.sf.jasperreports.xlsx.data.source.factory = net.sf.jasperreports.engine.data.ExcelDataSourceFactory See the attached image as well. Best regards, Massimo.
  3. Hi, at the moment we are not providing a dedicated build for Apple Silicon processors. Please refer to the following Github issue: https://github.com/TIBCOSoftware/jaspersoft-studio-ce/issues/56 Best regards, Massimo.
  4. Hi, the problem you are verifying it's actually a bug in the latest version 6.20.6 where the new FastExcel library was added, besides the "standard" POI. A fix will be available in the next release. Since the exception is triggered during the "read fields" operation, you might need to create the initial report using another DA, for example the "empty" one. Later add manually the fields in the report with the same names of the columns you added manually or automatically read in the Excel data adapter. This workaround should allow you to use the XLS DA to run the report preview. Best regards, Massimo.
  5. Hi, the last version of Jaspersoft Studio 6.20.6 is bundling Temurin JRE 17.0.8.1+1. The projects use Java 11 as default since we stick to this version as minimum requirement. You can try to modify it, in order to use Java 17 in your project. Adding/removing new JRE/JDK from the Eclipse preferences requires you to start Jaspersoft Studio application with a JDK instead of a JRE. So you should first download it (i.e. from the Adoptium website) and properly configure the -vm flag in the .ini configuration file. Regarding the Jaspersoft Studio installation for the M1 (or other Silicon processors) there is already a bug related to it: https://github.com/TIBCOSoftware/jaspersoft-studio-ce/issues/56 Unfortunately I don't have a machine where I can properly work and test a possible dedicated build for such kind of Mac flavor. I'll advise you to follow the GITHUB entry in order to be updated on the topic. If you are facing any issue please proceed in opening a dedicated bug on the tracker. Lastly for people using Jaspersoft Studio plugin in different Eclipse flavors it helps give a look at the following article I wrote: In general for people using the plug-in it is a good idea to give a look at the .ini configuration file of the Jaspersoft Studio stand-alone product. From time to time there could be different flags/properties used in order to properly make the product work. With the plug-in, there are too many different possible configurations out there and a user might need to proper customize the startup entries in order to fit its needs. Best regards, Massimo.
  6. Hi can you please verify after following the instructions written in this troubleshooting article I wrote some time ago: Let me know if this helps solving the issue. Thanks. Best regards, Massimo.
  7. Hi, as Thomas said you should try to leverage the "font extensions" JasperReports mechanism in order to properly use fonts sizing / alignment. That said, the output of a command like "uname -a" (or similar) does not help in understanding which Linux flavour you are using (i.e Debian, Mint, Ubuntu etc). There is no indication if you are using a Jaspersoft Studio standalone product or a plug-in version with a specific Eclipse version. The 6.20 numbering is generic, please specify the correct one including the minor qualifier. Also no indication of the currently installed version of JasperReports Server (where the report gets deployed) is present. Regards, Massimo.
  8. ProblemDifferent users mentioned strange behaviors of the Jaspersoft Studio plug-in when installed on the most recent flavors of Eclipse. One example is the disappearing of the JasperReports connections from the Repository Explorer view after a restart. See the following [#14496] - Server connection not saving. SolutionConsidering that the RCP version is a standalone version where we can customize a more "strict" environment, we can not provide the same level of "customization" also in the plug-in version one. Each Eclipse flavor (ie. Java Developers, J2EE Developers etc.) comes with a different set of bundles pre-installed that might clash with Studio ones or not work properly. The probability that something can wrong is higher when the user Eclipse installation has also other additional bundles. Lastly, also which JRE/JDK is used to kick Eclipse can represent an additional variable to the final environment. For this reason is always a good idea to give a look at the Jaspersoft Studio product file, in particular the section dedicated to the VM args. Since Jaspersoft Studio 6.20.1 we moved to Java 11 as minimum required environment for all our plug-ins, before it was Java 8. Plus after shipping for some releases a bundled Java 11 JRE, we moved in the latest 6.20.6 to a Java 17 version. Therefore we highly advice to properly modify you "eclipse.ini" file with a proper set of options. In the above mentioned issue, this means for example adding some instructions like: --add-exports=java.xml/com.sun.org.apache.xml.internal.serialize=ALL-UNNAMED--add-opens=java.desktop/sun.java2d=ALL-UNNAMED--add-opens=java.base/java.io=ALL-UNNAMED--add-opens=java.base/java.lang=ALL-UNNAMED[/code]This will helps solve the server connection(s) disappear, plus some other possible related runtime/startup issues.
  9. Not sure which video you watched. There is no automatic field read in the JSON Data Adapter dialog. In order to have the tree-like representation of the JSON file you should open the Dataset&Query dialog (i.e. button on the report top toolbar). You probably saw the "automatic fields" read operation during the "New Report Wizard" steps. But here you are showing the data adapter editor. Regards, Massimo.
  10. Please re-check the field name attribute. For example the one at line 9 of the JRXML is empty. Not sure how it happened. Also the field name at line 8 seems not a proper one. Regards, Massimo.
  11. ScenarioIn order to be able to properly use the "Manage JasperReports Versions" dialog in Jaspersoft Studio, you might need to download a specific version of the JasperReports Library together with its dependencies. Even though for some old versions it's possible to use the content of a big file like jasperreports-X.Y.Z-project.zip, the latest JR versions no longer contain the dependencies files. Therefore you will need to download them on your own. SolutionYou can create a proper temporary folder where to store your desidered version. In that folder you can download the different JR jars published (fonts, customizer, etc.) besides the main one. More important it is to grab the pom.xml for the library. You can grab it online from different places like MVNRepository or Repo Maven. Once done you can from terminal give the following command (example with version 6.17.0): mvn dependency:copy-dependencies -DoutputDirectory=. -f jasperreports-6.17.0.pom[/code]This way you will have all dependencies in the current folder. Please be sure to have your Maven settings properly configured to grab artifacts from something like Jaspersoft JFrog. Otherwise you might not be able to download "special" jar like the itext related one etc.
  12. Hi, even if you are using a very old version of Jaspersoft Studio Professional (I see 7.1.0), you might be able to drop the license file inside the installation root folder of JSS, renaming it to "TIBCOJaspersoft-JSS.license" or "jasperreports.license". I suppose the error message you are getting is coming from the License Manager itself, accessible through the dedicated menu item under Help. Try to clean-up your system/installation from previous tries (i.e if you dropped somewhere the license file). You might want also to double check, via JSS Preferences, what is the value of the property com.jaspersoft.jasperreports.license.location once you start JSS or after you have tried to setup the license. If the problem persists you need to reach out support. They will double check you have a correct license and maybe open a dedicated ticket for the problem. From what you reported it seems to be a configuration issue. Maybe something got screwed up. Regards, Massimo.
  13. Hi, you might want to use the Barcode4J Type EAN13. Entering a code expression like so will work fine: "9783468111242+56789". Regards, Massimo.
  14. Introduction If you tried to install Jaspersoft Studio inside one of the more recent Eclipse flavours (i.e. IDE for Java Developers), starting from 2020-12 (4.18), you might be experiencing problems using the JasperReports Server plug-in. For example while testing the JRS connection you might see the following error: See the attached exception log for more details. The source of problems is the presence of different bundles related to packages javax.xml.bind.* / com.sun.xml.bind.*. WorkaroundIn Jaspersoft Studio when we create the target platform for the product we start from the Eclipse SDK version adding the needed bundles to make everything work fine. Therefore, after the transition to Java 11 support, we are shipping among the others, the two mandatory bundles jaxb-api (javax.xml.bind.jaxb-api) and com.sun.xml.bind.jaxb-osgi. Apparently starting from the version 4.18, Eclipse in the different pre-packaged flavors (not the SDK one) is shipping these files: com.sun.xml.bind_2.3.3.v20201118-1818.jarjavax.xml.bind_2.2.0.v201105210648.jarcom.sun.xml.bind_2.2.0.v20201118-1845.jarjakarta.xml.bind_2.3.3.v20201118-1818.jarThe quick and dirty solution is then two rename those bundles above, changing their extension to something different from .jar. These will lead to use the Jaspersoft Studio shipped bundles below: com.sun.xml.bind.jaxb-osgi_2.4.0.b180830_0438.jarjaxb-api_2.4.0.b1808300359.jarThis way you should be able to have the JRS plugin working again. Additional note: if this operation creates issues with other plugins you have already added to your Eclipse installation, the advice is to rely on the Jaspersoft Studio stand-alone version for your report creations and executions. sampleerrorlog.txt
  15. Apparently the uploaded DMG was not signed. Try to re-download it. Thanks.
×
×
  • Create New...