You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Paul Ramirez (JIRA)" <ji...@apache.org> on 2011/02/15 16:23:57 UTC

[jira] Issue Comment Edited: (OODT-122) Rest Services Package

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

Paul Ramirez edited comment on OODT-122 at 2/15/11 3:21 PM:
------------------------------------------------------------

Part of this should take the services built in OODT-139 and package them into this tree.

      was (Author: pramirez):
    Update this to take the services built in OODT-139 and package them into this tree.
  
> Rest Services Package
> ---------------------
>
>                 Key: OODT-122
>                 URL: https://issues.apache.org/jira/browse/OODT-122
>             Project: OODT
>          Issue Type: New Feature
>          Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
>    Affects Versions: 0.3
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>             Fix For: 0.3
>
>
> Create a REST services top level component with the following sub components: filemgr-services, workflow-services, and pcs-services. Filemanager and workflow services are for our core components and will build to a war project. PCS services will build to a war but will have cross cutting services and depend on filemgr and workflow services; this will be accomplished via a web overlay. UIs can then build on these services or tailor their own where necessary. This modularity will allow for a wide variety of deployment methods and would even allow the same set of filemanager services to be installed multiple times each configured to talk to a different filemgr. This breakdown will give us a clear path of where to develop services and will hopefully prevent duplication of effort.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira