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:57:59 UTC
[jira] Created: (OODT-154) Flexible response handling for XMLPS
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. 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OODT-154) Flexible response handling for XMLPS
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Kale updated OODT-154:
---------------------------
Affects Version/s: (was: 0.3)
0.1-incubating
0.2
Fix Version/s: 0.3
Issue Type: Improvement (was: New Feature)
Changed to "improvement," corrected affects and fix versions.
> Flexible response handling for XMLPS
> ------------------------------------
>
> Key: OODT-154
> URL: https://issues.apache.org/jira/browse/OODT-154
> Project: OODT
> Issue Type: Improvement
> Components: xmlps
> Affects Versions: 0.1-incubating, 0.2
> Reporter: Dave Kale
> Assignee: Dave Kale
> Fix For: 0.3
>
>
> 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
[jira] [Updated] (OODT-154) Flexible response handling for XMLPS
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-154:
-----------------------------------
Fix Version/s: (was: 0.3)
0.4
> Flexible response handling for XMLPS
> ------------------------------------
>
> Key: OODT-154
> URL: https://issues.apache.org/jira/browse/OODT-154
> Project: OODT
> Issue Type: Improvement
> Components: xmlps
> Affects Versions: 0.1-incubating, 0.2
> Reporter: Dave Kale
> Assignee: Dave Kale
> Fix For: 0.4
>
>
> 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
[jira] [Assigned] (OODT-154) Flexible response handling for XMLPS
Posted by "Chris A. Mattmann (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann reassigned OODT-154:
--------------------------------------
Assignee: Chris A. Mattmann (was: Dave Kale)
> Flexible response handling for XMLPS
> ------------------------------------
>
> Key: OODT-154
> URL: https://issues.apache.org/jira/browse/OODT-154
> Project: OODT
> Issue Type: Improvement
> Components: xmlps
> Affects Versions: 0.1-incubating, 0.2
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OODT-154) Flexible response handling for XMLPS
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ 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