Hi Oliver,
I wanted to install latest stable version of Archiva which is currently
1.3.5
and I wanted the user management xmlrpc services to be included as well.
Anyway, I also tried to install 1.4-M1 where the patch is already applied.
So in case the patch cannot be applied to lower version I would use this
one.

But now, my main problem is how to actually use the added capability of
user management thru xmlrpc.
Can you please provide some examples how to use/call the services having
installed
1.4-M1 or any usefull guide link?
I wasn't able to find any

Thank you

Lukas


2012/1/20 Olivier Lamy <[email protected]>

> 2012/1/20 Gmail <[email protected]>:
> > Hello,
> > I have applied the patch: http://jira.codehaus.org/browse/MRM-1481
> > on the archiva version 1.3.5.
> > Now I would like to know actually how I can use the xmlrpc services in
> > archiva.
> >
> > As I use python to call the services, so for example the xmlrpc services
> > which were already part of the archiva 1.3.5 I call this way:
> > import xmlrpclib
> > proxy =  xmlrpclib.ServerProxy("http://admin:password@localhost
> > :8080/archiva/xmlrpc")
> > proxy.AdministrationService.getAllManagedRepositories()
> > So far everything works ok.
> >
> > And now,  I supposed that usage of those new exposed services by the
> patch
> > should be called in some similar way, e.g.
> > proxy.RoleService.getRoles()
> >
> > So what would be the correct usage/call of those new xmlrpc services
> neded
> > from following redback api:
> > I need to call methods from exactly this implementation class:
> >
> http://redback.codehaus.org/redback-core/apidocs/reference/org/codehaus/redback/xmlrpc/service/RoleServiceImpl.html
> >
> >
> > For me It seems that the ServiceObjects are not accessible or exposed yet
> > after even though the patch was applied
> >
> > As last comment, I don't like to use rest api in this moment
>
> Why ?
> BTW it's only available in 1.4-Mx
>
>
> >
> > Thanks for any advise folks
> >
> > BR.Lukas
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Reply via email to