Yeah.. we might be not able to use the current wire-log implementation for do this but we need to find a way how we can pass the wire level message as part of the ctx.
On Tue, Apr 5, 2016 at 9:30 AM, Isuru Udana <[email protected]> wrote: > Hi Kasun, > > TRANSPORT_HEADERS case is somewhat different, because we have access to > the all the transport level headers from the HttpRequest coming from Http > Core level, but for the entire message we won't be able to take that > approach. > > Thanks. > > On Tue, Apr 5, 2016 at 9:24 AM, Isuru Udana <[email protected]> wrote: > >> Hi Kasun, >> >> It is not possible to make it a part of the message context as we don't >> have access to any context at the Wire level (Not even the http core level >> context). >> >> >> On Tue, Apr 5, 2016 at 9:11 AM, Kasun Indrasiri <[email protected]> wrote: >> >>> Can we have wire level message information as part of the message >>> context (Of course we have to do this only if debugging is enabled or >>> something), so that we can correlate message and its wire level message >>> while debugging. >>> >>> >>> On Fri, Apr 1, 2016 at 9:46 AM, Rajith Vitharana <[email protected]> >>> wrote: >>> >>>> 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/ >>>> >>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> >> -- >> *Isuru Udana* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> > > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
