james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Tellier (Jira)" <server-...@james.apache.org>
Subject [jira] [Closed] (JAMES-3515) Expose JAMES functionalities via REST APIs
Date Sat, 01 May 2021 16:32:00 GMT

     [ https://issues.apache.org/jira/browse/JAMES-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Benoit Tellier closed JAMES-3515.
    Resolution: Not A Problem

I am closing this ticket.

Feel free to open a new one if you plan to add WebAdmin support for the Spring package.


> Expose JAMES functionalities via REST APIs
> ------------------------------------------
>                 Key: JAMES-3515
>                 URL: https://issues.apache.org/jira/browse/JAMES-3515
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Omid Pourhadi
>            Priority: Minor
> Integrating JAMES into your external project requires many configuration and is not as
easy as it should be, the proposal here is to expose JAMES functionalities including add domain,
user, mailbox via REST APIs since JMX being hard to secure and its use is considered legacy. 
> [Here|[https://github.com/omidp/james-spring-boot-jpa-webclient-api]] I created a [james-spring-boot-jpa-webclient-api|https://github.com/omidp/james-spring-boot-jpa-webclient-api] to
do a POC if this is possible . 

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