I have an old 'C' application that reads a SOAP message directly from a TCP socket processes it and builds a SOAP response that it sends back.
This has been structured such that the client process can be built using a standard WSDL file that is created by the 'C' app for that purpose. Thus the 'C' app can be front-ended by many of the web dev tools that are available. Obviously the 'C' code handles processing all the XML/WSDL content in the SOAP request and response and performs varying operations depending on what exactly is in the request part. Whilst this has been OK on a local LAN I'd like to bring the app under Axis for many reasons and future capabilities. My problem is I really don't want all the serializing to and from Java classes that Axis will do for me because effectively the app already handles the SOAP message decoding/encoding. I've had a look at the Axis C++ interface but again that seems to be doing serialisation to/from classes. Also at this stage I don't want to have to deploy several hundred Java servers. So the BIG question... Is there a way I can let the Axis server communicate with the client process (just like normal) to receive the SOAP message but then short-cut the usual processing and simply pass the SOAP out to the 'C' app and finally have Axis return the SOAP response? Many thanks for any thoughts/help you can offer Tim. -- View this message in context: http://www.nabble.com/Passing-the-SOAP-WSDL-message-to-an-external-C-app-tf4024781.html#a11432069 Sent from the Axis - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
