Jump to content
We've recently updated our Privacy Statement, available here ×

gustavofarias

Members
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Everything posted by gustavofarias

  1. Now, there is CVE-2021-45046 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)
  2. CVE-2021-45046CVE-2021-45046: Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack. Severity: Moderate Versions Affected: all versions from 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. Source: https://logging.apache.org/log4j/2.x/security.html
  3. https://logging.apache.org/log4j/2.x/security.html "It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations."
  4. I have this simple report attached and would like to export it to JSON using a schema also attached. Differently from subreports, images, etc I can't reference the json schema with a relative path. Since it is in the same folder of the report I expected to use just "schema.json" as expression to net.sf.jasperreports.export.json.schema . If I use an absolute path like 'C:usersusernamepathtoschema.json' it works fine. This also prevent me from using schemas in Jasper Server.
  5. This is only a generic error message. For people to help you you first need to really know what is the error. So, try to activate the logging for your server, then, read the log and post the error.
  6. there is an "anonymousUser" without password by default. The reports this users can view can be accessed using the api
  7. why do you need table component? You can do what is in the picture just usind column header (yellow part), salmon group, inside it the gray group, and the detail in white.
  8. Won't produce correct answers. above with BigDecimal.ROUND_CEILING -> 3.35 set the number of decimal places to 1 ($V{ RoundUp}.setScale(1,BigDecimal. ROUND_HALF_UP)) -> 3.4 What is asked is not a rounding operation, so using rounding is unlikely produce a correct answer.
  9. Yes, it's possible. In fact that's the point of the whole thing.
  10. vai depender do que tem aqui: $P!{unidadesOrcamentarias}
  11. can you pass the page number as a parameter to the subreport?
  12. The above answer is wrong and you produce the exact same 3.35
  13. This is not rounding, it's another operation. Can't you do it in the expression of the text field or variables?
  14. to update just follow the instructions inside the zip. Basically, unzip the 2 zip files on the correct locations and overwrite the files.
  15. In fact Build version [20210726_1127] is the build version of the service pack, not the server that will receive the patch. Confusing.
  16. I think it's a bug corrected in 7.8.1. Solved in 7.8.1: JS-59254 Always Prompt Input Control Flag not WorkingUpdate: just checked that applying the service pack corrects the problem.
  17. Docs of the pack says: "This Service Pack should be applied to JasperReports Server version [7.8.0]. Build version [20210726_1127]." The version I have is [20200807_1412]. I don't get how I ended up installing this version if there is only one version available for download. By the way, should I upgrade too?
  18. posta uma imagem de como vc quer que fique e do que você está obtendo no momento.
  19. When you publish to JasperServer it probably created a local input parameter that points to an empty list. One of the many elements you can create in jasper server is lists of values. After you create one, change the input parameter of your report to link to the newly created list and you will see values in the "disponibles" tab. In this case, the list will have fixed values. Not sure if that's what you want. If you want a free to type list, change the input parameter to String. Make sure you filter it properly (e.g only numbers and commas are accepted) to avoid hacks an use this in your SQL: and column in ( $P!{singleStringOfCommaSeparatedValues} ) You can create in Server your custom input parameter that you be checked against a regex. You can define it to have the format "param, param, param..."
×
×
  • Create New...