[ 
https://issues.apache.org/jira/browse/SYNAPSE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640199#comment-13640199
 ] 

Thilini Shanika commented on SYNAPSE-928:
-----------------------------------------

Hi all,
I'am a final year undergraduate from Computer Science and Engineering 
Department, University of Moratuwa. I got opportunities to work in projects of 
Apache Software Foundation, during my 7 months of internship period. Apache 
Synapse and Axis2 related projects are the projects that I was involved in. 
Since that I have a good understanding of Synapse code base and features. 
I have a interest on working on this project. According to my understanding, it 
is required to study and understand the logic of deployment and persistence of 
Synapse artifacts like proxy services, sequence, endpoints etc to proceed in 
this project. Thus, currently I'm working on debugging the code base. Apart 
from that, a major architectural change is required to achieve this target and 
for that, please provide further instructions.

Thanks,
Thilini
                
> [GSoC] Versioning of Synapse config artifacts
> ---------------------------------------------
>
>                 Key: SYNAPSE-928
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-928
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Kasun Indrasiri
>            Priority: Critical
>              Labels: gsoc2013
>
> Currently non of the synapse artifacts fully support versioning mechanism. 
> This feature is to support a new versioning strategy for all such artifacts. 
> Sequence, Proxy Service, API, Endpoints 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to