[
https://issues.apache.org/jira/browse/OOZIE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633476#comment-13633476
]
Hadoop QA commented on OOZIE-1234:
----------------------------------
Testing JIRA OOZIE-1234
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 4 line(s) longer than 132
characters
. {color:green}+1{color} the patch does adds/modifies 10 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:red}-1 JAVADOC{color}
. {color:red}-1{color} the patch seems to introduce 25 new Javadoc warning(s)
{color:red}-1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 2 new javac warning(s)
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1135
. Tests failed: 1
. Tests errors: 14
. The patch failed the following testcases:
. testDoneFlagCreation(org.apache.oozie.TestCoordinatorEngine)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/443/
> JMS Event Listeners for publishing notifications related to workflow and
> coordinator
> ------------------------------------------------------------------------------------
>
> Key: OOZIE-1234
> URL: https://issues.apache.org/jira/browse/OOZIE-1234
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Fix For: trunk
>
> Attachments: jms_notification_spec.docx, OOZIE-1234_1235.patch,
> OOZIE-1234_1235.patch
>
>
> The event listeners will emit notifications for workflow, coordinator and SLA
> events. There are different ways of sending notifications like through JMS or
> email.
> This JIRA will focus on JMS Event listeners for workflow and coordinator
> related events.
> JMS implementation of event listener will send messages on a particular topic
> In addition to the JMS payload, the notification message will have properties
> on which the consumers can apply selectors to filter messages at JMS server.
> The JMS event message will be serialized and Oozie will also provide a helper
> class for consumers to deserialize these messages back to Java Objects.
> Classes
> EventMessage: There can be different event messages like
> WorkflowJobSuccessMessage, WorkflowJobFailureMessage similar to different
> events in OOZIE-1209
> EventListener: Listener to publish event messages on msg bus. One
> implementation will be JMSWorkflowEventlistener for publishing workflow
> related event messages
> MessageFactory: Factory for providing serializer, deserializer and creating
> Oozie event messages instances
> MessageSerializer: Serialize the JMS messages. One implementation can be
> JSONMessageSerializer to send the messages as JSON string.
> MessageDeserializer: Class to convert the serialized string back to Java
> Event Messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
