[
http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131880#action_131880
]
nramirez edited comment on MRM-694 at 4/23/08 8:35 AM:
--------------------------------------------------------------------------
The following test cases are handled:
1. Accessing a valid repository group root url (e.g.
http://machine.com/repository/repository-group/) returns a Bad Request (HTTP
400)
2. Accessing an invalid repository group root url is forwarded to managed
repository checking
3. Accessing an artifact in a valid repository group will iterate over the
managed repositories in the repository group
3.a. If an invalid managed repository is encountered (managed repository
doesn't exist), a Not Found (HTTP 404) is returned and the iteration is broken
3.b. If an artifact is not found in a valid managed repository (after
proxying, etc.), a Not Found (HTTP 404) is set but not returned yet, the
iteration continues to the next managed repository. The Not Found (HTTP 404)
is returned after exhausting all valid managed repositories
3.c. If an artifact is found in a valid managed repository, the artifact
is returned, the iteration is broken and any Not Found (HTTP 404) is disregarded
4. Accessing a valid repository group with any http write method returns a Bad
Request (HTTP 400)
was (Author: nramirez):
The following test cases are handled:
1. Accessing a valid repository group root url (e.g.
http://machine.com/repository/repository-group/) returns a Bad Request (HTTP
400)
2. Accessing an invalid repository group root url is forwarded to managed
repository checking
3. Accessing an artifact in a valid repository group will iterate over the
managed repositories in the repository group
3.a. If an invalid managed repository is encountered (managed repository
doesn't exist),
a Not Found (HTTP 404) is returned and the iteration is broken
3.b. If an artifact is not found in a valid managed repository (after
proxying, etc.),
a Not Found (HTTP 404) is set but not returned yet, the iteration
continues to the next managed repository.
The Not Found (HTTP 404) is returned after exhausting all valid
managed repositories
3.c. If an artifact is found in a valid managed repository,
the artifact is returned, the iteration is broken and any Not
Found (HTTP 404) is disregarded
4. Accessing a valid repository group with any http write method returns a Bad
Request (HTTP 400)
> Virtual repositories or repository grouping
> -------------------------------------------
>
> Key: MRM-694
> URL: http://jira.codehaus.org/browse/MRM-694
> Project: Archiva
> Issue Type: New Feature
> Components: repository interface
> Reporter: Maria Odea Ching
> Fix For: 1.1
>
> Attachments: MRM-694-archiva-configuration.patch,
> MRM-694-archiva-webapp.patch, MRM-694-archiva-webdav.patch,
> MRM-694-web-interface.patch
>
>
> A number of managed repositories can be grouped together with that group
> having only one url. So you only need to specify that url in the settings.xml
> file and when Archiva receives a request via that url, it would look for that
> artifact from the repositories belonging to that group.
> More details are dicussed here:
> http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
