nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Order matters in jobspec elements?

pbenn

Hi,

While using XML: Smiley Frustrated

imple to post edit a hand edited jobspec file, I noticed that I started seeing missing vpath errors when I attempted to iwjobc -i the modified XML:: Smiley Frustrated

imple::XMLout created files. XMLout does not guarantee ordering of elements and attributes.

WHen I tried making areavpath the first subelement of my cgi task, it stopped complaining about the missing areavpath, but then started complaining about missing successors. I moved the successorset to be my second subelement, and low and behold, it stopped complaining.

Is this surprising to anyone else?

Thanks

P.

Find more posts tagged with

Comments

Adam Stoller

Not really surprising - the DTD for workflows specifies the ordering of the elements it expects to see in task definitions. The fact that the code / editor you're using to process / produce a job spec doesn't adhere to that ordering is a problem with that code / editor IMO.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com