Bug 5425 - Backwards compatability break in 4.0.5
: Backwards compatability break in 4.0.5
Status: RESOLVED INVALID
: GRAM
general
: 4.0.4
: Macintosh All
: P3 normal
: 4.0.6
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-07-06 11:24 by
Modified: 2007-07-10 14:50 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-07-06 11:24:24
ManagedExecutableJobConstants.RD_STAGING_JOB_ENDPOINT does
not exist anymore in Gram in GT 4.0.5

Instead, three other constants exist:
ManagedExecutableJobConstants.RD_STAGE_IN_ENDPOINT
ManagedExecutableJobConstants.RD_STAGE_OUT_ENDPOINT
ManagedExecutableJobConstants.RD_CLEAN_UP_ENDPOINT

We had to change this because of audit logging in 4.0.5.
Having only one constant we had not been able to store
various endpoints of stageIn, stageOut and fileCleanup requests
which are now saved as part of an audit record. 

But we forgot backwards compatability issues when we removed
that constant. A check is needed whether this constant can be added
again in a way that makes sense.
------- Comment #1 From 2007-07-10 14:50:43 -------
I'm resolving this.  I don't think we need to worry about compatibility to this
level.  This is an internal service variable that does not need to be preserved
for backward compatibility.  What needs to be preserved is the service
interface and any supported client and service APIs.

-Stu