Dynamic jasper reports: how to tell FastReportBuilder to respect timezone

[Joe Simone]

I am using this class

ar.com.fdvs.dj.domain.builders.FastReportBuilder

it is part of the the dynamic jasper package and allows creating jasper reports on-the-fly. The issue I have is that when I add a Timestamp column to my report, the time zone it uses for formatting is always EST.

Does anyone know how to accomplish this? Here is a snippet of code ...

        FastReportBuilder rep = new FastReportBuilder();
        rep.setUseFullPageWidth(false); 
        rep.setPrintColumnNames(true);
        rep.setIgnorePagination(true);
        rep.addColumn("Date", String.valueOf(26),  "java.sql.Timestamp", 26, false, "MM/dd/yyyy hh:mm:ss a zzz");

        DynamicReport dynReport = rep.build();
        JRDataSource dataSource = new ReportResultsJRDataSource(resultDto);
        JasperPrint  jasperPrint = DynamicJasperHelper.generateJasperPrint(dynReport, 
                               new ListLayoutManager(), dataSource);
 
        JRCsvExporter exporter = new JRCsvExporter();
        exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
        exporter.setParameter(JRExporterParameter.OUTPUT_WRITER, out);
        try {
            exporter.exportReport();
        } catch (JRException e) {
            throw new IOException(e.getMessage());
        }

 

I get this in the output: ... 12/06/2012 02:47:51 PM EST ...

Thanks in advance.

[Paul Clapham]

What would "respecting a timezone" mean? I'm assuming that EST is the default time zone when the application runs, so what should cause the application to choose some other time zone?

[Joe Simone]

Paul Clapham wrote:What would "respecting a timezone" mean? I'm assuming that EST is the default time zone when the application runs, so what should cause the application to choose some other time zone?

Sorry if I was not clear. The code does make use of the timezone defaulted to EST. I just want to be able to pass in and change the timezone accordingly. For example if someone from the west coast runs the report I would like the date to be formatted for PST (his local zone) instead of the default EST.

I've spent most of the day trying to google an example of how this would be done.

Thanks in advance.

[Paul Clapham]

That would involve knowing how the report was run. If the person from the west coast ran the report on their own computer, then the default time zone would be their time zone and you wouldn't be asking the question. So I have to conclude that somehow the person from the west coast is running the report somehow on some other computer.

[Joe Simone]

True.

The reports are all run on our east coast servers, hence the default JVM timezone of EST. However, the customer's data maybe from another timezone - the one they are located in. The code that gets called for the jasper csv export has as one of its invocation parameter the timezone, but we have no place to set it so dynamic jasper FastReportBuilder can make use of it.

Therefore, I am stuck.

Thanks in advance.

[Paul Clapham]

Joe Simone wrote:The code that gets called for the jasper csv export has as one of its invocation parameter the timezone, but we have no place to set it so dynamic jasper FastReportBuilder can make use of it.

So there are two problems (I think).

(1) You need to fix that code so that you do have a place to set the time zone.

(2) You need some way of deciding which time zone to set, once (1) is fixed.

[Joe Simone]

I tried setting timezone in the jasperPrint object thusly

        jasperPrint.setTimeZoneId(resultDto.getTimezone().getID());
        System.out.println("TIME ZONE SET TO ..."+resultDto.getTimezone().getID());

and I still get the following in the CSV export ...

TIME ZONE SET TO ...US/Pacific
... ,12/06/2012 05:55:44 PM EST, ...

Not much progress today!

Thanks in advance.

[Joe Simone]

This jasper forum comments seems to indicate this was recently addressed and fixed:

jasper community issue 4616

[Joe Simone]

public static final String PROPERTY_TIME_ZONE = "net.sf.jasperreports.jdbc.time.zone"

How to set this property and where is now the question

[Joe Simone]

