[Bug #628] Fix bug.
Getting the scenario was causing the order to be associated to the session. In order to fix this, the orders are reattached first. FEA: ItEr60S04ValidacionEProbasFuncionaisItEr59S04
This commit is contained in:
parent
e8340b1bd6
commit
81d3193b5b
1 changed files with 5 additions and 4 deletions
|
|
@ -153,11 +153,12 @@ public class TimeLineRequiredMaterialModel implements
|
|||
public JRDataSource getTimeLineRequiredMaterial(Date startingDate,
|
||||
Date endingDate, MaterialStatusEnum status, List<Order> listOrders,
|
||||
List<MaterialCategory> categories, List<Material> materials) {
|
||||
|
||||
for (Order each : listOrders) {
|
||||
reattachmentOrder(each);
|
||||
}
|
||||
Scenario currentScenario = scenarioManager.getCurrent();
|
||||
for (Order order : listOrders) {
|
||||
reattachmentOrder(order);
|
||||
order.useSchedulingDataFor(currentScenario);
|
||||
for (Order each : listOrders) {
|
||||
each.useSchedulingDataFor(currentScenario);
|
||||
}
|
||||
|
||||
List<TimeLineRequiredMaterialDTO> result = filterConsult(startingDate,
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue