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/01 02:34:29 UTC
[jira] Created: (OODT-122) Rest Services Package
Rest Services Package
---------------------
Key: OODT-122
URL: https://issues.apache.org/jira/browse/OODT-122
Project: OODT
Issue Type: New Feature
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
[jira] Updated: (OODT-122) Rest Services Package
Posted by "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 updated OODT-122:
-----------------------------------
Component/s: workflow manager
resource manager
push pull framework
pge wrapper framework
file manager
crawler
- classify
> 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
[jira] Updated: (OODT-122) Rest Services Package
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ramirez updated OODT-122:
------------------------------
Due Date: 25/Feb/11 (was: 06/Feb/11)
> 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
[jira] Commented: (OODT-122) Rest Services Package
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988990#comment-12988990 ]
Paul Ramirez commented on OODT-122:
-----------------------------------
I believe this approach accomplishes the best of both worlds and avoids a "goober" project where everything is clumped in one tree with a ball of services. A good side benefit of this approach is it will allow multiple versions of a services component to be installed and configured differently. For example, this means that it would be easy to install the filemgr-serivces war three times in different contexts simply configured differently to talk to different filemanagers. Originally I thought the "goober" approach would be best but as it now stands I think this will give OODT Rest Services the most modularity in practice.
> Rest Services Package
> ---------------------
>
> Key: OODT-122
> URL: https://issues.apache.org/jira/browse/OODT-122
> Project: OODT
> Issue Type: New Feature
> 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
[jira] Commented: (OODT-122) Rest Services Package
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994838#comment-12994838 ]
Paul Ramirez commented on OODT-122:
-----------------------------------
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
[jira] Issue Comment Edited: (OODT-122) Rest Services Package
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (OODT-122) Rest Services Package
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988995#comment-12988995 ]
Paul Ramirez commented on OODT-122:
-----------------------------------
I'll post a patch later this week (probably weekend) to show how the poms will be setup and the build artifacts created. This will give people something tangible to talk about.
> Rest Services Package
> ---------------------
>
> Key: OODT-122
> URL: https://issues.apache.org/jira/browse/OODT-122
> Project: OODT
> Issue Type: New Feature
> 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
[jira] [Updated] (OODT-122) Rest Services Package
Posted by "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 updated OODT-122:
-----------------------------------
Fix Version/s: (was: 0.3)
0.4
- push out
> 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.4
>
>
> 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