Simplified and Solved some Issues had in provided links in last email.

[1]
https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/SynapseDebugInterface.java
[2]
https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/SynapseDebugManager.java
[3]
https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/SynapseDebugFlag.java
[4]
https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/AbstractMediator.java
[5]
https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/AbstractListMediator.java

Regards
Kevin


On Fri, May 16, 2014 at 5:28 PM, Kevin Ratnasekera
<[email protected]>wrote:

> hi all,
>
> I was busy with my academic work as I am completing my Internship period,
> from now on i will be able to give more time and effort this project. As we
> discussed I am currently implementing the extension point to ESB runtime to
> support debugging according to deliverable 1 in my proposal. In my proposal
> I have defined a protocol of messages exchange between the ESB and debug
> framework. I have defined two TCP channel according to the communication
> protocol. One TCP channel is sending Debug commands ( stop, resume, set
> breakpoints ) and the other one is send Debug events which makes the ESB
> and debug frame work work together to provide synchronization ( started,
> terminated, resumed etc) . I have implemented the deliverable one according
> to the  protocol defined.
>
> [1]
> https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/SynapseDebugManager.java
>
> [2]
> https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/SynapseDebugConstants.java
>
> You can review the code here with the provided links. I have refactored
> the code coding standards and I have tested the code to some extent. As I
> said the day we discussed offline It is necessary to slightly change the
> implementation of AbstractListMeadiator.java and AbstractMeadiator.java
> classes current implementation.
>
> [3]
> https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/AbstractMediator.java
>
> [4]
> https://github.com/djkevincr/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/AbstractListMediator.java
>
> You can have a look on those with the provided links.
> I am currently implementing a TCP client exhibit sample debug session
> scenarios for simple sequence configurations withe several mediators. I am
> working on this throughout this weekend, hopefully I will be able to come
> up with several test scenarios and update the the progress in next few days.
>
> As I was advised by the mentors recently, I will put more concentration on
> the at the ESB runtime end before moving in to the Eclipse debug framework
> and related UI. I will test it's full functionality thoroughly for
> different debug sessions scenarios as the sequence configuration complexity
> increases before moving on.
>
> Regards
> Kevin
>
>
>
>
>
>
>
>
> On Sun, May 11, 2014 at 9:10 AM, Isuru Udana <[email protected]> wrote:
>
>> Hi Kevin,
>>
>> As we discussed offline few days ago, could you please update the thread
>> with the current progress.
>>
>> Thanks.
>>
>>
>> On Mon, Apr 28, 2014 at 12:28 PM, Viraj Rajaguru <[email protected]> wrote:
>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>>  Senior
>> * Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: [email protected] cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to