james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
Date Thu, 16 Mar 2017 02:06:41 GMT

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

Tellier Benoit commented on JAMES-1932:
---------------------------------------

Hi Shravan,

site/* folders are for the Apache website code.

Let's not mix that... Please introduce a new mvn project in server/protocols/mailet-edition
. Serve your code with an embedded server. Jetty (like JMAP) or Spark-java (like WebAdmin).
Then you will need to wire it in the server/guice/protocols project in order to start it and
start playing.

Let's wait other people answer about this. I believe that this pannel can also belong in WebAdmin...
(Maybe on an other path than the Shravan code, to avoid much conflict).

> 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
account
> * 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
(v6.3.15#6346)

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


Mime
View raw message