[jira] [Commented] (OODT-664) RADIX deployment of opsui incorrectly uses /pcs-opsui as the web.xml context and omits 2 key PCS properties from context.xml

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

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

Chris A. Mattmann commented on OODT-664:
----------------------------------------

Pull request here: https://github.com/apache/oodt/pull/3

> RADIX deployment of opsui incorrectly uses /pcs-opsui as the web.xml context and omits 2 key PCS properties from context.xml
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OODT-664
>                 URL: https://issues.apache.org/jira/browse/OODT-664
>             Project: OODT
>          Issue Type: Bug
>          Components: opsui, radix
>         Environment: RADIX any version with OPSUI
>            Reporter: Chris A. Mattmann
>            Assignee: Paul Ramirez
>             Fix For: 0.7
>
>
> We saw at the NSF RAPID meeting that the OPSUI out of the box references /pcs-opsui as the context which messes up data download in the File Catalog (fmbrowser) module. Easy fix is to change web.xml to ref /opsui. In addition the OPSUI omits 2 properties in the context.xml file that are are absolutely needed to run:
> {code:xml}
> 	<Parameter name="org.apache.oodt.pcs.trace.excludeList"
> 	    value=""/>
> 	
> 	<Parameter name="org.apache.oodt.pcs.trace.enableNotCat"
> 	    value="true"/>
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)