james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pramod dilshan rathnyake (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
Date Sun, 12 Feb 2017 14:35:41 GMT

    [ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862804#comment-15862804

pramod dilshan rathnyake commented on JAMES-1932:


I am Pramod Dilshan Rathnayake a Computer Engineering Undergraduate from the faculty of Engineering,
University of Ruhuna, Srilanka.
I really like to contribute to this project for GSOC 2017 and I believe I have knowledge for
do this well. (I have very good experience and knowledge in Java EE, Spring/Spring boot/Spring
Cloud/Spring Security, Spring Data JPA , AngularJS2, HTML, JavaScript, CSS, Maven).
First of all, I went through the documentation of Apache_James_Server (https://james.apache.org/server/quick-start.html).
As mentioned there  I downloaded the project source code and configured it on my local machine.
Also, I downloaded Binary files of  Apache_James_Server and tried to setup it on my local
machine. But Unfortunately when I try to create domains and users, that give an error. So
I need some help to configure it and get some knowledge about this.
So if someone gives an idea what I have to do first and How I start this, I will be really
really grateful.
Pramod Dilshan Rathnayake, 
University of Ruhuna,

> Mailet pipeline ui edition tool
> -------------------------------
>                 Key: JAMES-1932
>                 URL: https://issues.apache.org/jira/browse/JAMES-1932
>             Project: James Server
>          Issue Type: Task
>            Reporter: Matthieu Baechler
>              Labels: backend, frontend, gsoc2017, java, js, json, rest, sse
> James has to concept of mailet pipeline : for any incoming email, the email is passing
through the pipeline the is made of matchers and mailets. These components allow to implement
business rules based on some xml configuration and some java component.
> That's a great strength of James and a lot of people use it for this capability.
> Nevertheless, editing the pipeline and making tests is painful right now, you are left
finding solutions like "edit xml, launch server, send an email, read logs".
> To ease adoption, we would like to make that process easy and fun by :
> * providing a web ui frontend to design the pipeline
> * given a set of emails, make it possible to visualise each email flow into the mailet
pipeline to test it
> * define a way to express the expected results to make sure people can save their work
into automated tests
> To implement that, the student must know enough about web frontend dev to implement a
pipeline designer and debugger.
> She or he will need to know some java to implement server side logic for :
> * make james accept to reconfigure its pipeline at runtime to take modifications into
> * design a protocol to stream debug data from a pipeline to the web ui and implement
it server-side in java
> * implement a junit runner to be able to run some special mailet tests based on the work
done in the web designer.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message