1
|
// $Id$
|
2
|
/**
|
3
|
* Copyright (C) 2009 EDIT
|
4
|
* European Distributed Institute of Taxonomy
|
5
|
* http://www.e-taxonomy.eu
|
6
|
*
|
7
|
* The contents of this file are subject to the Mozilla Public License Version 1.1
|
8
|
* See LICENSE.TXT at the top of this package for the full license terms.
|
9
|
*/
|
10
|
|
11
|
package eu.etaxonomy.cdm.api.service.lsid;
|
12
|
|
13
|
import com.ibm.lsid.server.LSIDServerException;
|
14
|
import com.ibm.lsid.server.LSIDService;
|
15
|
|
16
|
import eu.etaxonomy.cdm.model.common.IIdentifiableEntity;
|
17
|
import eu.etaxonomy.cdm.model.common.LSID;
|
18
|
/**
|
19
|
* LSIDMetadataService interface which was altered from com.ibm.lsid.server.LSIDMetadataService,
|
20
|
* replacing the LSIDRequestContext with a simple LSID. My thinking behind this is that provided the
|
21
|
* LSIDMetadataService has no responsibility for security, then there is no need to pass that
|
22
|
* information to it (in an LSIDRequestContext). This allows better separation of concerns in that methods
|
23
|
* requiring authentication and authorization can be secured transparently within CATE without the need for
|
24
|
* the LSIDMetadataService to know anything about it. I could be wrong, of course.
|
25
|
*
|
26
|
* @author Ben Szekely (<a href="mailto:bhszekel@us.ibm.com">bhszekel@us.ibm.com</a>)
|
27
|
* @author ben
|
28
|
*
|
29
|
* @see com.ibm.lsid.server.LSIDMetadataService
|
30
|
* @see com.ibm.lsid.server.LSIDRequestContext
|
31
|
*/
|
32
|
public interface LSIDMetadataService extends LSIDService {
|
33
|
|
34
|
/**
|
35
|
* Get the meta data associated with the LSID
|
36
|
* @param LSIDContext lsid
|
37
|
* @return an IdentifiableEntity, null if there is no metadata
|
38
|
*/
|
39
|
public IIdentifiableEntity getMetadata(LSID lsid) throws LSIDServerException;
|
40
|
}
|