Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0034272 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] A. Platform | minor | always | 2016-10-21 14:52 | 2022-02-01 08:09 | |||||||
Reporter | caristu | View Status | public | |||||||||
Assigned To | Triage Platform Base | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0034272: Not possible to print uncommitted DAL object information with the current reporting API | |||||||||||
Description | Is not possible to print information of not commited DAL objects using the ReportingUtils API. This is because the generateJasperPrint() method[1] is making use of a new connection by using connectionProvider.getTransactionConnection().Thus, the connection passed to the report is not able to see the objects which are not commited. [1] https://code.openbravo.com/erp/devel/pi/file/8f17df764d0f/modules/org.openbravo.client.application/src/org/openbravo/client/application/report/ReportingUtils.java#l955 [^] | |||||||||||
Steps To Reproduce | 1) Get the module from this repository: https://code.openbravo.com/erp/mods/org.openbravo.platform.ci [^] and install it 2) This module contains a process which executes a report. This process has one parameter "Create UOM": - If checked it will create a new UOM and it will be persisted (commit) before printing the report. - Otherwise the new UOM will be created but never persisted. 3) Launch the process checking the flag: the report is generated with data 4) Launch the process without checking the flag: the report will be empty | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Issue History | |||
Date Modified | Username | Field | Change |
2016-10-21 14:52 | caristu | New Issue | |
2016-10-21 14:52 | caristu | Assigned To | => platform |
2016-10-21 14:52 | caristu | Modules | => Core |
2016-10-21 14:52 | caristu | Triggers an Emergency Pack | => No |
2016-12-01 12:21 | alostale | Type | defect => design defect |
2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base |
Copyright © 2000 - 2009 MantisBT Group |