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

Andrew Hart commented on OODT-139:
----------------------------------

Got this working locally, and it ROCKS. There were just a couple sticking 
points for me:

* the PCS core package assumes the existence of three environment variables: 
FILEMGR_URL, WORKFLOW_URL, and RESMGR_URL. Setting these allowed me to continue
* trunk/pcs/services/src/main/webapp/META-INF/context.xml contains two local 
path variables that need to be set to the physical location of the 
pcs-crawlers.xml and pcs-workflow-statuses.xml respectively. (Both of these 
files exist in trunk/pcs/core/src/main/resources/


> PCS JAX-RS services
> -------------------
>
>                 Key: OODT-139
>                 URL: https://issues.apache.org/jira/browse/OODT-139
>             Project: OODT
>          Issue Type: New Feature
>          Components: pcs
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>              Labels: jaxrs, jsr311, pcs
>             Fix For: 0.3
>
>         Attachments: OODT-139.Mattmann.021311.patch.txt, 
> OODT-139.Mattmann.021411.2.patch.txt, OODT-139.Mattmann.021411.patch.txt
>
>
> Now that the PCS core is contributed, it would be great to not just have 
> command line versions and APIs for tools like pcs_stat, pcstrace and pcs_ll. 
> We should expose them over JAX-RS so that webapps can easily take advantage 
> of PCS services.

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

        

Reply via email to