[
http://jira.codehaus.org/browse/MRM-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145620#action_145620
]
James William Dumay commented on MRM-124:
-----------------------------------------
Committed r687522 on branch
https://svn.apache.org/repos/asf/archiva/branches/MRM-124
* Using Atlassian XML-RPC API (Source and binaries available under the Apache 2
license at https://maven.atlassian.com/public/)
* Modules for API and Server
Clients can simply depend on the archiva-xmlrpc-api module and use its
interfaces to bind to remote services.
Here is an example:
Client interface:
{code}
@ServiceObject("Test")
interface TestService
{
String ping();
}
{code}
Server implementation
{code}
class TestServiceImpl implements TestService
{
String ping() {
return "pong";
}
}
{code}
Clients would then connect like so:
{code}
Binder binder = new DefaultBinder()
TestService testService = binder.bind(TestService.class,
"http://path/to/archiva/xmlrpcservlet";);
String result = testService.ping(); //result should equal "pong"
{code}
> web service interface
> ---------------------
>
> Key: MRM-124
> URL: http://jira.codehaus.org/browse/MRM-124
> Project: Archiva
> Issue Type: New Feature
> Components: web application
> Reporter: Brett Porter
> Assignee: James William Dumay
> Fix For: 1.2
>
>
> this needs a new jira component.
> We need a comprehensive web services interface to the application. Like RSS,
> it should be a new view on the same actions. The more we can derive that from
> the repository-core interfaces, the better.
> This should include administration and security.
--
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
