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

Asankha C. Perera commented on SYNAPSE-618:
-------------------------------------------

Hi Denis

> Regarding [1] , My mentor Milinda Pathirage on ODE-565 redirected Marco to me 
> and he started to personally contact me,..

There seems to be many issues here.. 

1) I do not see anyone requiring redirection, as Marco asked a question on the 
public mailing list - to which no one has replied yet, when anyone could have 
replied - even directing Marco to you, publicly

2) Open source projects means that community interaction is also open, so 
whoever wanted to improve your code could have discussed issues openly - on the 
mailing list/JIRA

3) Then, if another person made changes to code, you legally *cannot* attach 
such code as "yours" as it is seen in the above JIRA today. This is why the ASF 
requires each contributor to specifically grant the ASF the authority to use 
the code when you upload a patch to a JIRA - so now it seems like the ASF has 
been entangled into a legal issue as well by your hurried act - and I suggest 
you remove this attachment.

More seriously, I do not think you met the objective of the GSoc project [my 
earlier link], when you clearly stopped participation in the ODE project soon 
after the GSoc stuff was in a state of submission for you after just a couple 
of months. I also see that your completion status was not included into the ASF 
board report [1] after reminders - though its not your fault

Leaving all these aside, you were always free to contribute to Synapse anytime. 
And I believe GSoc as per its objective "inspired" you to "begin" participating 
in open source projects. After completing one round with GSoc, showing 
spontaneous enthusiasm in this Synapse JIRA just approximately 7 hrs after 
being published, but forgetting the ODE project where your involvement was 
funded by GSoc earlier seems to indicate possibly something else.. I personally 
believed the GSoc program was to just "bring in" students into open source, and 
that doing it once is enough. I do not have any questions on the technical 
aspects of what you had done, or plan to do now, but about what really 
motivates you.. 

asankha

[1] http://markmail.org/message/ipc7dzjm532nw3ia


> [GSoC] Implement a Dead Letter Channel for Synapse
> --------------------------------------------------
>
>                 Key: SYNAPSE-618
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-618
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Core, Endpoints
>            Reporter: Hiranya Jayathilaka
>             Fix For: FUTURE
>
>
> Currently when Synapse attempts to send a message and if it fails, following 
> actions can be configured to deal with the error:
> * Execute a fault sequence and handle the failed request gracefully
> * Fail-over to a different endpoint
> In addition to these, Synapse ESB should support the "dead letter channel" 
> enterprise integration pattern to deal with various errors that might occur 
> during mediation or while sending. With the dead letter channel, the failed 
> message will be put into a message store in the ESB. Later the ESB can retry 
> to send the messages in the message store. 
> We should be able to have multiple implementations of the actual message 
> store and should be able to configure which store to use for a particular 
> scenario. Users should be able to implement their own message stores and plug 
> into the ESB easily. To start with we can have a simple in-memory message 
> store and a persisting store based on JDBC or JMS. 
> References:
> http://www.eaipatterns.com/DeadLetterChannel.html
> https://issues.apache.org/jira/browse/SYNAPSE-263
> Possible Mentors:
> Hiranya Jayathilaka

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to