Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[udig-devel] [jira] Created: (UDIG-1107) Local Catalog find( url, monitor ) assumes IGeoResource identifier subset of IService identifier

Local Catalog find( url, monitor ) assumes IGeoResource identifier subset of IService identifier
------------------------------------------------------------------------------------------------

                 Key: UDIG-1107
                 URL: http://jira.codehaus.org/browse/UDIG-1107
             Project: uDIG
          Issue Type: Bug
          Components: API catalog, catalog
    Affects Versions: UDIG 1.1.RC5
            Reporter: Jody Garnett
             Fix For: UDIG 1.1.RC6


We have proceeded with the following assumption:
- http://localhost/geoserver/wms
- http://localhost/geoserver/wms#layer

We need to break this assumption as a georesource may have a valid identifier based on contents rather then the server access point...

Proposed Fix:
1. search through services using urlEquals( service_id, query ) for each service
- this will 
2. seach through service, and check connected services for a matching identifier
3. seach through service, and check not connected services for a matching identifier

Proposed Optimization:

We can also optimize the initial search by breaking it into two passes - one for connected services and a second for notconnected services.

What about your Friends?

The friends function also needs to walk through available services and georesources; since this is delegated off to an extension point we will be at the mercy of each implementation to respect connected / non connected status.

The best solution woudl be to create a catalog visitor that "walks" the data structure in order of CONNECTED, NOTCONNECTED; and to modify the Friends contract to return non BROKEN friends.  Think there is an Eric Clapton song about that ....

-- 
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

        


Back to the top