Hi mathieu,
The meaning of the error that you are getting is that our data binding
framework, ADB, is expecting a particular element, but it is receiving
the header element (I presume SOAP header element).
If you are extracting the SOAP message from the XMPP transport and
setting that to the
Hi,
you say :
You need to extract the SOAP message from the XMPP message and then need
to set the SOAP message to the the message context.
but i do that thing on the server side. And after, i give the message
context (which is complete) to the axis engine (receive methode).
And this is when i
Mathieu
You might want to look at the refactoring that Asankha did for creating
Axis2 transports. I believe he has tried to create some simple base
classes you can extend. The code is in the Synapse tree, but the results are
pure Axis2.
On Nov 7, 2007 12:42 PM, Deepal jayasinghe [EMAIL PROTECTED] wrote:
mathieu fabre wrote:
hi,
I would like to implement my own transport in xmpp (jabber)
i write a XMPPTransportSender and a XMPPSimple Server like for the
http transport.
i add these sender and receiver in the axis2.xml
hi,
I would like to implement my own transport in xmpp (jabber)
i write a XMPPTransportSender and a XMPPSimple Server like for the http
transport.
i add these sender and receiver in the axis2.xml config file.
The client extract the soap message from the messageContext and send it to a
chat (in
mathieu fabre wrote:
hi,
I would like to implement my own transport in xmpp (jabber)
i write a XMPPTransportSender and a XMPPSimple Server like for the
http transport.
i add these sender and receiver in the axis2.xml config file.
Well we have already implement the XMPP transport , will
