Actually, it sounds like you are getting XML-RPC (XML requests over HTTP POST), not SOAP. Using Axion SOAP to receive non-SOAP messages is going to be hard. You should probably look at the XML-RPC project, AND ask what standard the other application is sending you XML in.
Tom > From: Brian Fliege [mailto:[EMAIL PROTECTED]] > Sent: 05 February 2003 19:38 > To: [EMAIL PROTECTED] > Subject: Messages, Handlers, and Architecture > > > Hello everyone, I am architecting an XML application and would > really love to use Axis, but my prototype has run into a big snag. The > application my team is working on accepts XML messages over an HTTP > transport. Various unwrappings and transforms need to be performed > before the messages are acted upon. I have been experimenting with Axis > because the handler chains that can be defined match PERFECTLY with the > kinds of transforms our application needs to do. > > Based on the types of services that can be implemented with Axis, it > looks like "RPC," "document," and "wrapped" message styles would not > work in my situation. I have been experimenting with the various > methods available to "message" style services, but it seems to me that > each and every one (or possibly the Axis servlet?) wants the incoming > XML to specifically be SOAP (wrapped with > <SOAP:Envelope><SOAP:Body>...</SOAP:Body></SOAP:Envelope>). Our > messages are non-SOAP XML documents and simply telling the other end to > wrap everything in SOAP tags will not work because we have no control > over the sender. > > Is there a way I can still take advantage of receiving and passing > an XML DOM down a handler chain and NOT have it wrapped in a SOAP > document? > > -Brian > >
