[jira] [Commented] (OODT-605) Upgrade the CAS-Product web application to use JAX-RS

["Ross Laidlaw (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642995#comment-13642995 ] 

Ross Laidlaw commented on OODT-605:
-----------------------------------

Below is a first draft project plan:


_April 29th to May 3rd (1 week)_

* Project planning
* Submit proposal to GSoC


_May 4th to May 26th (3 weeks)_

* Preparation work
** read up more on Apache CXF, JAX-RS
** finalize plans after discussion with OODT community


_May 27th to June 9th (2 weeks)_

* Add draft designs (e.g. UML) to JIRA
* Update project POM file (webapp/fmprod/pom.xml) to include Apache CXF
* Add new skeleton Java package for the JAX-RS(e.g. named org.apache.oodt.cas.product.service)


_June 10th to June 30th (3 weeks)_

* Add Java classes and XML configuration files to allow products and metadata to be served as resources via JAX-RS RESTful interface (URLs). (i.e. port DataDeliveryServlet and DatasetDeliveryServlet functionality to the new cas.product.service package)
** products retrieved by product ID
** product sets retrieved by product type
** returns product(s) and metadata as application/zip


_July 1st to July 21st (3 weeks)_

* Add Java classes and XML configuration files to allow information on products to be output as RDF streams via JAX-RS RESTful interface (URLs). (i.e. port RDFProductServlet and RDFDatasetServlet functionality to the new cas.product.service package)
** products retrieved by product ID
** product sets retrieved by product type (plus filtering, queries)
** add capability to retrieve information on current product transfers (as currently available in the RSS servlet)


_July 22nd to August 11th (3 weeks)_

* Add Java classes and XML configuration files to allow information on products to be output as RSS streams via JAX-RS RESTful interface (URLs). (i.e. port RSSProductServlet and RSSProductTransferServlet functionality to the new cas.product.service package)
** products retrieved by product ID
** product sets retrieved by product type (plus filtering, queries, including option to limit number of results returned)
** include capability to retrieve information on current product transfers


_August 12th to August 25th (2 weeks)_

* Add ways to configure the above services using XML configuration files


_August 26th to September 15th (3 weeks)_

* Extension: add Java classes and XML configuration files to allow information on products to be output in JSON format via JAX-RS RESTful interface (URLs).
** products, product sets and current transfers to be retrieved in a similar fashion to that used for the other services (parameters, filters, queries)


_September 16th to September 23rd (1 week)_

* finalize documentation - code comments, user guides
* close out JIRA issues
* prepare final reports and code samples

                
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
>                 Key: OODT-605
>                 URL: https://issues.apache.org/jira/browse/OODT-605
>             Project: OODT
>          Issue Type: New Feature
>          Components: product server
>    Affects Versions: 0.6
>            Reporter: Ross Laidlaw
>            Assignee: Ross Laidlaw
>              Labels: gsoc2013
>             Fix For: 0.6
>
>   Original Estimate: 3,360h
>  Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application (webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to provide additional ways of accessing File Manager products (e.g. providing different output formats for metadata, using additional parameters to find products and product groups).
> Other possibilities include: 
> - options to start and stop File Manager instances via the RESTful interface
> - options to initiate batch File Manager jobs via the RESTful interface
> - the ability to delete products via a REST URL (this might be too risky!)
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code project.
> I'm going to firm up the list of ideas and add a plan/schedule to this JIRA issue.  I'm hoping that if other members of the OODT community are interested they can find information here and make comments, suggestions, etc. and see how everything's progressing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira