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 ajith.ranabahu@gmail.com
 designates 64.233.184.194 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=aKfxDXveyWDXYsJ6ZcSE7bVAGUx7DAF1ssOyrbTPuO4TL8EWX9NpVQzFnEbPl9x/4wWtAcIA1poWlT4H0mQs+m6ShKJzMwoGVE+zIhFNSIX+m5PYyZ6Nx5mSIkMhzn1vS5DLYtnXNFmzxKRnURgyHDeLSOIpFvV927mh19AfwiU=
Message-ID: <f43ea579050311032225f9bd11@mail.gmail.com>
Date: Fri, 11 Mar 2005 17:22:59 +0600
From: Ajith Ranabahu <ajith.ranabahu@gmail.com>
Reply-To: Ajith Ranabahu <ajith.ranabahu@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Message structure and Attachments
In-Reply-To: <E0467379DD4FA84BAF6E42D3161A9A0880680B@inhyms21.ca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <E0467379DD4FA84BAF6E42D3161A9A0880680B@inhyms21.ca.com>

Hi,
Well yes there has been some skipping of the specs. SOAPMessage was
deliberately skipped and you wouldn't find the SOAPpart anywhere
either.
 Interestingly there is no concept of an OM document (which if existed
should match with the SOAPMessage in my sense). What you will get is
the envelope directly from the builder.
The catch here is that this framework is built not with SAAJ (or any
of the other specs for that matter) in mind. It is supposed to be a
lightweight framework and if SAAJ is needed theoretically it is
possible to layer it upon this framework. An infoset model for the
Binary content has already being suggested (OMBlob) but it is again
not SAAJ specific.
Have a look at the mail I sent to the dev list for Venkats question.
I've included a description  of the Axis 2 view :)

BTW we appreciate all of you guys going over the code. More brains the
better it is :)


On Fri, 11 Mar 2005 16:26:30 +0530, Shahi, Ashutosh
<Ashutosh.Shahi@ca.com> wrote:
>  
>  
> 
> Hi all, 
> 
>             I was looking at the how message is constructed in Axis2, and
> found it to be little different from what we do in Axis 1.2. In Axis 1.2 we
> get the SOAP Envelope through: MessageFactory - > SoapMessage - > SOAPPart
> (and Attachment Part) -> SOAPEnvelope. This is according to SAAJ 1.2 specs.
> But in Axis2 we directly get SOAPEnvelope from the factory class. 
> 
>             I could not find any concept of SoapMessage and SOAPPart. And,
> though I have glanced at the discussion on MTOM and the implementation code,
> I could not understand how AttachmentPart forms part of a SOAPMessage and
> how SOAPEnvelope and AttachmentPart are linked. Has it been deliberately
> decided not to follow the message structure in Axis 1.2 (and SAAJ)? If yes,
> then what is the kind of message structure that has been planned? 
> 
>             I have just started looking at the Axis2 code, so tell me if
> there is any misunderstanding on my part. 
> 
>   
> 
> Ashutosh 
> 
>   


-- 
Ajith Ranabahu