[
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304166#comment-14304166
]
Harsh J commented on OOZIE-2060:
--------------------------------
We should be able to add the -conf method with a short note that the filename
may be subject to change? It is still a good addition nevertheless.
In Shell actions one can use the resolving env-var $OOZIE_CONF_ACTION_XML
though, and such a thing could be passed to -conf if one were using that.
Maybe we can provide a new feature in Oozie via an EL function or so that
returns the XML filename/path, if it seems possible to do, and Java action
users can call it to get the current action's XML? I've not looked into if this
would be possible, but such a thing would fit into the abstraction.
It is unlikely we'll ever change the action.xml filename, but the current
user-facing parts do appear to be built to hide it in.
> Incorrect documentation of Java action config XML filename
> ----------------------------------------------------------
>
> Key: OOZIE-2060
> URL: https://issues.apache.org/jira/browse/OOZIE-2060
> Project: Oozie
> Issue Type: Sub-task
> Components: docs
> Affects Versions: 3.3.2, 4.0.0, 4.0.1
> Reporter: Ben Roling
> Priority: Minor
> Attachments: OOZIE-2060.patch, OOZIE-2060.patch
>
>
> The [documentation of Java
> action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
> suggests that Java action configuration is available in a file named
> "oozie-action.conf.xml".
> This does not seem to me to be true. My experience is that this
> configuration is available in "action.xml".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
