[kepler-dev] [Bug 2490] - Get ecogrid endpoints from Ecogrid registry

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue Feb 5 14:44:51 PST 2008


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2490


leinfelder at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #7 from leinfelder at nceas.ucsb.edu  2008-02-05 14:44 -------
Endpoints are now automatically refreshing from the registry when a user first
goes to the Data search tab.  This still happens once per kepler window (there
is a new bug that deals with reducing this to once per Kepler launch).
Additionally, there is a "Refresh" button on the Sources dialog.  This can be
used to force a refresh when desired.
Registry entries are then serialized to the config file and persist there.
Note that the scope of the EcoGridServicesController has been expanded to
include more service types than just the QueryService (authentication,
identification, put, and authenticated query).  This class should be used as
the main interaction point between Kepler, the registry, and the various
services.


More information about the Kepler-dev mailing list