Hi, I have written a XMPP transport for Axis2/Java [1]. I am planning to submit a patch soon. Right now I do not have the full spec complacency. But you can call Axis2 web service from a Axis2 client using XMPP as the transport & get the response using the same.
/sumedha [1] http://ws.apache.org/axis2/ On 8/22/07, Jonathan Dickinson <[EMAIL PROTECTED]> wrote: > > If you want your server to expose a SOAP endpoint you will need a > plugin, otherwise you could always have a custom Jabber client and have > JIDs like [EMAIL PROTECTED] and [EMAIL PROTECTED] > > It makes more sense to make the server JID (e.g. bank.com) the SOAP > endpoint, but that isn't always possible: as it seems to be in your case. > > Furthermore, I would recommend you alter your SOAP framework somehow, > because SOAP is stateless where XMPP is stateful, you can leverage this > to your advantage (in my honest opinion, XMPP is better suited to Remote > API than HTTP). E.g. most SOAP endpoints require a login of some form, > you can have the user log in once using a Login method instead of > sending credentials/tokens each time another method is called. > > Good luck! > > Devraj Mukherjee wrote: > > Hi everyone, > > > > I am a new to Jabber development, and am trying to carry SOAP messages > > over XMPP. I noticed the SOAP extension to XMPP on the XMPP web site. > > > > My questions is do Jabber servers require additional > > plugins/implementations to carry SOAP messages across or can any > > standard Jabber server be able to carry the message? > > > > Thanks. > > >
