All, >From what I can gather -- wrapped services are simply a clever hack to buy me >rpc-like functionality via a doc/literal service? Seems like a dangerous leg to >stand on considering that it's not standard (regardless of msft defaults ;)) and the >interpretation of what represents a wrapped service is left to the framework (even >though there's a general understanding).
That said, if I go pure doc/literal, I'm likely to be handed the root of the envelope by Axis (is this the case?) as opposed to anything representing the object I'd like to marshall into. Seems like JAXB might play a nice role in marshalling this raw xml for me? I'm basically wanting to move away from our rpc/encoded services we're deploying now and into doc/literal but still have the convenience of rpc -- seems like wrapped is the only way to go, but a non-standard way at the same time. Comments anyone? Cory
