Return-Path: 
 <axis-dev-return-29563-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 71084 invoked from network); 21 Sep 2004 02:30:47 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 21 Sep 2004 02:30:47 -0000
Received: (qmail 68573 invoked by uid 500); 21 Sep 2004 02:30:44 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 68300 invoked by uid 500); 21 Sep 2004 02:30:42 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-dev@ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 68291 invoked by uid 99); 21 Sep 2004 02:30:42 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [218.214.36.77] (HELO mail.viator.com) (218.214.36.77)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Sep 2004 19:30:38 -0700
Received: from localhost (localhost [127.0.0.1])
	by mail.viator.com (Postfix) with ESMTP id BE3FE2C152F
	for <axis-dev@ws.apache.org>; Tue, 21 Sep 2004 12:32:53 +1000 (EST)
Received: from mail.viator.com ([127.0.0.1])
 by localhost (mail.viator.com [127.0.0.1]) (amavisd-new, port 10025)
 with LMTP id 32502-04-14 for <axis-dev@ws.apache.org>;
 Tue, 21 Sep 2004 12:32:51 +1000 (EST)
Received: from [192.168.100.57] (stephen.viator.com [192.168.100.57])
	by mail.viator.com (Postfix) with ESMTP id DD7BA2BF7F0
	for <axis-dev@ws.apache.org>; Tue, 21 Sep 2004 12:32:51 +1000 (EST)
Message-ID: <414F9245.5050507@viator.com>
Date: Tue, 21 Sep 2004 12:30:29 +1000
From: Stephen Chi Zhang <stephenc@viator.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Strange automatic sorting happening within MessageElement
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at viator.com
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

hi all,
I came to web services with axis a few months ago, so not sure if any 
fella has addressed this problem before and had the problem already 
answerd( I have been searching through the axis mail list for clue 
though).  The problem annoying my for quite a few days without any 
breakthrought is,
I have a xsd file defining a request element containing a few sub 
elements in a wanted order, ie.
<element name="SearchAndSelectResponse">
        <complexType>
               <sequence>
                        <element name="ResponseHeader" 
type="sba:WSRPResponseHeader"/>
                        <element name="Basket" type="sba:Basket"/>
                        <element name="PassengerSummary" 
type="sba:PassengerAgeSummary"/>
                </sequence>
        </complexType>
</element>
I created a SearchAndSelectResponse object and fully populated it with 
some testing dummy data, then assigned this object into a MessageElement 
pending for being sent via web services.
Surprisingly and saddly, when I open tcpmon to monitor the message flow, 
I saw my message elements have been sorted out in an alphabetical order, ie.
SearchAndSelectRequest
       Basket
       PassengerSummary
       ResponseHeader
/SearchAndSelectRequest
This kind of automatic sorting is not what I want. Rather I do need 
those elements are in the order their associated xsd has defined. Does 
anybody have an idea how and where this sorting happens, and even better 
come with a solution to fix the problem. After all, any comment and 
sympathy is highly appreciated. Many thanks in advance.

cheers
Stephen