Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (hermes.apache.org: domain of atmanes@gmail.com designates
 64.233.170.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=WZX9nIMJiL1UuGjPIDRX0P3LytT9j+SJhNhV/Nyi+0+CUEunO0e4N5UYlMEuLpQ0qH8bXTsi1ZvHy01k6aA8+KW8GiarTu5ZrdO/DJ1iN04qE6XOXH4G5NSn4Mcq30Ylvc1WHU0wJeaEG9fqrklhS7OgfbSCrjBFSUw3ez1CRp8=
Message-ID: <bf414ee6050307062570cfcc60@mail.gmail.com>
Date: Mon, 7 Mar 2005 09:25:56 -0500
From: Anne Thomas Manes <atmanes@gmail.com>
Reply-To: Anne Thomas Manes <atmanes@gmail.com>
To: axis-dev@ws.apache.org, babloosony <babloosony@gmail.com>
Subject: Re: Format/Structure of req./res. soap msg.
In-Reply-To: <ee7d3701050306052069c4083a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <ee7d3701050306052069c4083a@mail.gmail.com>

The schema always defines the structure and format of request and
response messages. If you are using a Java/XML binding tool, such as
JAXB, JiBX, or Castor, then you can have these tools generate the
schema that goes into your WSDL. But the message on the wire must
conform to the schema in the WSDL.

Anne


On Sun, 6 Mar 2005 18:50:13 +0530, babloosony <babloosony@gmail.com> wrote:
> Hi All,
> 
> What determines the structure/format of custom types(we use in a web
> service method call) in request/response soap mesages(that we can view
> using AXIS TCPMonitor). Does the schema definition in WSDL determines
> and/or the custom (de)serializers (like jaxb, jibx, castor) determines
> it ?
> 
> Please clarify ...
> 
> Thanks & Regards,
> Kumar.
>