Bug 4734 - Missing wsa:Action for GRAM4 rendezvous register operations
: Missing wsa:Action for GRAM4 rendezvous register operations
wsrf managed multi job service
: 4.0.3
: All All
: P3 normal
: 4.2.1
Assigned To:
  Show dependency treegraph
Reported: 2006-09-27 06:24 by
Modified: 2012-09-05 11:43 (History)



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

Description From 2006-09-27 06:24:35
The ManagedExecutableJobPortType and ManagedMultiJobPortType schema
declarations should have (had) wsa:Action directives to allow for the reuse of
the standalone rendezvous client libraries that are shipped with GT to also
talk to the GRAM(4) services.

As things stand right now, I have to have multiple client bindings linked in
with my application and logic to keep track what type of GRAM service it is
that I rendezvous with.
------- Comment #1 From 2006-09-27 08:52:45 -------
I already added wsa:Action attributes to the 4.0 MJFS and MJS WSDLs in the
trunk (we discovered this problem with 4.1.0). I didn't realize the operations
defined in the ws-rendezvous WSDLs were missing those attributes as well, so
I'll fix that in the trunk when I get a chance.
------- Comment #2 From 2007-09-19 11:38:03 -------
Reassigning to current GRAM developer to close/fix as appropriate.
------- Comment #3 From 2012-09-05 11:43:19 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here: