Hi Thilina,
Thanks for comments.
I have make enabled SwA support in Axis2. It seems that I cannot enable both
SwA and MTOM at the same time.
If the attachment is very big, will base64Binary introduce more performance
penalty?
Regards.
Xinjun
On 5/10/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Axis2 supports Java2WSDL only for MTOM...
> String uploadFile(String userID, String fileName) {}
Try changing the method as follows,
String uploadFile(String userID, DataHandler file) {}
> My second question is:
> What will be the differences between MTOM and SwA in terms of Web
Service
> implementation class (the signature) and the WSDL?
It's not trivial to capture the SwA details in the WSDL... Axis2 does
not support it either..
On the other hand specifying a MTOM compatible WSDL is trivial.. You
just need to specify a element with the type base64Binary...
> Another question about attachment is about interoperability.
> From Axis2 user guide, MTOM is much better than SwA. However, MTOM is
not
> WS-I Basic Profile 1.0 or 1.1 compliant.
I don't think MTOM was there when they are doing the basic profile ;)...
>Will there be any issue if my web
> service uses MTOM and the client uses .NET or other non-Axis2 SOAP
toolkit?
Most of the newer stacks including WCF (.net) supports MTOM..If you
are looking for a futuristic approach then MTOM is the choice..If you
are looking for support from the older stacks, then SwA is the choice.
Thanks,
Thilina
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
