Hi, I was able to simply show the wire log (what is just written to the wire) as a property when a debug point get hits, But in that case there are some drawbacks, such as we can't see back end call wire logs because we can't set debug point just after back end call happens, (we can see back end response but not back end request) and also we can't see the final response to the client as well(due to the same reason).
But if we can just print the wire logs (as already doing when wire logs are enabled in ESB) in Developer studio side when something gets written to the wire, IMO that would be more usable, If we are going to do that, we will have to figure out a way to filter the wire logs for that specific service only(which is being debugged) otherwise it will show everything which get's written to the wire. WDYT? Thanks, On Thu, Mar 31, 2016 at 10:54 AM, Kasun Indrasiri <[email protected]> wrote: > Hi, > > We came across a sort of a mandatory requirement for debugger : debugging wire > level message from the visual editor. We need to figure out how to > represent this visually + implement this at the core engine level (probably > propagate these transport level information to the mediation level). > > With this feature, the debugger can be used to design/debug complete end > to end message flows in ESB. > > Thanks, > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
