On 31 August 2016 at 16:23, Paul Brack <[email protected]> wrote:
> We'd like to set up our own remote Taverna component registry - I've tried to > simply expose my local one via HTTP but Taverna Workbench isn't recognising > it. Is this something we're able to do? Hi, what did you set up, your own myExperiment install or some other HTTP service? I think the API used by the remote component registry does not directly map to the files stored by the local repository - but rather maps to certain methods in the myExperiment API http://wiki.myexperiment.org/index.php/Developer:API If it's public, do you have a URL to share? Here's the code that does the remote calls: https://github.com/apache/incubator-taverna-plugin-component/blob/master/taverna-component-activity/src/main/java/org/apache/taverna/component/registry/standard/NewComponentRegistry.java (and neighbouring classes. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718
