The problem lied in that in advanced allocation perspective only the
task being modified was saved. Now the task's parents are updated and
saved too.
FEA: ItEr68S04BugFixing
Changes in resources load is filtered by criteria:
* second level tag: one row per generic resource allocation with the criteria names of the resource allocation.
* third level tag: one row per workers of the resource allocation with the name of the workers.
FEA : ItEr68S04BugFixing
it sorts the list by company name.
it changes a label by other one to facilitate the understanding.
it adds the delete operation of a company with some constraints.
FEA : ItEr67S04BugFixing
They were not working as expected. NotBlockingDesktopUpdates was
delegating to the decorated emitter the available values, but for each
event it blocked until a new polling request has been made. Now all
progressive executions have async notifications and several updates
are executed in each polling request.
FEA: ItEr68S04BugFixing
This exception happened after saving and continuing due to labels not
being in the session.
ERROR org.hibernate.LazyInitializationException - failed to lazily initialize a collection of role: org.navalplanner.business.templates.entities.OrderElementTemplate.labels, no session or session was closed
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.navalplanner.business.templates.entities.OrderElementTemplate.labels, no session or session was closed
FEA: ItEr68S04BugFixing
CONTENTS_CHANGED event doesn't work well when the node has children as
the new content.
When TreeViewStateSnapshot.openIfRequired(Treeitem) tries to open the
previously opened element, the associated Treeitem has the _loaded
property set to true. As you can see in [1] this avoids the children
to be rendered.
Instead a INTERVAL_REMOVED and INTERVAL_ADDED are fired so the the
Treeitems for the elements moved are removed and recreated completely
avoiding that problem.
This introduces a new issue: the node loses its selection status but
can be fixed using a similar approach to TreeViewStateSnapshot.
[1] org.zkoss.zul.Tree.renderItem0(Renderer, Treeitem, Object)
The error was happening due to using Dates instead of LocalDates. The
start of the satisfaction was in the middle of a day and the received
Date was at the start, so the first day was considered outside of the
criterion satisfaction's interval. Criterion satisfactions now use
LocalDates instead of Dates and this problem is fixed.
FEA: ItEr67S04BugFixing
The named parameter must be provided always otherwise this can happen:
Caused by: org.hibernate.QueryException: Not all named parameters have been set: [name] [Select t from OrderElementTemplate t where t.parent = NULL and LOWER(t.infoComponent.name) like LOWER(:name)]
at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:291)
FEA: ItEr67S04BugFixing
