Task #1390
Story #1275: Fix metacat bugs
baseurl in metcat /nodes response incorrect
Status:
Closed
Priority:
Normal
Assignee:
Category:
Metacat
Target version:
Start date:
2011-03-01
Due date:
% Done:
100%
Milestone:
Product Version:
*
Story Points:
Sprint:
Description
Related issues
History
#1 Updated by Dave Vieglais about 13 years ago
- Position set to 2
- Target version set to Sprint-2011.09-Block.2
#2 Updated by Dave Vieglais about 13 years ago
- Target version changed from Sprint-2011.09-Block.2 to Sprint-2011.10-Block.2
- Position set to 2
- Position deleted (
6)
#3 Updated by Dave Vieglais about 13 years ago
- Target version changed from Sprint-2011.10-Block.2 to Sprint-2011.11-Block.2
- Position deleted (
30) - Position set to 4
#4 Updated by Dave Vieglais about 13 years ago
- Assignee set to Chris Jones
#5 Updated by Dave Vieglais about 13 years ago
- Target version changed from Sprint-2011.11-Block.2 to Sprint-2011.12-Block.2
- Position deleted (
10) - Position set to 2
#6 Updated by Dave Vieglais about 13 years ago
- Parent task set to #1275
#7 Updated by Chris Jones about 13 years ago
- Status changed from New to Closed
Changed Metacat's ResourceHandler to use the correct nodeId URL.
#8 Updated by Chris Jones about 13 years ago
- Status changed from Closed to In Progress
After discussion, reporting the Metacat node id property isn't necessarily correct since the node id may not be a URI, but rather a symbolic name. Re-opening this issue to deal with the difference.
#9 Updated by Chris Jones almost 13 years ago
- Status changed from In Progress to Closed
Modified ResourceHandler to construct the base URL from the server name and port using the SystemUtil.getContextURL() method.
