You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Dave Kale (JIRA)" <ji...@apache.org> on 2011/03/11 22:59:59 UTC
[jira] Updated: (OODT-154) Flexible response handling for XMLPS
[ https://issues.apache.org/jira/browse/OODT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Kale updated OODT-154:
---------------------------
Description:
So XMLPS's default output is "ERNE Rows" (foolishly and confusingly renamed "CDE Rows"): with tuples delimited by $'s and attributes in a tuple delimited by tabs. No doubt very useful for ERNE/EDRN, but for our purposes at CHLA, we'd love to just get CSVs (for extraction to files) or JSON (to make it play nicer with a PHP web front-end). Chris suggested we change XMLPS to allow custom, configurable response writing, so I'm going to take on that task. Not sure what it will involve (yet), but roughly I plan to do the following:
1. Change XMLPS to allow configurable response writing.
2. Make the "ERNE Rows writer" the default.
3. Add a CSV writer.
4. Add a JSON writer.
was:
So XMLPS's default output is "ERNE Rows" (foolishly and confusingly renamed "CDE Rows"): with tuples delimited by $'s and attributes in a tuple delimited by tabs. No doubt very useful for ERNE/EDRN, but for our purposes at CHLA, we'd love to just get CSVs. Chris suggested we change XMLPS to allow custom, configurable response writing, so I'm going to take on that task. Not sure what it will involve (yet), but roughly I plan to do the following:
1. Change XMLPS to allow configurable response writing.
2. Make the "ERNE Rows writer" the default.
3. Add a CSV writer.
> Flexible response handling for XMLPS
> ------------------------------------
>
> Key: OODT-154
> URL: https://issues.apache.org/jira/browse/OODT-154
> Project: OODT
> Issue Type: New Feature
> Components: xmlps
> Affects Versions: 0.3
> Reporter: Dave Kale
> Assignee: Dave Kale
>
> So XMLPS's default output is "ERNE Rows" (foolishly and confusingly renamed "CDE Rows"): with tuples delimited by $'s and attributes in a tuple delimited by tabs. No doubt very useful for ERNE/EDRN, but for our purposes at CHLA, we'd love to just get CSVs (for extraction to files) or JSON (to make it play nicer with a PHP web front-end). Chris suggested we change XMLPS to allow custom, configurable response writing, so I'm going to take on that task. Not sure what it will involve (yet), but roughly I plan to do the following:
> 1. Change XMLPS to allow configurable response writing.
> 2. Make the "ERNE Rows writer" the default.
> 3. Add a CSV writer.
> 4. Add a JSON writer.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira