2009/3/28 Emmanuel Lecharny <[email protected]>: > Ashish wrote: >> >> On Sat, Mar 28, 2009 at 5:50 AM, Emmanuel Lecharny <[email protected]> >> wrote: >> >>> >>> Hi guys, >>> >>> another things we discusses with Jean-François was about how to debug. We >>> agreed that the current core does not have enough logs (well, 'not >>> enough' >>> is already a huge exageration ...). If we could only trace a session ... >>> >>> So we need to add some more logs in all parts of the core to help our >>> users >>> - and us if users come to us with questions - to get a clue on what's >>> going >>> wrong. >>> >> >> Agreed. >> There's one more thing that we can add to wiki for our user's/developer's. >> MINA runtime view. How does the application behave once running. Let >> me explain a bit further >> We know about the Acceptor-FilterChain-IoHandler, once running we get >> different view like sessionCreated is called all the way in one thread >> and how filter chains are per session etc etc. In a nut shell, how >> MINA internal works. At time, I am also lost. >> > > I have done some cool test with a tool named jip. Basically, it traces all > the methods calls in and out, so you can see which path you are going > through. >
Great! Had a brief look at the tool. A very nice use of AOP. Will try to use it on couple of programs and try to create some sequence diagrams out of it. thanks ashish
