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

Robert Kanter commented on OOZIE-1347:
--------------------------------------

I think something went bad in the commit; some of the files are empty after 
this comment and are showing up as RAT warnings in Jenkins builds now:

{noformat}
core/src/test/java/org/apache/oozie/command/TestJMSInfoXCommand.java
core/src/test/java/org/apache/oozie/jms/TestJMSServerInfo.java
core/src/main/java/org/apache/oozie/command/JMSInfoXCommand.java
core/src/main/java/org/apache/oozie/jms/DefaultJMSServerInfo.java
core/src/main/java/org/apache/oozie/jms/JMSServerInfo.java
{noformat}

[~virag], can you look into this?  
                
> Additions to JMS topic API
> --------------------------
>
>                 Key: OOZIE-1347
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1347
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Virag Kothari
>            Assignee: Virag Kothari
>             Fix For: trunk
>
>         Attachments: OOZIE-1347.patch, OOZIE-1347.patch, OOZIE-1347.patch, 
> OOZIE-1347.patch, OOZIE-1347.patch
>
>
> This JIRA will make the following changes from API in OOZIE-1235
> OozieClient will have two API's
> JMSConnectionInfo getJMSConnectionInfo() 
> String getTopicName(jobId);
> JMSConnectionInfo has the following API's
> Properties getJNDIProperties()
> String getTopicPrefix()
> String getTopicPattern(AppType appType)
> TopicPattern will the pattern configured in oozie-site.xml
> E.g ${username}, ${jobId} or a fixed string like WORKFLOW
> This JIRA also addresses comments by Rohini on OOZIE-1234 and OOZIE-1235
> Some of them are:
> Make the JMSMessagingUtils.getEventmessage() return a generic subtype
> Fix some of implementation related to thread local session and connection.
> Remove JMSServerInfo 
> Few other issues

--
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

Reply via email to