-
Notifications
You must be signed in to change notification settings - Fork 0
ItEr61S04NavalPlanEntities
TWiki> LibrePlan Web>ItEr61S04NavalPlanEntities (20 Aug 2012, ManuelRego)EditAttach
Story summary | Code generation for LibrePlan entities |
Iteration | ItEr61week38To40 |
FEA | ItEr61S04NavalPlanEntities |
Story Lead | |
Next Story | |
Passed acceptance test | No |
Acceptance Criteria
Additional Specification Comments
Implementation Notes
I have created the entities EntitySequence, EntitySequenceDao, and the EntitySequenceTest . Also I have created an enum that represents the entities which use code generation. Also I changed the configuration interface to add the code sequence for each entity.
The problem was fixed. It was reused a method implemented that removes the orderSequence but this one had one problem. it uses the ids of all the sequences which it was going to save or update, to order to select the sequences to remove. It is include in this list of ids the id of the new objects so this returned always a empty list.
It performed the creation of default sequences for the entities with code generation and it replaced the current generation scheme based on random UUID by sequences, except on Calendar entity which has not any generation scheme.
It integrated the entity OrderSequence in the general EntitySequence. This means that the current OrderSequence and OrderSequenceDAO were deleted and the sequences for orders will be managed through rows with entityName=ORDER of EntitySequence .
All integration services were checked. During this verification it found an bug which was reported.
Delay Causes
I have any problems with the transactions when I delete an active sequence and save a new active sequence in your place.
Final or Pending Considerations
It is necessary to create the generation scheme of calendar and the constraint to the configuration interface in order that the prefixes are not repeated. Also it still is should adding the separator ( - ) to other entities sequences like order elements, criteria or labels y the functionality which lets skip a number sequence if this already exists.
Tasks | Est | Spent | To do | Risk | Reviewer | Developer | Task Name | Start Date | Est End Date | End Date |
---|---|---|---|---|---|---|---|---|---|---|
Task | 20 | 24 | 0 | Low | JavierMoran | SusanaMontes | LibrePlan configuration for generated entity codes | 0 | 0 | 0 |
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.