GraphMerger utility so far assumed that the merge(do1, do2) will happen on
DOs
which are contained in DataGraphRoot and have changeSummary associated with
them.
Looking at JIRA-1815, it shows a valid case when an user wants to merge 2
DOs (which do not have any knowledge of DataGraphRoot) and may
Maybe DAS could detect this conflict and throw a specifically Exception for
this case and reporting it to the user.
Regards,
Adriano Crestani
On 10/5/07, Amita Vadhavkar <[EMAIL PROTECTED]> wrote:
>
> GraphMerger utility so far assumed that the merge(do1, do2) will happen on
> DOs
> which are con
Trying to summarize the possible combinations below. Have a question at the
end.
Cases:
Data Objects can be formed in the context of DAS in three ways -
1) static using model - programmatic
2) dynamic using SDO apis - programmatic
3) dynamic using queries - DAS query
It should be possible to merg
I need input at different places -
1) when there are SDOs embedded in DataGraphRoot and DataGraphRoot have
change summaries , it is same as DAS query result.
2) when SDOs are formed from model and are not embedded in DataGraphRoot and
don't have change summaries, GraphMerger
can embed them in Dat
After a couple of discussion over ML and JIRA-1815 comments below is the
summary of changes that can
be accommodated in Graph Merger util.
Graph Merger Improvements:-
Initial/Old scope:
Initial scope for graph merger util was to merge 2 DataObjects coming from 2
executions of DAS. These DOs were
