Hi, I don't know if there was or is a change in the way Muse send messages out?
As long as Muse uses http connectors to write outgoing messages, there will be no way to use the Rampart module of Axis2. This will be only possible if Muse sends the outgoing messages trough Axis2 and uses the Axis2 engine. To use WSSE in the outgoing direction you have to setup the WSSE header yourself and overwrite the Muse classes to allow the addition of the header parameter. Hopes this helps. Matthias -----Ursprüngliche Nachricht----- Von: alfredo.s.g_uam_spain [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. Dezember 2007 11:48 An: [email protected] Betreff: RE: AW: axis2 deployment and configuration Im now trying to do this task and i found out that for sending notifys with muse is a little more complicated to add the ws-security. Has someone made it and can give me some guidelines to force muse to use axis outgoing or to force muse to use ws-security somehow? for incoming soap messages with ws-security is much easier ¿isnt it? thanks Daniel Jemiolo wrote: > > I recall a number of other users having success setting up the WS-Security > module in Axis2 (w/ Muse). In fact, I think Matthias (the other > participant in this thread) is one of them. I don't think you'll run into > any issues, but if you do, please report them so we can fix Muse and allow > the WS-Security module to work as expected. > > Dan > -- View this message in context: http://www.nabble.com/axis2-deployment-and-configuration-tp9736934p14271129.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
