[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Condor-users] condor_q -xml bug?

Thanks for the quick reply.  I see what you're saying about separating
between multiple schedd results.  I'm not familiar enough with XML to
know, but is there a way to use some sort of remark/comment tags on
either sides of the non-XML information?.  Maybe that would allow an XML
parser to just ignore those areas.  As it stands, piping the XML output
directly into another application just doesn't seem doable. 



-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Alain Roy
Sent: Thursday, June 16, 2005 6:52 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] condor_q -xml bug?

>So I'm learning that a "well formed" xml file has the xml version on
>first line and nothing else.  It appears that 'condor_q -xml' outputs a
>"-- Submitter..." line as the first line.  I have to parse the removal
>of the line in my code in order for the XML interpreter to recognize
>XML.  Is this a bug?

I'm the author of the code that did the XML code, so it's probably a
idea for me to comment on this.

I think it's debatable if it's a bug or not. I'm open to suggestions on 
this point, but I don't think it is. I think of the output of condor_q
as a body of text that happens to contain an XML document as a subset of

the text.

If you have more than one schedd in your pool, try "condor_q -global
and you'll see something like this:

-- Schedd: whoppers.cae.wisc.edu : <>
<?xml version="1.0"?>
<!DOCTYPE classads SYSTEM "classads.dtd">

-- Schedd: gamgee.cs.wisc.edu : <>
<?xml version="1.0"?>
<!DOCTYPE classads SYSTEM "classads.dtd">


So for each schedd we have a separate XML document. Is this optimal? 
Perhaps not, but I don't think it's a bug.

In the general case, we might have things like error messages intermixed

here too. We could define a larger XML document that encodes all of this

information. We decided to keep it simple though.


Condor-users mailing list