[jira] [Resolved] (OODT-122) Rest Services Package

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OODT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-122.
------------------------------------

    Resolution: Later

It's been 2 years on this one, and I'm more a fan of the build services (JAX-RS) in each package, which is occurring (see fmprod and workflow CXF services). If someone wants to build a package like this, please do so, but for now I'm closing it.

> 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.7
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)