[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[udig-devel] [jira] Created: (UDIG-1103) Confirm IService handles CONNECTED / NOTCONNECTED status
|
Confirm IService handles CONNECTED / NOTCONNECTED status
--------------------------------------------------------
Key: UDIG-1103
URL: http://jira.codehaus.org/browse/UDIG-1103
Project: uDIG
Issue Type: Task
Components: arcgrid, arcsde, catalog, oracle, postgis, shapefile, wfs, wms, world image
Affects Versions: UDIG 1.1.RC6
Reporter: Jody Garnett
Assigned To: Richard Gould
Fix For: UDIG 1.1.RC6
The CatalogImpl.find( query, monitor ) method pays attention to the server.getStatus() state when searching for layer resources....
for( IService service : services ) {
if( service.getStatus() == CONNECTED ){
IResolve res = getChildById(service, query, monitor);
if( res!=null ){
found.add(res);
found.addAll( friends( res));
break;
}
}
}
For this to be effective services *really* need to be honest about their CONNECTED status; there is a speed advantage during initial load if all implementations get this correct (but the first implementation to get it wrong will slow everybody down - once).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira