The current set of tests show that there are issues with either the tests or the software behavior and we need to determine which.
Ron has some results to show on the call today so we can resolve.
As I understand it, the problems are two-fold:
1) When you do a POST, you can’t do a GET of the results because you don’t know the IDs that will be assigned
2) The current implementation won’t instantiate links for collections that are not yet populated. That is if you POST a UsagePoint, there will be no ElectricPowerUsageSummary link until an ElectricPowerUsageSummary is added.
If this is desired behavior, the tests will have to be modified to accommodate. If it is not, the software updated.
Note that the autoincrement nature of the table IDs assigned adds complexity to accepting an addition to a collection (such as a new IntervalBlock) since the mapping between source ID and destination ID will have to be made. Also, the operation of the sandbox which needs to be repopulated often will have a dependency of always having to have things in the same order and same composition. Otherwise the assigned links will change.
Marty