Bug 5745 – Allow users to specify JDD in a different order than RSL schema

Bug 5745 - Allow users to specify JDD in a different order than RSL schema

Summary:

Allow users to specify JDD in a different order than RSL schema

Status:	RESOLVED WONTFIX

Product:	GRAM
Component:	wsrf gram clients
Version:	4.1.2
Platform:	Macintosh All

Importance:	P3 enhancement
Target Milestone:	---
Assigned To:	Stuart Martin

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-12-21 14:37 by Charles Bacon
Modified:	2012-09-05 11:43 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Charles Bacon 2007-12-21 14:37:34

Right now, users have to write their JDD in RSL schema order.  I propose that
the client re-order the JDD into a schema-compliant order and possibly output a
warning that it happened.  There should be both C and Java API calls so that
people who write other clients can call it also.

------- Comment #1 From Joe Bester 2008-04-25 12:47:24 -------

It might be better to do this in the schema (use the xsd:all compositor instead
of the xsd:sequence compositor). The arguments, library_path, and environment
elements would need to be slighly modified to do so, as they are an unbounded
particle.

------- Comment #2 From Stuart Martin 2012-09-05 11:43:39 -------

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:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363