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

Friendly User

Members
 View Profile  See their activity

  • Posts

    435

  • 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 Friendly User

  1. Friendly User
    Pretty much all versions use that, it's an implementation of factory pattern for the JRLib to create objects of class JRBoxContainer.
  2. Friendly User
    The JRBoxFactory is part of JasperReports library, it's located in jasperreports/src/net/sf/jasperreports/engine/xml, to get access to that factory you need to have JR library in your classpath.
  3. Friendly User
    The changelog can be found inside the JasperReports project archive (jasperreports-2.0.4-project.tar.gz) in the file called changes.txt. Also that is a very very very old version, not sure why you would want to use it instead of our latest version.
  4. Friendly User
    Hey! I am not sure what you mean here by dynamic category expression here. Category expressions are by definitions dynamic and will create you a category based on what the expression resolves to. Do you want to have something like $P! for your expression where first the parameter evaluates into some string with code and then that code is used as category expression? That wouldn't be possible, unfortunately, as the $P! syntax only works for queries.
  5. Friendly User
    You need to download the previous version of JR, add a new compiler in Window->Preferences->Jaspersoft Studio -> Compatibility -> Manage JasperReports Versions. Point the dialog to the /dist/ subfolder of the downloaded JR. Then in the properties of the project or single report file set the compiler to use that compiler you've added.
  6. Friendly User
    Download the version of JasperReports that you used to develop that report, go to Window -> Preferences -> Jaspersoft Studio -> Compatibility -> Manage JasperReports Versions, add another compiler of that version. You'll need to point to /dist/ folder of the downloaded JasperReports version. Then create a new project where you're going to run the older reports, click on the properties and in the compatibility window change the compatibility settings and set the project to use the old compiler. This can be also through Right click on report -> properties and changing compatibility settings there for a single report.
  7. Friendly User
    This does sound like a bug, I'd suggest reporting it here: https://community.jaspersoft.com/node/add/bug
  8. Friendly User
    As previous poster indicated, the procedure is invoked using "call <stored_proc_name>(<arguments>)". I'd suggest first to try to simplify the query, remove the parameters and see if that runs successfully for you. Then add the parameter. It seems there is an error here in executing the SQL statement, I am not sure what value you pass with the parameter.
  9. Friendly User
    Hello Shaheed, I don't think it's possible to add JS files to the studio to reuse. You can add JAR's and java classes to the classpath but not javascripts. To make things easier you can define a custom expression in Window -> Preferences -> Jaspersoft Studio -> Editors -> Expression editor. You can then re-use the expression by picking it in User Defined Expressions folder in Expression Editor. This is not code reusability but it could make it easier to work.
  10. Friendly User
    We do not support Oracle Java 1.6 or OpenJDK 1.6 anymore. Oracle doesn't support Java 1.6 either.
  11. Friendly User
    There should be no problems opening the report HTML exports using Chrome, JasperReports generates regular HTML output that is understandable to all browsers. Try to disable Chrome extensions if you have any and check out the F12 developer tools console and network tab for any peculiarities when opening the HTML files.
  12. Friendly User
    Set the permission to report repository object to No Access for the roles and users you don't want running the report.
  13. Friendly User
    You can create groups in the report based on the report element (field, paramater) or expression. You don't need to use the query language for that. You can also create a sort field to sort the data before grouping. To do a totals count, you can create a variable with count calculation and reset type set on group you've created. In JSS to create a group right click on the root report object in the outline and press Create Group.
  14. Friendly User
    Scenario: You are running JasperReports Server 7.1.0 and want to upgrade to 7.1.1 to follow the security advisory. What would be the easiest way to do that? Solution: JRS 7.1.1 doesn't have any changes to the database. All you'll need to do is to re-deploy the new WAR file and make it point to the same database. The easiest way to do that would be the following: Stop your application server and undeploy JRS WAR file. To do that just delete the existing WAR file or better move it to another location until the upgrade is complete. Afterwards delete the original WAR file if successfulIn JRS 7.1.1 buildomatic configure the default_master.properties to point to your application server and database. You need to configure appServerType, appServerDir, dbUsername, dbPassword, dbType, dbHost, dbPort. Configure other properties if needed. Please refer to the installation guide for details on how to configure default_master.properties file (https://community.jaspersoft.com/documentation/tibco-jasperreports-server-installation-guide/v71/installing-war-file-using-js-insta-0)Once everything is configured, go to buildomatic root and execute js-ant deploy-webapp-pro command to deploy the 7.1.1 WAR fileRestart your application serverThis method works for only Tomcat, JBoss, Glassfish. For other web application servers you can do the upgrade-samedb.sh/bat or do a new deployment skipping all the steps required to configure the database. It's already configured for the current instance you're running. If you are upgrading from earlier version than 7.1.0, follow the steps from the 7.1.0 Upgrade Guide but apply them to the downloaded 7.1.1. They would be the same. If you need to port the customizations to the new version, check out this article to see what files were changed in 7.1.1 and apply customizations accordingly: https://community.jaspersoft.com/wiki/changed-web-inf-files-jasperreports-server-711
  15. Friendly User
    Scenario:You're designing ad hoc crosstabs and don't want the users to have an option to click on the aggregated values and get another view with details about that aggregation. Turning this off can be useful when embedding, for example. How to disable this feature? Solution:Disabling drilldown in crosstab can be achieved through minor customization. Follow these steps: Stop Tomcat Go to {JRS WAR}/WEB-INF/jsp/jsTemplates/crosstabDetails.jsp Copy contents of line 122 and 123: <td class="{{-xtabCell.hierarchicalSelectors}} {{- _oddEvenClass}} {{- detailRowIndex}}" id="measureBucketInvalidDrill_{{-xtabCell.rowGroupPathIndex}}_{{-xtabCell.columnGroupPathIndex}}_values"><span class="">{{- xtabCell.cellValue }}</span>[/code]Replace contents of line 125 and 126 with what you copied so they are the same. Save. Clean your compiled JSP cache. For example, in Tomcat go to /tomcat/work/Catalina/ and delete the whole jasperserver-pro folder. Restart
  16. Friendly User
    Scenario:During the usage of JasperReports Server 6.4.0 or earlier you encounter a StackOverflow error in the error logs. The StackOverflow looks to be caused by the JavascriptForwardingServlet. Sample stack trace: [toc]at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1404) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:196) at com.jaspersoft.jasperserver.war.JavascriptForwardingServlet.doGet(JavascriptForwardingServlet.java:47) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1233) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:782) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:43) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1404) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:196) at com.jaspersoft.jasperserver.war.JavascriptForwardingServlet.doGet(JavascriptForwardingServlet.java:47) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1233) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:782) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:43) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1404) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:196) at com.jaspersoft.jasperserver.war.JavascriptForwardingServlet.doGet(JavascriptForwardingServlet.java:47) Solution:If you are a user of Professional edition and cannot do version upgrade, download the latest cumulative hotfix for 6.4.0. If you can do version upgrade then upgrade to version 7.1.1 where this issue is addressed.
  17. Friendly User
    This list of changes has been compiled by comparing the vanilla 7.1.0 WAR and 7.1.1 WAR using a comparison tool. This should be useful for the users upgrading from 7.1.0 to 7.1.1 as a part of security advisory. Below is the list of changes. The + in the beginning means the line was added in 7.1.1, - means it was removed. @@ indicates the line and position where the changes are
  18. Friendly User
    The 401 response here looks to indicate that your user does not have sufficient permissions to execute the request. The organization should not be creatable by the regular ROLE_USER, only ROLE_ADMINISTRATOR and ROLE_SUPERUSER should be allowed to do that, as well as manage users. Have a look at the bean filterInvocationInterceptor in applicationContext-security-web.xml and applicationContext-security-pro-web.xml to see what roles are required to access certain REST endpoints.
  19. Friendly User
    Hello, add Accept: application/repository.file+json or Accept: application/repository.file+xml to your request headers.
  20. Friendly User
    Not really, the report is only executing the main query and subdataser queries, it doesn't communicate with the database afterwards.
  21. Friendly User
    Hello John, this may be a fonts problem. What fonts do you use and do you get the other fields in bold or italic with the same font in resulting PDF?
  22. Friendly User
    Can you post a screenshot and report JRXML that demonstrate the issue?
  23. Friendly User
    UUID is used mostly for the interactive elements like tables and crosstabs to identify the elements for sorting/filtering/etc. It's used in the viewer and on the engine level, I am not sure there is useful API available to interact with elements using UUID.
  24. Friendly User
    Possibly when upgrading you have imported the previous repository archive with previous themes. I'd suggest to drop and recreate the JRS database, do the import minimal step and then when importing the repository archive add --skip-themes As for the user, we'd need more details. Did you have encryption turned on in the previous version? Do you get any error messages in browser console or jasperserver.log files?
  25. Friendly User
    You should be using a parameter here, Fields are objects coming from the data source, Paramters are objects defined before the report query is executed and their value is an expression or custom input. In this case Parameter makes most sense
×
×
  • Create New...

© 2024 Cloud Software Group,
Inc. All rights reserved.

Products

Explore