You call it an inconvenient, but it may be a blessing. I think they should be totally separate, that is, different container instances running, one for Axis2 and one for Axis1. This would allow them to run on different machines or even in different domains. It also brings up security concerns, in that the instance running Axis2 that communicates with the client may have much tighter security requirements than the web service Axis1, which is completely internal. The separation allows your production support people more flexibility.
Having said that, I'm sure you probably could get both Axis1 and Axis2 running in the same Tomcat instance, or whatever container your running. But I think it would introduce problems down the road. Since all of the libraries are named differently between Axis2 and Axis1, and I believe you can use the same jdk version for both (since jdk's tend to be very good at backwards compatibility) and also considering that the Axis source code is a neatly packaged web application, in theory I think you could get them to run side by side, but again, I doubt it's good archjitectural practice to do so. Regards, -jeff -----Original Message----- From: Alberto Patino [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 12:26 AM To: [email protected] Subject: Re: rpc-encoded vs rpc-literal vs document-literal migrate Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit OK, I got the point. Thats exactly the the way the ESB would decouple the axis2 document/literal service from the axis1 rpc/encoded. I only see an inconvenient: I'll require an axis1 engine resident in its own servlet container, could it be the same servlet container that holds the axis2 engine? Would it be a good practice? Thanks On 7/30/07, Walker, Jeff <[EMAIL PROTECTED]> wrote: > I wouldn't try mixing Axis2 with Axis1 libraries in the same deployment. > Sounds like a recipe for disaster. > I'd recommend a Composite web service design. > The first web service is Axis2-based and that is exposed to the Client. > This uses SOAP 1.2, WSDL 2.0 and doc/lit for comms (whatever latest and > greatest specs you want, really). That Axis2 service is a client of a > 2nd service, which is Axis1 based (it is a totally separate deployment). > This uses SOAP 1.1, WSDL 1.1 and doc/lit for comms between the two > services. > That Axis1 service is a client of the final RPCEncodedService, comms > between these two is SOAP 1.1, WSDL 1.1 and rpc/encoded. > -jeff > > > -----Original Message----- > From: alpatino2 [mailto:[EMAIL PROTECTED] > Sent: Monday, July 30, 2007 11:17 AM > To: [email protected] > Subject: Re: rpc-encoded vs rpc-literal vs document-literal migrate > Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit > > > 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-mig > rate-Axis1.4-wsdl-%28rpc-encoded%29-to-Axis2-doc-lit-tf4113634.html#a118 > 65674 > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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] > > -- Don't be evil!!! --------------------------------------------------------------------- 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]
