[jira] [Resolved] (MARMOTTA-85) Allow modular triple store backend packaging

["Sebastian Schaffert (JIRA)" <ji...@apache.org>]

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

Sebastian Schaffert resolved MARMOTTA-85.
-----------------------------------------

    Resolution: Fixed

> Allow modular triple store backend packaging
> --------------------------------------------
>
>                 Key: MARMOTTA-85
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-85
>             Project: Marmotta
>          Issue Type: Task
>          Components: Platform, Triple Store
>            Reporter: Sebastian Schaffert
>            Assignee: Sebastian Schaffert
>             Fix For: 3.2
>
>
> With the changes to the architecture in 2.6, it is now easy to configure different backends for Marmotta. During the code importation, we should foresee this by creating an appropriate module and package structure that separates the actual backend implementation (currently SesameServiceImpl) from the core so that different backends can be provided more easily. I suggest:
> - we create a directory "backends" to group the different backend implementations
> - we have then different backend implementations (marmotta-backend-kiwi and marmotta-backend-memory for 3.0, marmotta-backend-native, marmotta-backend-tdb, marmotta-backend-sdb for later)
> - we let the backend-specific modules depend on the respective backend instead of the marmotta-core



--
This message was sent by Atlassian JIRA
(v6.1#6144)