rsilverns.sympatico.ca

Aleksss, To introduce pages into Jasper you have to create dummy Group elements and make each 'page' being a Group Header band. There is no way currently to make pages in the detail band itself. HTH, Robin

Teodor does that work if the 3 reports have different page sizes/layouts? R.

I don't know if this is possible under JaserpReorts directly, but you can easily post-process the report with iText and insert the Page numbering manually that way. iText is pretty powerfull and it can be done with about 20 lines of code. Not sure if this helps or not... R.

Teodor, I am not sure if you recall, but we exchanged several emails last November concerning my inability to log into the website to post follow up questions and as such I emailed you directly as per your instructions asking at that time for the feasibility of my RFE. There was no response to that email to this point is what I meant by 'no action on it'. Not withstanding those technical issues, my mentality behind this RFE is the ability to have 1 report be visible in 1 file in your editor, and to have the ability to designate a report design that is clear and logically outlined. Using work-around's is never as preferable as using a straight forward solution and from an architectual perspective a cause for concern. Don't get me wrong, I think JasperReports is an amazing technology, I am just trying to express ways that it does not seem to meet my needs and hopefully participate in it's evolution and growth. R.

I know about the break element (now). What i mean is a way to designate set 'pages' in the detail band. I have had a RFE in for about 1.5 years now, but never really had any action on it. Just wondering if it is even a blip on the radar, or a long ways off still. My theory is it simply cuts the detail band and inserts a new page whenever it is encountered. Each 'page' that it cuts would still be required to be validated for height etc. individually, and the element would have no printWhen's or other variables assigned to it that would interfere with its evaluation time. R.

Just pass the name in as a parameter, and set the parameter to have a default value of the name you assign to the report. Edit: As an example: Code:<?xml version="1.0" encoding="UTF-8"?> <!-- Created using JasperAssistant (http://www.jasperassistant.com) --> <!DOCTYPE jasperReport PUBLIC "-//JasperReports//DTD Report Design//EN" "http://jasperreports.sourceforge.net/dtds/jasperreport.dtd"> <jasperReport name="Unnamed" pageWidth="595" pageHeight="842" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="30" bottomMargin="30"> <property name="com.jasperassistant.designer.Grid" value="false"/> <property name="com.jasperassistant.designer.SnapToGrid" value="false"/> <property name="com.jasperassistant.designer.GridWidth" value="12"/> <property name="com.jasperassistant.designer.GridHeight" value="12"/> <parameter name="REPORT_NAME" class="java.lang.String" isForPrompting="false"> <defaultValueExpression><![CDATA["My Sample Report"]]></defaultValueExpression> </parameter> <detail> <band height="100"> <textField> <reportElement x="40" y="9" width="132" height="20"/> <textElement/> <textFieldExpression class="java.lang.String"><![CDATA[$P{REPORT_NAME}]]></textFieldExpression> </textField> </band> </detail> </jasperReport> HTH, Robin Post edited by: rsilver@ns.sympatico.ca, at: 2007/12/17 14:21

Teodor, What are the odds that there will ever be a <page_break> element or something similar to achieve the multiple pages in the detail band? I am sure that thinking up this idea there are many concerns that I don't consider, but it seems like it would be a very valuable element to have. Most of my reports have been based on 'pages' as well as I am sure a lot of others. Is this on the plate at jasperforge at all? Thx, Rob

I'm sure I am overlooking some basic fact about the <break> element here so wanted to post and hopefully get my confusion cleared up. I created the attached sample report that illustrates my problem. It is a LONG detail band that is longer than 1 page and has a break element roughly 20px above where the first page ends. I tried to compile it to see the break in action but I get the error: Code: Shouldn't I be able to use the break element this way? Detail bands can span multiple pages normally, so wondering how i can design my report 'pages'. I really want to avoid using any work arounds as I really embraced the break element to avoid the usual group header-page workaround. Attached is a very simple sample report that illustrates my issues. I'm using JasperReports 2.0.2. [file name=pagebreak_sample-d2602f001bf5cf6ee2fa5b97718ebd5c.jrxml size=1704]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/pagebreak_sample-d2602f001bf5cf6ee2fa5b97718ebd5c.jrxml[/file] Post Edited by iryzhikov at 06/05/2012 16:56

Whoops.. forgot to attach.. here you go. [file name=pagebreak_sample.jrxml size=1678]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/pagebreak_sample.jrxml[/file]

Whoops.. forgot to attach.. here you go. [file name=pagebreak_sample-686ab5774e1dc546dc0c73f4182fa469.jrxml size=1678]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/pagebreak_sample-686ab5774e1dc546dc0c73f4182fa469.jrxml[/file] Post edited by: rsilver@bfm.bm, at: 2007/12/12 14:25

I'm sure I am overlooking some basic fact about the <break> element here so wanted to post and hopefully get my confusion cleared up. I created the attached sample report that illustrates my problem. It is a LONG detail band that is longer than 1 page and has a break element roughly 20px above where the first page ends. I tried to view it to see the break in action but I get the error: Code:net.sf.jasperreports.engine.design.JRValidationException: Report design not valid : 1. The detail section, the page and column headers and footers and the margins do not fit the page height. at net.sf.jasperreports.engine.design.JRAbstractCompiler.verifyDesign(JRAbstractCompiler.java:260) at net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:144) at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:220) at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:153) at com.test.ReportRunner.main(ReportRunner.java:21) Shouldn't I be able to use the break element this way? Detail bands can span multiple pages normally, so wondering how i can design my report 'pages'. I really want to avoid using any work arounds as I really embraced the break element to avoid the usual group header-page workaround.

Hey Rachel, I've seen the same thing using JasperAssistant. Until I added a break element using the tool, I would get the same error message. You ever get any feedback on this? Rob

Can you confirm that you have named the parameter in JasperServer the same as the parameter is defined as in your jrxml file? i.e. in JasperServer you may have a text box named "ProductDescription", this parameter in the jrxml file must then be $P{ProductDescription}.

Hey Exie, As far as reporting on your data what you would need to do is... 1. Design the report to display the relevant data using a design tool (IReports, JasperAssistant, etc.). In doing so you will need to configure your data as a data source. I am assuming by "lumps of data" you mean "collection of data stored in a table or tables"? I havn't used Oracle that much to be honest, so if its an Oracle-native term please forgive me :). 2. Once you've designed and tested the report, you need to insert the report into JasperServer using the gui interface. This shouldn't be a hard task, just upload the images, subreports, etc. as needed. One trick is that any image etc. that is stored in the repository must be referred to as "repo:/<PATH>/<filename.extension>" in your report. repo:/ is a reference to repository structure where your files will be stored once they are uploaded. 3. Once you have the report and support elements installed you will need to configure your datasource. To do this you have to install the jar file in the web server.. for me this meant putting it in "C:Program FilesApache Software FoundationTomcat 5.5commonlib". Once this jar file is in place, restart your server and it should pick it up. Then its just a matter of entering the proper driver class name, and other such details of where your database server is located and you should be good to go. HTH, Robin

Adam, The algorithm for positioning elements inside of an XLS file is pretty strict. You have to be cautious when designing your report that elements line up properly or they will be seperated by these rows and columns that you are seeing. I would check the layout of your elements and see where the items can be more closely aligned. This may help you remove some of these extra rows/columns. HTH, Robin