GeoServer

Add support for GML encoding in RSS/Atom output formats

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1-RC2
  • Fix Version/s: 2.1-RC3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

Hi Justin,
here is a patch that follows your suggestion to build a bridge between translators and content handlers.

It seems to be working fine, however there is a catch: I had to work around an issue in the end element method, the Encoder never provides the proper qName so I had to qualify with the prefix it in the bridge instead. I guess it is because the start method in the Encoder uses the namespace support, whilst the end method does not.

Anyways, what do you think, ok to commit?

Show
Andrea Aime added a comment - Hi Justin, here is a patch that follows your suggestion to build a bridge between translators and content handlers. It seems to be working fine, however there is a catch: I had to work around an issue in the end element method, the Encoder never provides the proper qName so I had to qualify with the prefix it in the bridge instead. I guess it is because the start method in the Encoder uses the namespace support, whilst the end method does not. Anyways, what do you think, ok to commit?
Hide
Permalink
Justin Deoliveira added a comment -

Nice! +1 on the patch. Please commit as you please.

Do you mind if I push this back into geotools (sometime in the future... probably after the upcoming release). I think it could be of general utility.

About the encoder namespace issue... I think its fixable. If there is no prefix available from the element being encoded we do have the namespace context so can fall back on that to figure out what the default prefix is or should be.

Nice work.

Show
Justin Deoliveira added a comment - Nice! +1 on the patch. Please commit as you please. Do you mind if I push this back into geotools (sometime in the future... probably after the upcoming release). I think it could be of general utility. About the encoder namespace issue... I think its fixable. If there is no prefix available from the element being encoded we do have the namespace context so can fall back on that to figure out what the default prefix is or should be. Nice work.
Hide
Permalink
Andrea Aime added a comment -

About backporting, nice idea, +1
About the namespace issue, also proceed as you see fit

Show
Andrea Aime added a comment - About backporting, nice idea, +1 About the namespace issue, also proceed as you see fit
Hide
Permalink
Andrea Aime added a comment -

Fixed on 2.1.x and trunk

Show
Andrea Aime added a comment - Fixed on 2.1.x and trunk
Hide
Permalink
Andrea Aime added a comment -

Mass closing all issues that have been in "resolved" state for more than a month without further comments

Show
Andrea Aime added a comment - Mass closing all issues that have been in "resolved" state for more than a month without further comments

People

  • Assignee:
    Andrea Aime
    Reporter:
    Andrea Aime
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: