Yep, thanks Dims. The part of
"write it directly to the http stream" is what I need to verify. Thanks to both you and Thilina. Sorry I wasn't able to be more clear in the very beginning. Davanum Srinivas wrote: > Chad, > > Take a deep breath and start from scratch :) > > You a WSDL with a Schema with an element whose schema type="xsd:base64Binary" > [See http://ws.apache.org/axis2/1_2/mtom-guide.html, search for MyBinaryData] > > When you run WSDL2Java and review Base64Binary.java, it will have a > setBase64Binary/getBase64Binary with DataHandler as the parameter > > In either your client or service, just use say a file backed > DataHandler to send the data. Your file will have binary data (NOT > base64 encoded). > > At runtime, *IF* you have enabled MTOM in axis2.xml or as a property > in options on the client side, the engine will create a mime separated > stream with the soap xml in the root mime part and will ask *your* > data handler for the binary stream and write it directly to the http > stream. > However if MTOM is *disabled*, the engine will try to base64 encode > the *WHOLE* byte stream from your data handler and create a giant text > node inside the SOAP request/response. > > Is the process clear now? > > thanks, > dims > > > BTW, I don't recommend HTTP/SOAP for multi-gig content > > Step #2: When you run WSDL2Java *USING ADB data binding*, > > On 8/5/07, Chad La Joie <[EMAIL PROTECTED]> wrote: >> Thilina Gunarathne wrote: >>>> If, as we discussed in the first part of this thread, Axis2/Axiom >>>> supports true end-to-end streaming, and Axiom can correctly stream >>>> content from/into a DataHandler, what causes problems for arbitrarily >>>> large files? >>> Problems like what.. AFAIK it does not cause any problems. >> I don't know what the problem would be. You said >> >> "Do you want to send/receive binary in base64 form.. If so it won't >> tolerate large files.." >> >> So, I was trying to find out why it wouldn't tolerate large files. >> >> May be we >>> can hep you a bit if you state your use case clearly. >> I thought I had, or at least I tried. Let me try a third time. >> >> I have a SOAP body with an element defined as: >> >> <element name="foo" type="base64Binary"> >> >> I need support for putting multi-gig (pre-base64 encoding) content in >> that element and transporting over HTTP w/ MTOM. I'm trying to be >> obtuse, but I don't know what additional information I need to give either. >> >> At this point I'm really just trying to verify the large-content case >> over MTOM. >> >> -- >> Chad La Joie 2052-C Harris Bldg >> OIS-Middleware 202.687.0124 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- Chad La Joie 2052-C Harris Bldg OIS-Middleware 202.687.0124 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
