> Also, I'd like to keep my web services portable to different JAX-RPC > implementations, so I try to avoid Axis-specific features > (e.g., Message-style > services.) >
Just curious, but why? Are you constructing a service that you are planning to sell or that will need to be installed in many different JAXRPC implementations? Or have you (your company) not decided upon an implementation yet? As I've said before, I'm new to webservices, but I am under the impression that they are simply a deployment tool; an interface to the "real" code. If that's the case, why not use whatever is specific to the implementation if it makes it easier/better to deploy (and is, of course, standard)? It's not going to change the functionality of the service. Or (having an epiphany), is it that using implementation specific functionality can have a negative affect on the implementors of the service's clients? If that's the case, then I understand the reluctance. I'm sure interested in your (and anyone else's) thoughts on this. Gene
