Opened 17 years ago
Closed 16 years ago
#66 closed defect (fixed)
Remove extraneous namespace nodes from search results
| Reported by: | rjwalker | Owned by: | fxp |
|---|---|---|---|
| Priority: | minor | Milestone: | v2.4.0 RC2 |
| Component: | General | Version: | v2.2.0 Final |
| Keywords: | Cc: |
Description
The various search result pages contain xalan, gco, and geonet namespace nodes. They are harmless, but they bugged me enough that I decided to remove them. (OK, it was more out of curiosity than fixing a real problem.) I attach the patch.
There might be other pages with the same "issue" . . . .
Innocent question number 1: should
exclude-result-prefixes="xalan geonet"
be
exclude-result-prefixes="geonet"
extension-element-prefixes="xalan"
instead?
Innocent question number 2: what's the reason for the use of xalan:nodeset instead of exsl:node-set?
Attachments (1)
Change History (3)
by , 17 years ago
| Attachment: | gnpatch7.txt added |
|---|
comment:1 by , 16 years ago
| Owner: | changed from to |
|---|
comment:2 by , 16 years ago
| Milestone: | → v2.4.0 RC2 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Committed revision 4355.
Also applied to search embedded.
Innocent question number 2: what's the reason for the use of xalan:nodeset instead of exsl:node-set?
Simon made an update on this. We are not using xalan nodeset function anymore.
Note:
See TracTickets
for help on using tickets.
Patch to remove extraneous namespace nodes