Thanks for the help, I see the necessity to use axis1, now what do you think is the best way to invoke this rpc/encoded service, I want to write a higher level service in axis2 using document/literal style, and inside of this service invoke to the rpc service, but I think I need to mix axis1 and axis2 libraries, I know I could decouple service invokation using a ESB, but I cannot afford to use this.
Client--->Axis2 (Doc Literal)Service --> rpc/encoded __________________________ |--> doc/literal __________________________ |--> ???? Thanks again Use Axis 1.4 instead. Anne On 7/30/07, Philipp Leitner <[EMAIL PROTECTED]> wrote: > AFAIK Axis 2 does not support RPC/encoded at all since it is not WS-I > compliant. > > /philipp > > alpatino2 schrieb: > > Hi! > > > > I have a slightly different requirement: I received wsdl's from a > service > > provider that implements the TR-069 spec, this spec define the use of > > rpc/encoded style. I need to invoke this service but I am not able to > > generate the client, I tried to generate the client for the sample > > stockAvailableNotification.wsdl extracted from the Building Web Services > > with Java book, but I get the following error: > > -- View this message in context: http://www.nabble.com/rpc-encoded-vs-rpc-literal-vs-document-literal-migrate-Axis1.4-wsdl-%28rpc-encoded%29-to-Axis2-doc-lit-tf4113634.html#a11865674 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
