Hi Erwin, Axis2 can act as a client and/or a server, the two endpoints in a message exchange, without any problem. Axis2 has all the capabilities to work as an intermediary also, but it just that you have to do some amount of work to get it working the way you want.
Synapse is all about mediation and meant to be act as an intermediary. So Synapse had done the above mentioned part already. I always think Axis2 as the client/ultimate receiver vs Synapse as the intermediary for a good application. Intermediaries are somewhat common these days. For example, a company might decided to get all the messages to one node and then route to different internal hosts, applying some policies. Or even might wanna log all the messages. There are lots of samples like this. On Thu, Jun 5, 2008 at 4:49 AM, Erwin Reinhoud <[EMAIL PROTECTED]> wrote: > Hello All, > > What is current support in Axis2 for intermediaries and the application > of the SOAP actor? A while back i was told it is not possible yet to > have intermediars and assign (ws-security/ws-addressing) headers to an > intermediary and leaving the body and possible other headers to the next > hop. Or is this supported by synapse? Is this scenario often applied, > because i cant find much about it (anybody have references)? > > Thanks in advance. > > Kind regards, > Erwin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- With Mettha, Eran Chinthaka -------------------------------------------------------------------- Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
