History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-460
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Arjohn Kampman
Reporter: Jan Stette
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sesame

Make it possible to use custom RepositoryManagers by accessing RepositoryManager instances through an interface

Created: 22/Oct/07 07:13 PM   Updated: 26/Sep/08 11:31 AM
Component/s: HTTP Server
Affects Version/s: 2.0-beta6, 2.0-beta5
Fix Version/s: 2.1.3


 Description   
In current versions of Sesame, it's not possible to use alternative implementations of RepositoryManager classes, as these are accessed directly by other objects, instead of through an interface. The default behaviour, i.e. serving up RDF from repositories from files and databases, covers many use cases, but I also need to serve up already existing repositories embedded in my application.

It's very easy to change this, simply by creating an interface that RepositoryManagers implement, and having other classes use this. This allows full pluggability of alternative implementations.



 All   Comments   Change History      Sort Order:
Comment by Jan Stette [22/Oct/07 07:16 PM]
I have patches for this issue, for beta5 and beta6. Let me know if you'd like me to submit these.

Comment by Jan Stette [13/Dec/07 03:44 PM]
With the latest version of Sesame (I'm looking at 2.0 RC2 at the moment) this has almost already been done. All that's needed to change is to make the RepositoryInterceptor and RepositoryListController use the RepositoryManager abstract base class instead of the concrete LocalRepositoryManager class.