Thanks for the information. About the problems with MTOM and Rampart I didn't want to mean that I had problems with it. Sorry if I expressed badly. I meant that I think I read about that in this mailing list.
About Base64 encoding not being necessary when sending files as attachments outside of the message: I thought it was mandatory to use with MTOM as I saw it in the sample that comes with axis2. So then, how can I indicate in the WSDL that I'm sending attachments??? is there any sample?? I had read the mtom-guide but I think I hadn't understood it well. So If I use rampart It will be working with both MTOM and SwA?? Regards, Jorge Fernández Thilina Gunarathne <[EMAIL PROTECTED]> escribió: > Also I want to secure my message also and I found that Rampart and MTOM have > memory problems. Not that I know.. Can you please be more specific and report these problems with samples or test cases, so that we can fix if there is any.. > - When I used ADB and MTOM I could see that if I don't enable MTOM, the > attachment is sent in binary code as a String inside de SOAP message but if > I enable MTOM, it's send outside the message in clear text (I used an xml > file as example of attachment). I would like to send the attachment outside > the message in binary code. Is this possible?? Attachment will be send in whatever the original format when it is sent as an attachment outside of the message. So XML will appear as it is.. Base64 encoding is not necessary when sending files as attachments outside of the message. > - I know that MTOM is better than SwA, but what are the reasons? Please read the introduction part of http://ws.apache.org/axis2/1_2/mtom-guide.html > > - Is there any limit in the size of messages that axis2 can send, I mean > in both the envelope and as attachments?? I'll have to send huge arrays of > int or other data. I'll have to send some of them as attachments to avoid > the multiple tags the xml would generate. There isn't a limit enforced by Axis2.. You might have to carefully select/write your data sources to deferred read your data in to the memory. In other words make sure they load them to the memory only when writing to the given OutputStream of the getOutputStream method. > - The last one: As I'm building big messages, I'm having memory problems > and I would like to know if axis can build this messages in parts, like > build the first part of the message when it reach a limit size and send it, > then build another one and send it...... Use HTTP chunking... I have successfully send attachments larger than 700 MB with HTTP chunking enabled and using FileDataSource, since I read the data off a file.. Thanks, Thilina > > Any help will be appreciated. > > Thanks in advance, > > Jorge Fernández > > > > Jorge Fernandez escribió: > Hi all, > > I would like to know if it's possible to use XMLBeans and Rampart with > attachtments cos I heard that XMLBeans doesn't support MTOM and I doubt if > Rampart supports SwA or there is any problem in that combination. > > Thanks and regards, > > Jorge Fernández > > > ________________________________ > > LLama Gratis a cualquier PC del Mundo. > Llamadas a fijos y móviles desde 1 céntimo por minuto. > http://es.voice.yahoo.com > > > ________________________________ > > LLama Gratis a cualquier PC del Mundo. > Llamadas a fijos y móviles desde 1 céntimo por minuto. > http://es.voice.yahoo.com > > -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
