Support for SOAP encoding requires a significant development effort and IMO is not a high priority. (There are lots of much more critical features that definitely have a higher priority, in any case.) SOAP encoding is not permitted by WS-I, and it is an optional feature in SOAP 1.2. Given than Axis2 is a third generation service engine, aimed at addressing the future requirements of web services, SOAP encoding just doesn't fit. People that need to support SOAP encoding should use Axis rather than Axis2.
Note that Sun's JAX-WS RI doesn't support SOAP encoding, and they have no plans to add support for it either. You must use the JAX-RPC RI instead. But -- if you feel this is a higher priority than I do, please recruit a team to develop the code. Anne On 9/26/06, Al Baker <[EMAIL PROTECTED]> wrote:
Hi, I was wondering if there is a way to have a single web app serve out both an rpc/encoded service and a doc/literal service? The use case I'm looking at is to support backwards compatibility and not force a huge upgrade for all clients. On a related note, when will Axis2 support rpc/encoded? Thanks, Al --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
