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

wolverto_1

Members
  • Posts

    17
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by wolverto_1

  1. There are two issues I am facing within JS Studio 5.5 related to the positioning of an organization within my Repository Explorer tab.  

    1.  The referenced style sheet only loads for the topmost Organization.  This is problematic because you can't tell whether or not styles are being applied to fields when working within an organization that is not topmost.  It looks like a un-styled report until you run it off of JasperServer where it will then correctly display a styled report.

    2.  When saving a report to the server, JS Studio does not bring you to the location from which you opened the report !!  Again, this only happens when you are working within an organization that is not the first in the list of organizations set up in the Repository explorer.  This makes it difficult to work out of multiple organizations during the course of the day not to mention if a report is accidently overwritten it is much harder to retrieve the original copy than it was using IReport.  IReport also handled this better with the "Replace with current document' function.  It seems to me that JS Studio has trouble following the organization structure.

    Have others run into these issues and/or know how it can be resolved?  

  2. Hello,  I have created what is essentially a book of reports in Jasper 5.0 using Ireport.Professional 5.0.  

    There is one blank master report holding 4 main reports.  Within the 4 main reports are many underlying subreports built to handle different scenarios, filtering headers/bands, etc.  The queries themselves are not large or complex, but the vast number of them is causing problems in returning the report.  When watching the report run, queries are being issued one-by-one instead of multi-threading.

    In any case, we’re also seeing issues within the session management component of Jasper-5.0 that are causing the “conversation lock” timeouts and reports to run away after they’ve been cancelled.  Any advice/suggestions are greatly appreciated, thanks!

×
×
  • Create New...