All,
   I found some examples pertaining to attachments in the "samples" provided with 
Axis. But
these use RPC style communication. I guess we could modify our code accordingly, but 
atleast
to satisfy my curiosity, I would appreciate if someone would post an example where an 
entire
SOAPMessags is transmitted along with multiple attachments. Thank you.
sincerely,
Ramesh

>  -----Original Message-----
> From:         Mantri, Mr. Ramesh (Contractor)  
> Sent: Thursday, April 29, 2004 10:25 AM
> To:   '[EMAIL PROTECTED]'
> Subject:      RE: using Axis in a legacy webapp
> 
> Also, could someone please post a simple example of a "client-server" that uses
> Document/Literal communication. Thank you.
> sincerely,
> Ramesh
> 
>        -----Original Message-----
>       From:   Mantri, Mr. Ramesh (Contractor)  
>       Sent:   Thursday, April 29, 2004 10:12 AM
>       To:     '[EMAIL PROTECTED]'
>       Subject:        using Axis in a legacy webapp
> 
>       All,
>          the term "legacy webapp" might sound paradoxical. We wrote a server 
> implemented as a collection of
>       JAXMServlets. Everything was sort of alright until we were told we would have 
> to stick a few Axis Handlers
>       in front of the server.
> 
>       My experience with Axis is about two weeks. I am aware that one shouldn't 
> expect too much from Open
>       Source by way of documentation since people don't get paid to do the work, 
> even if it isn't entirely thankless.
>       So I learnt a few things by trial-and-error, and also taking a peek into the 
> source when necessary. By and
>       large we are happy with Axis; we haven't observed any cause for complaint so 
> far. In particular, we were
>       pleased to observe that we were able to pass huge XML strings (200KB) to and 
> fro.
> 
>       Two questions:
>       1. What is the best way to pass attachments? One method that struck me was we 
> could stick a simple
>           Handler which adds AttachmentParts to the SOAP Messages. If there is a 
> better way, please let us know.
>       2. Have there been any problems communicating through "https" in place of 
> "http"? This is important for us.
> 
>       Thanks in advance and kudos to Axis developers.
>       sincerely,
>       Ramesh Mantri

Reply via email to