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 2010/08/28 01:06:55 UTC
[jira] Created: (OODT-29) Import (ERNE) XMLPS component
Import (ERNE) XMLPS component
-----------------------------
Key: OODT-29
URL: https://issues.apache.org/jira/browse/OODT-29
Project: OODT
Issue Type: Task
Environment: XML configurable Product- and Profile- server package for connecting to databases
Reporter: Dave Kale
Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
1. Add apache license headers.
2. New unit tests that aren't dependent on details specific to the ERNE project.
3. Testing.
I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909967#action_12909967 ]
Dave Kale commented on OODT-29:
-------------------------------
P.S. Apply my patch from within "trunk."
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-29:
----------------------------------
Fix Version/s: 0.1-incubating
let's try and get this in for 0.1-incubating
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: Task
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann reassigned OODT-29:
-------------------------------------
Assignee: Chris A. Mattmann
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OODT-29) Import (ERNE) XMLPS
component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909967#action_12909967 ]
Dave Kale edited comment on OODT-29 at 9/15/10 8:26 PM:
--------------------------------------------------------
PROTIP: Apply my patch from within "trunk."
was (Author: davekale):
P.S. Apply my patch from within "trunk."
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-29:
----------------------------------
Issue Type: New Feature (was: Task)
- reclassify as New Feature, since it's a code contribution, not a task.
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909097#action_12909097 ]
Chris A. Mattmann commented on OODT-29:
---------------------------------------
Dave (Woollard):
Thanks for looking at the patch and for attaching the example pom. It looks like all tests pass RAT muster save those 2 example files you mentioned. I think it's pretty easy to handle adding the license headers to the example files, so I'll take care of it.
Dave (Kale):
Thanks again for your patch! Overall I'd say it's an awesome port of the old EDRN handler. I plan on finding a better name for that property as you suggested. You mentioned you had some unit tests. Feel free to submit them when you have time. In the meanwhile i'll try and add a few simple tests when I commit.
If there are no objections I plan on committing this in the next 48 hours.
Cheers,
Chris
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Kale updated OODT-29:
--------------------------
Attachment: oodt-xmlps.diff
Updated the patch to add headers to the example config files and removed the "fix" for grid (which I will upload separately).
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Kale updated OODT-29:
--------------------------
Attachment: oodt-xmlps+grid_ignore_target.diff
XMLPS successfully converted to new Apache namespace, along with the following four changes and two caveats:
1. Added Apache License headers, though RAT still breaks when you try to do "mvn install." Something about unapproved licenses. Really annoying. I was very tempted to comment out the RAT lines in the pom file... :-D
2. Removed references to ERNE/EDRN and renamed things when appropriate.
3. Removed unit tests because they depended on access to an ERNE/EDRN database! Needs new unit tests!
4. Modified the MappingReader, Mapping, etc., to have one additional tag for the field element: a boolean called "apptabname" that tells the code assembling the SQL query whether to append the table name to the field name. This affects not only the SQL query but also the string keys that are used to retrieve results from the ResultSet (or whatever it's called...too tired to remember...); for our database, the query
SELECT TableName.FieldName FROM TableName
would give results, but the column name was just "FieldName," which meant that the following line in DBMSExecutor:
CDERow row = toCDERow(rs, map, returnNames);
returned nulls. Now you can configure this behavior. I recommend changing the tag, though; "apptabname" is pretty inscrutable.
CAVEAT #1: I'm new to maven, so please check the pom file with a fine-toothed comb.
CAVEAT #2: This builds and has been successfully used on our database, but by all means please check it and test it, because I made the changes in a hurry!
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: Task
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908850#action_12908850 ]
Chris A. Mattmann commented on OODT-29:
---------------------------------------
Hi Dave,
First off, thanks! I haven't had a chance to review the patch yet, but I'll check it out. We should try and get some unit tests in there. I also agree about renaming the property to something more appropriate.
Thanks for your hard work on this!
Cheers,
Chris
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: Task
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908860#action_12908860 ]
Dave Kale commented on OODT-29:
-------------------------------
FYI, in the course of teaching myself how to use this component, I am writing new unit tests. Soon as the module is checked in and added to the repository, I will send a new patch with unit tests.
Dave
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OODT-29) Import (ERNE) XMLPS
component
Posted by "Andrew Hart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909100#action_12909100 ]
Andrew Hart edited comment on OODT-29 at 9/13/10 11:02 PM:
-----------------------------------------------------------
> If there are no objections I plan on committing this in the next 48 hours.
+1 and a big thank you Dave (Kale) for preparing this patch!!
was (Author: ahart):
bq. If there are no objections I plan on committing this in the next 48 hours.
+1 and a big thank you Dave (Kale) for preparing this patch!!
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-29.
-----------------------------------
Resolution: Fixed
- patch applied in r997583 and r997584 with the following changes:
- took out "hack" in o.a.xmlps.product.DBMSExecutor
- formatting
- removed XMLUtils (ported to use oodt-commons version)
- removed calls to build conn to DB and replaced with DatabaseConnectionBuilder provided by oodt-commons
- changed name of field to "appendTableName"
- updated documentation in example files: ERNEResult=>CDEResult
- added unit tests back in (generalized them)
- updated pom for unit tests to hide log output and copy test resources
Thanks to Dave Kale for pushing forward and tackling this huge project! Thanks to ahart and woollard for additional contributions, including code porting, RAT review and updating the pom.xml!
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Andrew Hart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909100#action_12909100 ]
Andrew Hart commented on OODT-29:
---------------------------------
bq. If there are no objections I plan on committing this in the next 48 hours.
+1 and a big thank you Dave (Kale) for preparing this patch!!
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Dave Kale (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Kale updated OODT-29:
--------------------------
Attachment: (was: oodt-xmlps+grid_ignore_target.diff)
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Assignee: Chris A. Mattmann
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "David Woollard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Woollard updated OODT-29:
-------------------------------
Attachment: xmlps.rat.txt
pom.xml
Regarding RAT, there was some discussion on the email list regarding its use and you'll notice that we actually only incorporated for the sub-projects that have already been vetted for licensing issues. If you want, while importing code, you can not include it as part of the pom file (or comment it out).
I applied the patch and looked specifically at the licensing and it all looks good save the two example files you have. I have also attached a modified pom file that includes an exclude statement that will allow RAT to ignore the two example files.
As an alternative, you can add licensing info to the examples. The only reason we have not added it to other examples is when the addition would adversely effect the use of the example.
-Dave
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml, xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-29:
----------------------------------
Component/s: product server
profile server
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: Task
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-29) Import (ERNE) XMLPS component
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908865#action_12908865 ]
Chris A. Mattmann commented on OODT-29:
---------------------------------------
Awesome, thanks Dave.
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in databases (welcome to health IT...everything lives in normalized M$ SQL servers). The XMLPS package from ERNE makes it easy to deploy rapidly product servers, profile servers, and query handlers by separating the mechanisms for setting up connections, parsing queries, etc. (which lives in java code) from the data definitions, i.e., table names, field names, etc. (which are defined in XML-based configuration files). This probably requires the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the apache namespace and removed or generalized ERNE-specific naming conventions. The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.