Hi,
On Mon, Apr 28, 2014 at 2:59 AM, Kevin Ratnasekera <[email protected]>wrote: > Hi all, > > I would like to thank WSO2 community for accepting my proposal for $subject > for > GSOC 2014 and specially thankful for WSO2 ESB and DevStudio Team for > helping me out to come up with the proposal. I am pleased to work with you > as my GSoC project mentors at the same time being part of the WSO2 > community. > > Past few weeks I have been following working examples of debuggers written > using eclipse debug framework in order to get good understanding of how > debug framework can be used to develop custom debuggers.[1][2][3] Also I > have covered to some extent of eclipse debug API documentation. > > As mentioned in my proposal, I have implemented to some extent deliverable > 1 ESB extension point to plug ESB to a debug plugin as according to the > communication protocol defined. During the community bonding period I would > like to continue working on the deliverable 1 with WSO2 coding standards > and test it s functionality using a Simple Java TCP client with ESB server > runtime without testing it s integration with the eclipse debug as it is > not completed yet. > > Also I have studied Eclipse launching framework and documentation to some > extent and I would like to continue studying on them more during the community > bonding period. Also I have gathered some background knowledge on how to > instantiate WSO2 ESB instance inside a java program so that it would help > me to write the launch delegate class which is the core of the ESB launcher > for debug plugin. I also encountered some problems I would like to share > them with you too.[4] > > Without Integrating the debug plugin to be working with DevStudio > graphical editor, as a starting point I would like to work towards, to set > break points using the the eclipse default AbstractTextEditor for synapse > configuration xml. As this would help me test the full functionality and > also it is convenient as there is default implementation is available for > line based/oriented breakpoints in the debug framework it self. This may be > further extended to set breakpoints using devStudio graphical editor. > In ESB graphical editor plugin we have a source editor which is extended by "org.eclipse.wst.sse.ui.StructuredTextEditor". This 'StructuredTextEditor' class has been extended by "org.eclipse.ui.texteditor.AbstractTextEditor". You can use ESB graphical editor's source view/editor to set breakpoints for synapse configuration xml at the initial stage. Thanks, Viraj. > > These are the things I am working within this community bonding period > before the GSoC coding period starts.Comments and suggestions are really > appreciated. I have presented them briefly and I would like to discuss them > more with you. If you want anything further to clarify just please let me > know. I would like to start work on them early so it that it spare enough > time for me to complete the project. > > [1]eclipse debugger for perl interpreter > http://www.eclipse.org/articles/Article-Debugger/how-to.html > [2]eclipse debugger for Embedded systems Software > http://fmt.cs.utwente.nl/files/sprojects/22.pdf > [3]eclipse debugger for text interpreter > > http://codeandme.blogspot.com/2013/11/debugger-3-tale-of-debuggers-processes.html > [4]Launcher for JAVA applets. > http://www.eclipse.org/articles/Article-Launch-Framework/launch.html > > Regards > Kevin > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
