Jump to content

How to Update JRXML from old jasper to new jasper.?


Neeraj Rathi

Recommended Posts

  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

You can upgrade directly to 4.7.0 if your instance is one of the
following:

  * 3.7.0
  * 3.7.1
  * 4.0.0
  * 4.1.0
  * 4.2.1
  * 4.5.0

To upgrade, start with the WAR File Distribution ZIP:

  jasperreports-server-cp-4.7.0-bin.zip
 
It can be downloaded from JasperForge.org at Releases/Downloads area.

The recommended upgrade procedures are fully described in the
Installation Guide. See chapters 7 and 8.


Database Changes
----------------

The jasperserver repository database has changed between version
4.5.0 and 4.7.0. These changes support the upgrade of the quartz
scheduler component version as well as feature updates, such as
scheduled report job enhancements.


3.7.0, 4.0.0, 4.1.0, 4.2.1, or 4.5.0 to 4.7
-------------------------------------------

You can upgrade directly to 4.7.0 if you are at a version number
listed above.

The recommended procedure is described in the Installation Guide
Chapter 7. In this procedure, you run the js-upgrade script:

  js-upgrade-newdb-ce.bat/sh


NOTE: This procedure sets your jasperadmin login password back to its
default (jasperadmin). This issue will be fixed in a subsequent release.


4.5.0 to 4.7
------------

To upgrade from 4.5, the recommended procedure is described in
the Installation Guide Chapter 8. In this procedure, you run the
js-upgrade script:

  js-upgrade-samedb-ce.bat/sh


Upgrading Input Controls to 4.7.0
---------------------------------

Prior to release 4.7, query-based input controls of type string
were allowed for queries that returned dates. As of release 4.7,
the type of the input control must match exactly the type of
the field returned by the query. You must manually update your
query-based input controls to use only controls of type date for
date values.

Query-based input controls also support the $X{} syntax now to
handle equality comparisons with null values as input. The
following query will fail when the value of <parameter> is null:

  select * where <column> = $P{<parameter>}

Instead, use the following syntax:

  select * where $X{EQUAL, <column>, <parameter>}

The $X{EQUAL...} syntax will generate the correct SQL to compare
the value of the parameter when it is null. For any other types
of comparison, such as greater than, use the $P{} syntax.
 

Security After Upgrading to versions 4.5.0 and later
----------------------------------------------------

With the security framework introduced in JasperReports Server
4.5.0, user input and values passed to reports are restricted to
avoid potential security threats. In particular:

* Parameter names and values cannot have tags (that is, the
  < and > characters). If your business data contains tags, you
  need to update the security configuration to allow them.

* SQL queries must start with SELECT and cannot have comments.
  If your reports or Domains have queries with comments, you
  must either remove the comments or update the security
  configuration to allow them.

These restrictions were added to comply with security guidelines
for web applications. Removing the restrictions may make the
application more vulnerable to attacks.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...