[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2699) Feed <updated> element needs to be updated even when only an entry is updated

Christian Bauer (JIRA) jira-events at lists.jboss.org
Mon Mar 3 11:29:09 EST 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2699?page=all ]

Christian Bauer closed JBSEAM-2699.

    Fix Version/s: 2.1.0.GA
       Resolution: Done

Done but with a twist: The Rome generator doesn't have a syndFeed.setUpdatedDate() method, only setPublishedDate(). It actually abuses that date to set the <updated> timestamp in Atom feeds. That means with Rome you can not have a publication and and update timestamp in the same Atom feed XML output.

> Feed <updated> element needs to be updated even when only an entry is updated
> -----------------------------------------------------------------------------
>                 Key: JBSEAM-2699
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2699
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Wiki
>            Reporter: Christian Bauer
>         Assigned To: Christian Bauer
>            Priority: Critical
>             Fix For: 2.1.0.GA
> The atom specification says that the <updated> element of a <feed> has to be updated when an <entry> of the feed changes "in a significant way".
> I was naive and believed that conditional HTTP GET and timestamps on the feed entries are good enough for clients to handle caching/refresh etc. So the wiki does not update the feed timestamp when an entry is added, removed or modified. This needs to be implemented.
> http://atomenabled.org/developers/syndication/atom-format-spec.php#element.updated

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list