[
https://issues.apache.org/jira/browse/OOZIE-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574224#comment-14574224
]
Jaydeep Vishwakarma commented on OOZIE-2259:
--------------------------------------------
[~sriksun], Please check my reply below
# Yes like others workflowactions retry will be available.
# Yeah, Idea is same, I will correct the syntax.
# Yes I will do same.
# Just want to keep it simple.
# I understand why capture-output is useful. yes I will keep it. We can keep
response code as capture output.
# Yes it is just callback notification. I am not sure if anyone will need the
response body. We can enhance further if we get requirement.
# As mentioned in #5, We can get this information from capture output.
# We do not need launcher, The implementation would be same as
FsActionExecutor/EmailActionExecutor.
> Create a callback action
> -------------------------
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
> Issue Type: New Feature
> Components: action
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
>
> Need an action to send notification to external server by oozie. We should be
> able to do multiple types of callback, Currently I know jms and http call. It
> should suppose to have capability to call diffrent types of methods along
> with n number of arguments.
> The sample workflow with callback action
> {code:xml}
> <workflow-app name="[WF-DEF-NAME]" xmlns="uri:oozie:workflow:0.3">
> ...
> <action name="[NODE-NAME]">
> <callback>
> <host>[HOST]</host>
> <method>[METHOD]</command>
> <arg>
> <key>[KEY]</key><value>[VALUE]</value>
> <arg>
> ...
> </action>
> ...
> </callback>
> ...
> </workflow-app>
> {code}
> HOST : by the host system can figure out if it is http or jms callback
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
