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

phchrist

Members
  • Posts

    9
  • Joined

  • Last visited

phchrist's Achievements

Apprentice

Apprentice (3/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Issue:[toc on_off::hide=1] When my computer became unresponsive I did a "hard reset". After rebooting, and trying to restart iReport Designer, I received the following stack trace: ================================================================== java.lang.NullPointerException at org.openide.util.Exceptions.attachLocalizedMessage(Exceptions.java:111) at org.netbeans.core.windows.PersistenceHandler.load(PersistenceHandler.java:121) at org.netbeans.core.windows.WindowSystemImpl.load(WindowSystemImpl.java:69) catch at org.netbeans.core.NonGui$2.run(NonGui.java:178) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) ================================================================================ Resolution:iReport Designer stores various information in files in the directory .ireportpro. If iReport does not exit in a "clean" way some of these files may be left in a bad state that can create issues at subsequent attempts to start iReport Designer. Removing the directory .ireportpro resolved the problem. On Windows the .ireportpro directory can be found here: C:UsersAppDataRoaming.ireportpro Ref. Case #00024771 -- 22:16, 29 February 2012 (UTC)
  2. Issue:[toc on_off::hide=1]Properties such as net.sf.jasperreports.export.parameters.override.report.hints can be set in several places (jasperreports.properties, jasperserver.properties, ...). If the same property is set in more than one place which one "wins"? Resolution:The reference http://jasperreports.sourceforge.net/config.reference.html provides information about each settings property. The priority of settings is: Report > applicationContext.xml > jasperreports.properties > jasperserver.properties. This means that if a property is set in the .jrxml file of a report then that setting "wins". Best practice would be to keep all the global report properties in the jasperreports.properties file and leave jasperserver.properties and applicationContext.xml as is. Ref. Case #00021218 -- 17:34, 29 December 2011 (UTC)
  3. Issue:When I export to PDF or Word a background image does display. How can we make this work for the web view? Resolution:[toc on_off::hide=1] The image element placed in the background section of a JRXML template does not come through in HTML because the HTML exporter is a grid exporter and overlapping elements do not work in those exporters. Ref. Case #00020298 -- 23:19, 28 December 2011 (UTC)
  4. Issue:If you have multiple JasperServer instances running on the same server each instance may be sharing the same cache files. This can cause unpredictable behavior. The caches will normally on Windows be here: c:UsersAppDataLocalTemp[/code]in the folders 'ehcache' and 'ehcache-hibernate'. Resolution:The caches can be made non-persistent by editing the two xml files listed below. It is unlikely that there will be a noticeable performance impact by making these changes. Edit .../WEB-INF/ehcache.xml and .../WEB-INF/classes/ehcache-hibernate.xml and change all diskPersistent attributes to false. There is one out of three in ehcache that is currently set to true while both are set to true in ehcache-hibernate.xml. Ref. Case #00022642 -- 21:47, 28 December 2011 (UTC)
  5. Issue:[toc on_off::hide=1] I have a report deployed to JasperReports Server v4.2.0. I have set the mode to be Transparent. When I invoke it via HTTP API and embed it in an iframe. I am using the viewAsDashboardFrame=true parameter to get only the report HTML. I want the background of the report to be transparent. But there is a div tag (with the reportContainer div), which sets the background color to white. <div style="background-color: #FFFFFF;position:relative;width:812px;height:595px;">[/code]How / where can I configure this to be transparent and not white? Resolution:The property net.sf.jasperreports.export.html.white.page.background should be set to false. Ref. Case #00023010 -- 21:25, 28 December 2011 (UTC)
  6. The Thin Sampe Theme is described here: http://jasperforge.org/plugins/mwiki/index.php/Jaspersoftthemes Using that theme when you under Manage->Users in JasperReports Server display the properties of a user then the “Edit”, “Login as User” and “Delete User” buttons (which are available in the default theme) are not being displayed. These buttons in the default theme appear in the lower righ-hand frame. I am attaching two pictures showing the view with the default theme and the Thin Samle Theme.
  7. Issue:[toc on_off::hide=1] I want to display a report via HTTP API but do not want all the navigational items. What do I have to add to a URL like the following: ...flow.html?_flowId=viewReportFlow&reportUnit=/organizations/MyCompany/temp/testReport Resolution:Add &viewAsDashboardFrame=true or &decorate=no to the end of the URL. The first option simply displays the report in a frame while the second displays the report along with the option to export it into the usual formats such as PDF or Excel. Ref. Case #00022486 -- 23:57, 21 November 2011 (UTC)
  8. Customers sometimes want to customize the look and feel of the JasperReports Server interface by performing customizations as described in the JasperReports Server Ultimate Guide 4.2. In this guide there is information about how to remove the normal copyright notice (Copyright © 2000-2011 Jaspersoft Corporation). It is fairly easy to perform this removal. However, one thing to keep in mind is that most customer contracts with the Jaspersoft Corporation include the following wording: Customers wanting to remove the standard copyright notice should therefore read their contract and if they see the above clause (or similar wording) make sure that "Powered by Jaspersoft" appear on distributed reports or the report portal.
  9. [toc on_off::hide=1] Some customers want to limit the ability to create dashboards in JasperReports Server to users with an assigned role of ROLE_ADMINISTRATOR. Here is a description of how to accomplish that: The file actionModel-navigation.xml which in Windows normally can be found in a directory such as C:Program Filesjasperreports-server-4.0apache-tomcatwebappsjasperserver-proWEB-INF contains this XML near the end of the file: <!-- jasperserver designer pro only --> <context name="main_create_mutton" test="isProVersion"> <selectAction labelKey="NAV_005_CREATE"> <option labelKey="NAV_051_ADHOC_REPORT" action="primaryNavModule.navigationOption" actionArgs="designer"/> <option labelKey="NAV_050_DASHBOARD" action="primaryNavModule.navigationOption" actionArgs="dashboard"/> <condition test="checkAuthenticationRoles" testArgs="ROLE_ADMINISTRATOR"> <option labelKey="NAV_056_DOMAIN" action="primaryNavModule.navigationOption" actionArgs="domain"/> </condition> </selectAction> </context> Edit that XML to the following by adding the two lines with the comment <!-- New --> below: <!--jasperserver designer pro only--> <context name="main_create_mutton" test="isProVersion"> <selectAction labelKey="NAV_005_CREATE"> <option labelKey="NAV_051_ADHOC_REPORT" action="primaryNavModule.navigationOption" actionArgs="designer"/> <condition test="checkAuthenticationRoles" testArgs="ROLE_ADMINISTRATOR"> <!-- New --> <option labelKey="NAV_050_DASHBOARD" action="primaryNavModule.navigationOption" actionArgs="dashboard"/> </condition> <!-- New --> <condition test="checkAuthenticationRoles" testArgs="ROLE_ADMINISTRATOR"> <option labelKey="NAV_056_DOMAIN" action="primaryNavModule.navigationOption" actionArgs="domain"/> </condition> </selectAction> </context> We are effectively inserting a condition such that the "dashboard action" is only available to administrators. After the actionModel-navigation.xml file has been edited and saved it is necessary to restart JasperReports Server. The JasperReports Server web interface will now provide the Dashboard option in the Create drop-down menu only if the logged-in user has been assigned the role ROLE_ADMINISTRATOR.
×
×
  • Create New...