Opened 17 years ago
Closed 15 years ago
#74 closed defect (fixed)
repositories.xml should not be created during Z39.50 Server initialization
Reported by: | rjwalker | Owned by: | simon |
---|---|---|---|
Priority: | minor | Milestone: | v2.5.1 |
Component: | General | Version: | v2.2.0 Final |
Keywords: | Cc: |
Description ¶
The repositories.xml file that is used to specify remote Z39.50 servers is created at startup from repositories.xml.tem by the fixRepositoriesFile() method of src/org/fao/geonet/services/util/z3950/Server.java. That method is called by the init() method of the same Server class.
But what if you want to do remote searching, but don't want to start up GN's own Z39.50 server?
The repositories.xml file should be created whether or not the Z39.50 server will be running. The code to create it should be moved out of Server.java to somewhere where it will be executed on every startup.
Change History (5)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
Milestone: | → v2.5.0 |
---|
comment:3 by , 15 years ago
Creation of JZKitConfig.xml from JZKitConfig.xml.tem is independed of whether the server is enabled or not so the basic bug is fixed. However, I think the getRepositories service that reads the list of respositories from this config should not offer any collections from the local GeoNetwork server if the server is not enabled - so one more small fix is still required before this can be closed.
comment:4 by , 15 years ago
Milestone: | v2.5.0 → v2.5.1 |
---|
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
'One more small fix' referred to above has been committed for 2.5.1
Currently no GUI for Z39.50, so postponed until later release. Fix is ready in BluenetMEST