[
https://issues.apache.org/jira/browse/AIRAVATA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454018#comment-13454018
]
Raminderjeet Singh commented on AIRAVATA-568:
---------------------------------------------
i dont think its a bad design option. I can argue with a practical use case. I
have a gateway use case where all the workflow run on same topic but uniqueness
is handled using experimentID. Keep experiment id unique is required but not
the topic. Experimentid and topic should be treated separately and need to be
reflected in the API. I will appreciate if you look at AiravataClient code to
give your design suggestions.
> Method to set messaging topic from airavata client
> --------------------------------------------------
>
> Key: AIRAVATA-568
> URL: https://issues.apache.org/jira/browse/AIRAVATA-568
> Project: Airavata
> Issue Type: Improvement
> Reporter: Raminderjeet Singh
>
> These need to a method to set messaging topic from airavata API for advanced
> clients to sent the information
--
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
