Robert,

Ref: http://www.xmlschemareference.com/sequenceElement.html

"
The sequence element provides an XML representation of an ordered set
of element types. For each element type associated with a sequence
element in an XML schema document, there must be a corresponding
element in the corresponding XML instance - in the same order. In
fact, there may be zero or many elements for each element type
depending upon the values of the minOccurs and maxOccurs attributes
associated with the corresponding element types.
"

Yes you are correct sir. That is how the "<xsd:sequence>" XML Schema
element works. ( I am sure you can find other references out there
too, but that was just the second link on google when I searched for
"xsd:sequence".)

HTH

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.



On Thu, Jun 26, 2008 at 6:18 PM, Robert Halstead <[EMAIL PROTECTED]> wrote:
> ** More information on this.
>
> If the order of the fields matches the order of the input mapping when
> sending a Create or Set method, we do not get the error at all.  It's only
> when the order differs.
>
> On Thu, Jun 26, 2008 at 10:16 AM, Robert Halstead <[EMAIL PROTECTED]>
> wrote:
>>
>> System:
>> ARS 6.3 Patch 20
>> Midtier w/ Java 1.4.2_13
>>
>> Hey all,
>>
>> We're using web services to connect with our Remedy server and we're
>> noticing that when sending an opSet XML method to Remedy, the fields need to
>> be in the same order as the Input Mapping is defined for that function.  Is
>> there any way around this, or is this the correct functionality?  It would
>> seem to me that by using XML, the field order shouldn't matter.  There is a
>> chance that I have my input mappings messed up.  Here's an example:

<snip>

>> We don't get the error if we switch the order of the fields in the XML so
>> that Priority is below details.  Is there a way to make it so that the order
>> doesn't matter?
>>
>> --
>> "A fool acts, regardless; knowing well that he is wrong. The ignoramus
>> acts on only what he knows, but all that he knows.
>> The ignoramus may be saved, but the fool knows that he is doomed."
>>
>> Robert Halstead
>
>
> --
> "A fool acts, regardless; knowing well that he is wrong. The ignoramus acts
> on only what he knows, but all that he knows.
> The ignoramus may be saved, but the fool knows that he is doomed."
>
> Robert Halstead

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to