Hi,

I introduced three experimental API calls:
- api.getApiNamespaces - Lists available API namespaces
- api.getApiNamespaceCallList - Lists all available api calls for the specified 
namespace
- api.getApiCallList - Lists all available api calls grouped by namespace 
(combination of previous two)

Example for api.getApiNamespaceCallList(key,'channel.org'):

{'channel.org.enableAccess_string_string_int': {'exceptions': 
['FaultException'], 'return': 'int', 'name': 'enableAccess', 'parameters': 
['string', 'string', 'int']}, 'channel.org.disableAccess_string_string_int': 
{'exceptions': ['FaultException'], 'return': 'int', 'name': 'disableAccess', 
'parameters': ['string', 'string', 'int']}, 'channel.org.list_string_string': 
{'exceptions': ['FaultException'], 'return': 'array', 'name': 'list', 
'parameters': ['string', 'string']}}

For each call identifier, there's:
- a list of exception, that the call can throw
- a return type
- name of the call
- parameter types (ordered list)

The biggest minus are top level types. It means, if channel.org.list returns an 
array, we do not find out, array of what type it is. If there's a struct 
returned, we do not know, how the struct look like. Anyway, the calls are 
intended to be used mainly to list available calls with required parameters and 
that is what these calls provide.

Any comments and patches are welcome!


Regards,
Tomas

These API call will be available in spacewalk-nightly repo since spacewalk-java 
version 0.9.12-1 soon. :-)

--
Tomas Lestach
RHN Satellite Engineering, Red Hat

_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to