You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, you needed to set the following parameters manually before calling xlib_jasperreports.show_report or xlib_jasperreports.get_report:
xlib_jasperreports.set_report_url
utl_http.set_wallet
utl_http.set_transfer_timeout
This is now done for you using the defaults in the table XLIB_JASPERREPORTS_CONF.
Setting those parameters explicitly will still work, they are only set when those values HAVE NOT BEEN SET.
Unfortunately, this is not the case for utl_http.set_wallet because we cannot determine the current wallet path.
Thus, when the report url is using https, set_wallet will be called automatically based on the values in XLIB_JASPERREPORTS_CONF regardless of previous calls to utl_http.set_wallet ... thus overwriting it.
The text was updated successfully, but these errors were encountered:
#45#44
- added jdbc library to $install/lib directory for convenience if somebody wants to register that in JasperSoft Studio
- included a new and improved sample application 2.6.1 with lots of new features
- updated documentation
- fix in compilation on the fly (jrxml => jasper)
- index.jsp has new reference to locale documentation from Oracle
- removed outdated demo reports
- updated test.jrxml and removed user objects for security purposes
- added tables XLIB_JASPERREPORTS_CONF and XLIB_JASPERREPORTS_DEMOS
- implemented picking up defaults from XLIB_JASPERREPORTS_CONF
Previously, you needed to set the following parameters manually before calling
xlib_jasperreports.show_report
orxlib_jasperreports.get_report
:This is now done for you using the defaults in the table
XLIB_JASPERREPORTS_CONF
.Setting those parameters explicitly will still work, they are only set when those values HAVE NOT BEEN SET.
Unfortunately, this is not the case for utl_http.set_wallet because we cannot determine the current wallet path.
Thus, when the report url is using https, set_wallet will be called automatically based on the values in
XLIB_JASPERREPORTS_CONF
regardless of previous calls to utl_http.set_wallet ... thus overwriting it.The text was updated successfully, but these errors were encountered: