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] [Resolved] (JAMES-2155) Implement a JPA Sieve Repository
Date Mon, 15 Oct 2018 06:33:00 GMT

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

Tellier Benoit resolved JAMES-2155.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.0

> Implement a JPA Sieve Repository
> --------------------------------
>
>                 Key: JAMES-2155
>                 URL: https://issues.apache.org/jira/browse/JAMES-2155
>             Project: James Server
>          Issue Type: New Feature
>          Components: data, jpa
>    Affects Versions: master
>            Reporter: Tellier Benoit
>            Priority: Major
>              Labels: newbie
>             Fix For: 3.2.0
>
>
> James exposes the *SieveRepository* interface for storing Sieve scripts. 
> Nowadays, Sieve scripts can only be stored on top of Files and Cassandra. Storing Sieve
scripts on top of *JPA* would unlock this feature above a database.
> I order to do so:
>  - Write a *JPASieveRepository* in *data-jpa* project. (in the sieve package.) You can
look at other classes to get hints. Like JPAUsersRepository or JPADomainList.
>  - To write a *JPASieveRepositoryTest* class and check your work simply extend the *AbstractSieveRepositoryTest*
class. 
> Don't hesitate to ask for help on the *Gitter* chat.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
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