I updated both DynamicJasper to 4.0.3 and jasper reports to 4.7.1 and tried to set the time zone 4 places in the code below. Still fails to set the timezone correctly.

	public void writeCSVReport(Writer writer, ReportResultsDto resultDto)
	        throws IOException, ClassNotFoundException, JRException {
		   
		TimeZone timezone = resultDto.getTimezone();

		FastReportBuilder reportBuilder = new FastReportBuilder();
		reportBuilder.setUseFullPageWidth(false); 
		reportBuilder.setPrintColumnNames(true);
		reportBuilder.setIgnorePagination(true);
		reportBuilder.setProperty(JRParameter.REPORT_TIME_ZONE, timezone.getID());

        int index = 0;
        for (ReportColumnMetadataDto metadataDto : resultDto.getMetadata()) {
            if (metadataDto.isDisplay()) {
                String columnLabel = metadataDto.getLabel();
                String columnClassName = metadataDto.getColumnClass();
                Class<?> columnClass = Class.forName(columnClassName);
                
                System.out.println("index="+index+"    label="+columnLabel+
                                "     className="+columnClassName);
                
                if (java.util.Date.class.isAssignableFrom(columnClass)) {
                    reportBuilder.addColumn(columnLabel, String.valueOf(index),
                        columnClassName, metadataDto.getColumnSize(), false, "MM/dd/yyyy hh:mm:ss a zzz");
                } else {
                    reportBuilder.addColumn(columnLabel, String.valueOf(index),
                        columnClassName, metadataDto.getColumnSize());
                }
            }
            index++;  
        }

        DynamicReport dynamicReport = reportBuilder.build();
        dynamicReport.setProperty(JRParameter.REPORT_TIME_ZONE, timezone.getID());
        
        JRDataSource dataSource = new ReportResultsJRDataSource(resultDto);
        ((JRAbstractTextDataSource)dataSource).setTimeZone(timezone.getID());
        
        JasperPrint jasperPrint = DynamicJasperHelper.generateJasperPrint(dynamicReport, 
                  new ListLayoutManager(), dataSource);
        jasperPrint.setTimeZoneId(timezone.getID());
        
        System.out.println("\n TIME ZONE SET TO >>>"+jasperPrint.getTimeZoneId()+"\n");

        JRCsvExporter exporter = new JRCsvExporter();
        exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
        exporter.setParameter(JRExporterParameter.OUTPUT_WRITER, writer);
        exporter.exportReport();

        writer.flush();
	}

Results we get are still wrong. Note the EST in the formatted date.

index=0    label=My First Name     className=java.lang.String
index=1    label=My Last Name     className=java.lang.String
index=2    label=Email Address     className=java.lang.String
index=13    label=Registration Date     className=java.sql.Timestamp
index=14    label=Registration Status     className=java.lang.String
index=15    label=Payment Status     className=java.lang.String
index=16    label=Payment Type     className=java.lang.String

 TIME ZONE SET TO >>>US/Pacific

My First Name,My Last Name,Email Address,Registration Date,Registration Status,Payment Status,Payment Type
John,Doe,[e-mail],12/07/2012 03:41:00 PM EST,Registered,Not Applicable,

[Joe Simone]

Here is the solution to the problem. We must get the jasper print object to respect timezone and setting the timezone id was not having the expected results.

          Map<String, Object> paramMap = new HashMap<String, Object>();
            paramMap.put(JRParameter.REPORT_TIME_ZONE, timezone);
            JasperPrint jasperPrint = DynamicJasperHelper.generateJasperPrint(dynamicReport, new ListLayoutManager(), 
                           dataSource, paramMap);

Now, by passing in a parameter map indicating the new timezone to override the default JVM timezone, we are able to get the JasperPrint object to respect the timezone.

This was tested with Dynamic Jasper 4.0.3 and Jasper reports version 5.0.0. I don't know if this functionality is broken in older versions of these jars so your results may vary.

[Paul Clapham]

Thanks for the follow-up, Joe!