Bug #1898
closedRedesign the web service harvester and create design documentation
0%
Description
A document on how to do the harvesting to fit inn with the new dynamic actor
loading, annotation, etc. The harvested services should not be kept in the
repository, and they should be updated everytime the Kepler client is loaded. We
probably need to have a metarepository in the end to keep track of the
repositories and keywords that were searched and also collect some information
on the user's interest.
Updated by Ilkay Altintas about 19 years ago
We need to discuss next week what harvesting web services mean for Kepler in the
new kar-based architecture. Then this can be implemented in 1-2 months.
Updated by Matt Jones about 19 years ago
The web service harvester should probably become part of the left hand pane to
allow for a user to choose a UDDI (etc) repository and harvest the services into
actors. This might wait until after the 1.0.0 release if its not obvious how to
do it.