mirror of
https://github.com/apache/archiva.git
synced 2025-02-22 18:31:43 +00:00
some more information
git-svn-id: https://svn.apache.org/repos/asf/archiva/branches/MRM-1025@909067 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
0709ac5238
commit
333764a1da
@ -4,3 +4,30 @@
|
||||
|
||||
Repository APIs
|
||||
|
||||
The repository APIs are the means for accessing metadata from any type of repository.
|
||||
|
||||
<Note:> currently, only metadata retrieval is available. As more of the application moves to this base, artifact
|
||||
content may be read using a stream, for example.
|
||||
|
||||
* Metadata Resolver
|
||||
|
||||
A repository request works in the following sequence:
|
||||
|
||||
[[1]] the user requests a project's metadata using a
|
||||
{{{./apidocs/org/apache/archiva/metadata/repository/MetadataResolver.html} MetadataResolver}}
|
||||
|
||||
[[2]] the resolvers are chained together to locate the source of the metadata, and to determine where the most
|
||||
up to date copy is. Included by default are the metadata repository and repository storage
|
||||
|
||||
[[3]] the metadata is retrieved, and if not up to date in the metadata repository it is stored there
|
||||
|
||||
[[4]] the metadata is returned to the requester
|
||||
|
||||
* Storage Resolver
|
||||
|
||||
Currently storage only supports obtaining information as well. In the future, the ability to modify the storage
|
||||
will be made available for plugins such as purging, etc.
|
||||
|
||||
More information can be found in the
|
||||
{{{./apidocs/org/apache/archiva/metadata/repository/storage/StorageMetadataResolver.html} storage metadata resolver}}
|
||||
class.
|
||||
|
Loading…
x
Reference in New Issue
Block a user