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

Larry McCay commented on KNOX-485:
----------------------------------

Hi [~andreina] - I am curious whether this is causing an issue for you. 
Can you describe the scenario where this is an issue?
I don't think that I would have a problem with a patch to address this as long 
as the default behavior continues to be the current behavior and the 
configuration would only be used to override it.

> Gateway deployment directory value is been hardcoded , instead of value being 
> read from exposed configuration.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: KNOX-485
>                 URL: https://issues.apache.org/jira/browse/KNOX-485
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.5.0
>            Reporter: J.Andreina
>
> Issue1 :
> ======
> During Gateway startup , deployment directory value is been hardcoded , 
> instead of value being read from available configuration .
> {noformat}
>   @Override
>   public String getGatewayDeploymentDir() {
>     return getGatewayDataDir() + File.separator + "deployments";
>   }
> {noformat}
> Issue2:
> ======
>    Configuration Name in gateway-default.xml is not same as the name used in 
> "org.apache.hadoop.gateway.config.impl.GatewayConfigImpl"
> {noformat}
>   private static final String GATEWAY_CONFIG_FILE_PREFIX = "gateway";
>   public static final String DEPLOYMENT_DIR = GATEWAY_CONFIG_FILE_PREFIX + 
> ".deployment.dir";
> {noformat}
> Incorrect Configuration name in gateway-default.xml
> {noformat}
>     <property>
>         <name>gateway.gateway.conf.dir</name>
>         <value>deployments</value>
>         <description>The directory within GATEWAY_HOME that contains gateway 
> topology deployments.</description>
>     </property>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to