I find it easier to think of SOAP as something more like JMS than RMI. That gets you into the mindset of document-oriented messages and loosely coupled connections and away from the distributed objects mindset. Nonetheless, Axis1/2 will happily generate an interface that looks and feels more like RMI. The catch is that Axis1/2 doesn't support a lot of features that you should expect from a distributed object system, like remote references. It's just something to be aware of.
Using document-oriented messages doesn't force your application to manipulate the SOAP message directly. Axis 1/2 will convert the messages into Java objects for you. My point is that SOAP is a very heavy protocol, so it's a good idea to create "chunky" rather than "chatty" interfaces -- you want to reduce the number of message exchanges, so you don't want to expose getter and setter methods on each object attribute.
If I haven't answered your outstanding questions, please ask them again.
Anne
On 5/8/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
I figured out a lot of my problems were infact a result of the WSDL. I have updated it to get more of what I want. My last post still has some questions in it that are valid.
Michael MacFadden
Tomax Corp - http://www.tomax.com
[EMAIL PROTECTED]
