You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Ross Laidlaw (JIRA)" <ji...@apache.org> on 2013/04/26 15:16:15 UTC

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

Ross Laidlaw created OODT-605:
---------------------------------

             Summary: 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
             Fix For: 0.6


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 as 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