[
https://issues.apache.org/jira/browse/JAMES-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649782#comment-16649782
]
Tellier Benoit commented on JAMES-2155:
---------------------------------------
https://github.com/linagora/james-project/pull/1719 solved the issue.
Many thanks to Sebast26 and all other people having worked on this issue.
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
