Kepler

sounds like some error catching is in order. should there be an alert using MessageHandler (attack of the pop up window!) or should it just log the error and move on with life?

I'd say show an alert when something is trying to use a data source, e.g. the ecogrid actor. Otherwise, ignore it.

added messagehandler error reporting when the services registry is not available.
if, on start up, there is an error accessing the registry, an alert is shown (in kepler gui mode, at least).

I'm reopening this since the error window now occurs regardless of any data sources actually being used (either the Data tab or ecogrid actors).

This seems low priority so could be re-targeted to 1.1.

retarget to 1.1

The short term solution is just removing the error message. Kepler will keep silent if it couldn't connect to the registry.

The long term solution is assigned to bug 3228.

Remove the error message panel and decrease debug level from error to warn in src/org/ecoinformatics/seek/ecogrid/SearchRegistryAction.java class. Now if kepler couldn't contact registry because of network disconnection and it will keep silence.

Original Bugzilla ID was 3209