This is a wild gess here. Based on one document/page on the web, it says that there are essentially 2 styles: document and rpc. Message style is a "programming" style. From there, my thinking is that messaging style can be just Document style. However, you'll send in an array of dom's elements as parameters, and also retrieve an array of dom's elements as returned value. Attachment appears to be the same (because these styles are in the body of the soap message (must be xml), while attachment is a separate part (binary/text/xml/anything).
So, with respect to attachment, there is nothing changed if you follow the echo attachment tutorial (maybe with little change, but the concept is the same). With respect to the messaging style, you can look at the messaging tutorial, very straight forward. What I "hope" is that Axis would actually translate/wrap all this stuff for you, and you can just call using the generated stub, as long as you specified them as Document.
These are reasoning. I haven't code in messaging with attachment. Someone with more familarity with these area please help or correct me.
Thanks.
P.S. the document/webpage I referred to above is:
http://www.possibility.com/epowiki/Wiki.jsp?page=SimpleAxisServer
Here's the quote:
The SOAP and WSDL standards define two styles of service -- document and rpc. The Axis WSDD style parameter defines the *programming* style rather than the service style. "Message" = messaging style (application performs marshalling/serialization) "Document" = object style (runtime accepts/returns objects) "Wrapped" = parameter style (runtime accepts parameters/returns return value and parameters) "RPC" = parameter style using RPC service style
Most SOAP implementations support all of these programming styles, although they don't necessarily use these specific names. The most important thing to understand is that WSDD is not standard. A lot of Axis users develop services starting with the WSDD rather than WSDL. There's bound to be some lock-in when you use this approach. It's always a better idea to start with WSDL.
Tomcat and Resin don't provide a built-in Web services platform. Axis runs in both these servlet engines -- in fact Axis runs in almost any servlet engine.
Eyad Garelnabi wrote:
Thanx for the heads up. After reading up on the difference between the two, it became apparent to me that I'm interested in MESSAGE style. How does this change the way I would send the attachments?
Thanx a million
-----Original Message-----
From: WAJSBERG Julien RD-BIZZ [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 3:25 AM
To: [EMAIL PROTECTED]
Subject: Re: desperate newbie-- trouble with image attachment
Vy Ho a écrit :
Looking at the reference for Java2Wsdl, there's this line:
-y, --style The style of binding in the WSDL, either DOCUMENT, RPC, or WRAPPED.
That means you can pass in DOCUMENT as the style when generating the wsdl to say that you want DOCUMENT style messaging.
Be careful to know whether you want Document style or Message style.
