Bug 238025 - Submission of 'bad' JDLs does not handle errors gracefully
Summary: Submission of 'bad' JDLs does not handle errors gracefully
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: David Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 221333 224633 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-21 11:39 EDT by David Johnson CLA
Modified: 2014-01-09 16:15 EST (History)
2 users (show)

See Also:

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 David Johnson CLA 2008-06-21 11:39:52 EDT 
No JDL validation before submission of DAGs

At present there is only rudimentary error checking of JDLs, which is most noticeable when submitting workflows to gLite, but I think applies when submitting any 'bad' JDLs anyway.

Basically I'm using this bug to consolidate 221333 and 224633 each of which both are caused by lack of robust error checking of JDL.

These bugs are not specifically caused by the workflows, but more to do with workflow job submission to gLite. If we consider users importing their own JDLs which might have bad bits in, it will be nice to validate those too.

So when I get this fixed, the fix should cover general submission of JDLs to gLite.
Comment 1 David Johnson CLA 2008-06-21 11:40:42 EDT 
Oh, so someone please assign this straight to me!
Comment 2 David Johnson CLA 2008-06-21 11:44:10 EDT 
*** Bug 221333 has been marked as a duplicate of this bug. ***
Comment 3 David Johnson CLA 2008-06-21 11:47:10 EDT 
*** Bug 224633 has been marked as a duplicate of this bug. ***
Comment 4 David Johnson CLA 2008-09-23 13:55:24 EDT 
targeting RC1, and reducing severity as it isn't hugely important