[kepler-dev] [Bug 4662] New: roll revision vs. new object ID

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4662

           Summary: roll revision vs. new object ID
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: aschultz at nceas.ucsb.edu
        ReportedBy: soong at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


My current auth namespace is 3371.  I have a file with an old auth namespace of
1347.  If I open the XML file, view LSID, and roll revision, then generate a
report and attempt to save the KAR, I get an error saying it can't be saved
because the report is NULL.  If I open the XML file, view LSID, new object ID,
then generate a report, I can save the KAR as expected.  If I open the XML
file, delete an actor then undo, then generate a report, I can save the KAR as
expected.

Thing seem to work fine if the auth namespace is the same.

What's the difference between roll revision and new object ID, why do we need
2, and why doesn't roll revision seem to work in this case.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.