If your attachments will be several megabytes, you might benefit from using Axis. Apache SOAP still creates an image of the whole payload in memory, which gets to be a problem with large attachments. While improving this is on the to-do list for SOAP, I do not know when it will be done.
I personally think the most compelling feature of Axis is support for WSDL. If you want to write clients to consume WSDL-based services, it's great to have the tool create proxies for you. The WSDL generation for services is great, too, but you can use the Axis tool to generate WSDL for Apache SOAP services, so that alone is not a reason to switch. Down the road, of course, you will certainly want to be using Axis, since it will evolve with the SOAP and WSDL specs, while Apache SOAP will remain a SOAP 1.1 implementation. Scott Nichol ----- Original Message ----- From: "Praveen Peddi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 08, 2003 3:56 PM Subject: Re: Urgent: Soap With attachments example > Thanks a lot Scott. > If nothing works out, I will pass in some dummy bytes and work around. > > Once again I really appreciate your help. > > Do you think its better to migrate to Axis, since we are using attachments > extensively. Whats your suggestion? > > Thanks > > Praveen > ----- Original Message ----- > From: "Scott Nichol" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, January 08, 2003 3:12 PM > Subject: Re: Urgent: Soap With attachments example > > > > Ugh. I never noticed that the admin GUI does not allow one to specify a > > fault listener. > > > > To get to the bottom of this, I wrote my own sample client and service. > > I got the "no signature match" error when I passed a null DataHandler, > > because the Apache SOAP code serializes a DataHandler as xsd:anyType, > > which is always deserialized as an Object. I am not sure why you do not > > still see this message, too. > > > > Anyway, I made a small change to SOAPMappingRegistry so that a null > > DataHandler can be properly serialized and de-serialized. If you pick > > up the next nightly build, you will get that change. Both your client > > and server will need the new code. > > > > Scott Nichol > > > > ----- Original Message ----- > > From: "Praveen Peddi" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, January 08, 2003 11:44 AM > > Subject: Re: Urgent: Soap With attachments example > > > > > > > Even though I have a deployment descriptor and the line > > > > > <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultLis > > tene > > > r> is in a separate line, I deployed the services using the soap admin > > > client that apache provided. I got NoClassDefFound errors when I tried > > to > > > deploy using deployment descriptor. > > > > <<snip>> > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
