Hi Thilina

I had some issues getting soap with attachments to work using axis 1.3.

Does axis 1.3 ( or 1.4) support  Web Service Interoperability (WS-I)
organization's SOAP with Attachments reference type: wsi:swaRef .  My
assumption is that Axis 2.0 will support this .

Thanks
  John


On 1/22/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:

Hi,

Have a look at here[1] for an introduction of the different attachment
technologies.

Use SOAP with Attachments if you want to support older soap
clients(Axis 1.x, ..). MTOM is the newest standard and it is the way
forward. I recommend you to use MTOM if supporting older clients is
not an requirement Most of the new SOAP stacks support MTOM..

~Thilina

On 1/22/07, Sherman Uri <[EMAIL PROTECTED]> wrote:
>
>
>
> Hello,
>
> I am looking into using attachments in some of my web services, for the
> trnsfer of pictures, videos, etc.
>
> I googled arround for a bit, and couldn't really find a clear tutorial
in
> axis site on the subject, but rather got confused from all the different
> choices (MIME/DIME/MTOM, using SAAJ and javax.activation in contrust to
> using axis proprietary libraries, and so forth).
>
> So, I'm currently using axis 1.4, but might decide to switch to axis2 if
the
> subject calls for it.
>
> I even got a working example using the javax.activation.DataHandler as a
> parameter to my service method to pass the attachment. The thing is the
wsdl
> generated by axis is clearly not generic (it marks the parameter of type
> "apachesoap:DataHandler").
>
> Can anyone shed some light on the subject? Pros and Cons for the
different
> options and some reading resources, I found lots of bits of knoledge but
> nothing giving a bigger picture….
>
> Thanks,
>
> Uri.


--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to