As I recall, the reason for this was that we hand off the SOAP body to Axis2, and it handles the final construction of the SOAP message before putting it on the wire. So we don't have the final SOAP message to log. Of course, we know what the headers should be, and we have the body, so we *could* construct an envelope DOM just to log it, but a) this might be a performance hit, and b) it could be confusing to debuggers should Muse and Axis2 ever "disagree" on what the final SOAP envelope should look like. The first one could be worked around by checking the logging level and only doing it if the level were high enough (FINE), but the second one seems problematic. I'm not sure what the Axis2 logging setup has to be to get it to display the SOAP messages - have you been able to get this working?
Dan "Beil, Matthias" <[EMAIL PROTECTED]> wrote on 04/18/2007 10:19:33 AM: > Hi, > > > > I just tried to have on the server side (tomcat 5.0.28) the soap > messages logged. While the incoming message is logged (line 118 Muse > 2.2.0) I found that there is no logic for this for the outgoing message > :-( > > > > While the simple log based logging works, the logging using log4j didn't > work. > > > > Mit freundlichen Gruessen / With kind regards > > Matthias Beil > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
