You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Dan Becker (JIRA)" <de...@tuscany.apache.org> on 2008/08/13 20:06:44 UTC
[jira] Created: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Atom Feed sorting algorithm should depend on Updated field, not Published field
-------------------------------------------------------------------------------
Key: TUSCANY-2548
URL: https://issues.apache.org/jira/browse/TUSCANY-2548
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.3
Environment: All OSs, All JVMs
Reporter: Dan Becker
Priority: Minor
Atom Feed sorting algorithm should depend on Updated field, not Published field.
According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Posted by "Dan Becker (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker updated TUSCANY-2548:
--------------------------------
Attachment: TUSCANY-2548.patch
Patch provides update to use updated field instead of published for sorting.
> Atom Feed sorting algorithm should depend on Updated field, not Published field
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2548
> URL: https://issues.apache.org/jira/browse/TUSCANY-2548
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.3
> Environment: All OSs, All JVMs
> Reporter: Dan Becker
> Priority: Minor
> Attachments: TUSCANY-2548.patch
>
>
> Atom Feed sorting algorithm should depend on Updated field, not Published field.
> According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Posted by "Dan Becker (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker updated TUSCANY-2548:
--------------------------------
Patch Info: [Patch Available]
> Atom Feed sorting algorithm should depend on Updated field, not Published field
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2548
> URL: https://issues.apache.org/jira/browse/TUSCANY-2548
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.3
> Environment: All OSs, All JVMs
> Reporter: Dan Becker
> Priority: Minor
>
> Atom Feed sorting algorithm should depend on Updated field, not Published field.
> According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Posted by "Luciano Resende (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Resende resolved TUSCANY-2548.
--------------------------------------
Resolution: Fixed
Patch applied under svn revision #685663.
> Atom Feed sorting algorithm should depend on Updated field, not Published field
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2548
> URL: https://issues.apache.org/jira/browse/TUSCANY-2548
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.3
> Environment: All OSs, All JVMs
> Reporter: Dan Becker
> Assignee: Luciano Resende
> Priority: Minor
> Attachments: TUSCANY-2548.patch
>
>
> Atom Feed sorting algorithm should depend on Updated field, not Published field.
> According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Posted by "Luciano Resende (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Resende reassigned TUSCANY-2548:
----------------------------------------
Assignee: Luciano Resende
> Atom Feed sorting algorithm should depend on Updated field, not Published field
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2548
> URL: https://issues.apache.org/jira/browse/TUSCANY-2548
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.3
> Environment: All OSs, All JVMs
> Reporter: Dan Becker
> Assignee: Luciano Resende
> Priority: Minor
> Attachments: TUSCANY-2548.patch
>
>
> Atom Feed sorting algorithm should depend on Updated field, not Published field.
> According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2548) Atom Feed sorting algorithm should
depend on Updated field, not Published field
Posted by "Dan Becker (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Becker closed TUSCANY-2548.
-------------------------------
> Atom Feed sorting algorithm should depend on Updated field, not Published field
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2548
> URL: https://issues.apache.org/jira/browse/TUSCANY-2548
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.3
> Environment: All OSs, All JVMs
> Reporter: Dan Becker
> Assignee: Luciano Resende
> Priority: Minor
> Attachments: TUSCANY-2548.patch
>
>
> Atom Feed sorting algorithm should depend on Updated field, not Published field.
> According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.