[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369019#comment-16369019 ] Raphaël Ouazana commented on JAMES-1932: Hi, Yes, this project is free, so you can work on it! Regards, Raphaël. > 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 >Priority: Major > 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 (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360769#comment-16360769 ] Irindu Nugawela commented on JAMES-1932: Hi I am a Computer Engineering Undergraduate from University of Peradeniya Sri Lanka, I am intrested in this project, can I work on this project for GSOC 2018 > 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 >Priority: Major > 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 (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360755#comment-16360755 ] Irindu Nugawela commented on JAMES-1932: Is this project completed ? can I still work on it ? > 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 >Priority: Major > 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 (v7.6.3#76005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956678#comment-15956678 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~e...@apache.org] , I'd definitely use a frontend framework such as reactjs or angular for the production UI. The above UI is just a sample. I haven't included a frontend framework in the sample. I'd surely use one for gsoc > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956669#comment-15956669 ] Eric Charles commented on JAMES-1932: - [~shravan97] I'd love to see react.js as javascript framework for you gsoc. Is this something possible to consider? (https://cdn.rawgit.com/shravan97/web_game/c90b1d74/mailet.html does not seem to have this) > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951376#comment-15951376 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~BTellier] , [~matthieu-at-arkoon] I've now edit my proposal with some of your suggested changes and uploaded it to Google's portal. If you could let me know at the earliest about the selection, I can start working soon. Thank you ! > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948005#comment-15948005 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~matthieu-at-arkoon] , [~BTellier] I've now made changes to the UI as suggested. I haven't implemented the drag and drop of mailets alone. Here is the link to the UI : https://cdn.rawgit.com/shravan97/web_game/c90b1d74/mailet.html Apart from this, I've created my proposal as well. Here is the link to my proposal : https://gist.github.com/shravan97/2c99dbb6d033b174b24acba1206b9a45 I'd certainly like to hear suggestions from both of you. And I'd also like to let you know that I've subscribed to the server-dev mailing list > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944961#comment-15944961 ] Tellier Benoit commented on JAMES-1932: --- http://james.apache.org/mail.html might help you > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944899#comment-15944899 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~BTellier], [~matthieu-at-arkoon] Thanks for giving me suggestions. I'll finish them up as soon as possible. How do I join the mailing list though ? Do I just need to send a mail to server-dev@James.apache.org regarding what I'm working on ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944813#comment-15944813 ] Matthieu Baechler commented on JAMES-1932: -- Please, if you are interested in a Google SoC application, join server-dev@james.apache.org mailing list to discuss it. > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944463#comment-15944463 ] Tellier Benoit commented on JAMES-1932: --- Hi, I like your UI proposal. It's simple, efficient and intuitive. >From a pure UX point of view : - Open all the mailets by default, we need to have at least mailet name at first glance - Mailets can have additionnal parameters - We need to be able to add mailets / processors - It can be cool to drag and drop mailets > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943973#comment-15943973 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~matthieu-at-arkoon], [~BTellier], Here's a link to the sample UI, I made for mailet edition. https://cdn.rawgit.com/shravan97/web_game/5572b0df/mailet.html Each of the elements with text in grey color are all editable. You'll just have to click on them to edit them. For now, I've just hardcoded the first few mailets from mailetcontainer.xml . Later, I'll be getting mailet info from server side. This is just a minute sample of what I'll be making. I'll be customizing it along the way. Please do suggest edits so I can improve it further. And also, I'll upload my proposal to this project very soon > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939151#comment-15939151 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi Matthieu, I'll do exactly as you'd suggested. I'll soon give you a link to a sample ui that I make for this. One of my question is, can I use of some amount of external CSS/Javascript libraries for specific components on the page ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932249#comment-15932249 ] Tellier Benoit commented on JAMES-1932: --- Hi Shravan, I believe the first step might be to have a front-end for editing configuration for the mailet container. You can see this configuration serialised as XML in mailetcontainer.xml. You can have a look at the CamelCompositeProcessor to see how this documentation is read. Step number 2 is to allow to save this configuration and overwrite mailetcontainer.xml (maybe with renaming old configuration first). Step number 3 might be to launch a CamelCompositeProcessor (a new one) from the web-based editor. We can imagine having some kind of Listener in it to keep track of the execution results (With registering special listeners ?). We can imagine feed it with "user uploaded emails". This would allow debugging. Step number 4 might be to allow replacing the current CamelCompositeProcessor with the one from the editor, allowing live changes to the mailet pipeline, without restarting the server. I believe the web-admin code should get control on this (the user edit/saves/replaces code). We might however need to be able to load current configuration in the web-editor. I would also value a clear separation of code with /server/mailet/mailetcontainer-camel , and to try to add these cool new features using composition. I also believe we need to track e-mail path for "under edition/debugging" mail pipeline, not the production one. I think this feature should not be "invasive" for production code. Cheers, Benoit > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931391#comment-15931391 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~BTellier] I'm quite new to the codebase and I'm still going through it and figuring out how everything is being arranged. As for this project, can I edit the already existing code for mailet api to call the web-admin server when mail processing is happening and then serve the frontend code accordingly ? I'd love to hear your suggestions and please do correct me if I'm wrong :) > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931173#comment-15931173 ] Tellier Benoit commented on JAMES-1932: --- Hi, After thinking a bit to it, yes I believe you can create a separate mvn project for it. You would need to create a project in server/protocols (the name you suggested seems fine to me). server/guice/protocols is for defining guice bindings for protocols. I would suggest you to reuse already existing code. You can define a Routes for mailet-edition that you can then load in web-admin. Note that using web-admin implies to use java-8 and guice. May I ask you the implementation steps that you plan to follow? Wich architecture would you propose for solving the problem stated above? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930415#comment-15930415 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi [~BTellier] , Did you mean that I'll have to create a new maven project named mailet-edition ? It's because 'server/protocols/mailet-edition' and 'server/guice/protocols' don't exist in the james-project repository > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926893#comment-15926893 ] Pramod Dilshan commented on JAMES-1932: --- [~shravan97], I sent mail from dils...@dilsoft.net to dils...@dilsoft.net. both user 'dilshan' and domain 'dilsoft.net' is in the James server. please see this link. http://stackoverflow.com/questions/42769810/how-to-configure-thunderbird-for-james-mail-server-in-ubuntu Thanks > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926384#comment-15926384 ] SHRAVAN MURALI commented on JAMES-1932: --- [~BTellier], my frontend code is supposed to go inside server/site right ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926356#comment-15926356 ] SHRAVAN MURALI commented on JAMES-1932: --- [~pramod94], are you sure that the outgoing email address is not from an external mail server ? If you've setup James in your local, then both the email addresses should belong to a mail server from the same network > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15919565#comment-15919565 ] Pramod Dilshan commented on JAMES-1932: --- Hi [~BTellier], [~shravan97] I am Pramod Dilshan Rathnayake and I am working on issue (https://issues.apache.org/jira/browse/JAMES-1931. I try to configure James Server in Thunderbird But I faced some problems. Here is StackOverflow Question.(http://stackoverflow.com/questions/42769810/how-to-configure-thunderbird-for-james-mail-server-in-ubuntu). Please help to find what went wrong. Thanks. > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907125#comment-15907125 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi Benoit, Thanks a lot ! I was perfectly able to integrate it with ThunderBird. Both IMAP and SMTP work perfectly now ! And as for this task, I'm supposed to make a UI for the flow of the mail right ? I'm well versed with making web UIs. So, I'll able to start it right away Cheers, Shravan > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906793#comment-15906793 ] Tellier Benoit commented on JAMES-1932: --- Hi. You can for instance set-up thunderbird and connect it to the James server. Cheers, Benoit > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906564#comment-15906564 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi Matthieu, I cloned the repository and then ran the docker-compose file. It works perfectly fine and all the services started. What do I do after that ? How do I test the mail server after creating users ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902612#comment-15902612 ] Matthieu Baechler commented on JAMES-1932: -- You can follow the links raphael gave you : download from github, you'll get the latest source code to start to work with. > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901738#comment-15901738 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi Matthieu, I tried to download it from https://james.apache.org/download.cgi . But this gave me 404 when clicked on the tar link. Where else do I download it from ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897242#comment-15897242 ] Matthieu Baechler commented on JAMES-1932: -- Hi, Did you managed to make it run ? Do you need some more help ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890294#comment-15890294 ] Raphaël Ouazana commented on JAMES-1932: Hi, I think you can start with the GitHub repository: https://github.com/apache/james-project/ There is a fine readme you can follow. Then you can find more specific mailets information there: http://james.apache.org/mailet/index.html Regards, Raphaël Ouazana. > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888740#comment-15888740 ] SHRAVAN MURALI commented on JAMES-1932: --- Hi Matthieu, I'm Shravan. Here's my github profile : github.com/shravan97 This seems to be a very interesting idea for me. I would like to take this issue up. How do I get started ? Where do I access the codebase ? > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1932) Mailet pipeline ui edition tool
[ https://issues.apache.org/jira/browse/JAMES-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862804#comment-15862804 ] pramod dilshan rathnyake commented on JAMES-1932: - Hi, 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. Thanks. Pramod Dilshan Rathnayake, University of Ruhuna, Srilanka. > 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
