[jira] Resolved: (OODT-29) Import (ERNE) XMLPS component

["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.