messaging body?

[GARG Shishir FTR&D <sh...@rd.francetelecom.com>]

SOAP: Simple Object Access Protocol.

While this is a good definition, there are some things I don't understand at
a logical level about what we're doing.

So, we can expose methods on the server side, and expect the client to make
RPC calls using the SOAP-envelope, by putting the relevant XML data within
the SOAP-Body.

So far so good.

In the Apache-SOAP implementation, and specifically, in the addressbook
example, we have defined objects that we use to represent the XML data, like
Address.class and Phone.class to represent the data that we want to
transfer.

I've not gone through the code, but I assume that the data that's being
serialized over the wire is the Object, rather than the raw XML that it
represents. 

Here's where the confusion kicks in: For each client-server transaction,
we're going to generate a new XML body. These could get pretty complex too.
Is there a way for us to either:

- Pass the XML to a processor that creates the objects at runtime and passes
them across (I can see obvious performance concerns)
- Pre-generate these objects to be instantiated at runtime (like what's
happening now, but the generation of those objects should be automated!).

I hope I've expressed myself clearly. Does this make ANY sense?

Thanks.