[overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

Brett Meyer (JIRA) issues at jboss.org
Wed Jul 2 00:18:25 EDT 2014


    [ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981228#comment-12981228 ] 

Brett Meyer edited comment on SRAMP-433 at 7/2/14 12:16 AM:
------------------------------------------------------------

Thinking through all the use cases for the queues.  Thoughts on the following?

- configured in s-ramp properties file via JNDI names
- disabled by default
- dtgov-specific queue must be enabled during dtgov installation (or programmatically)
- allow clients to create additional queues on the JMS platform and list them on the config prop
- each event is sent to all registered queues w/ no expiration time


was (Author: brmeyer):
Thinking through all the use cases for the queues.  Thoughts on the following?

- configured in s-ramp properties file
- disabled by default
- dtgov-specific queue must be enabled during dtgov installation (or programmatically)
- allow clients to create additional queues on the JMS platform and list them on the config prop
- each event is sent to all registered queues w/ no expiration time

> Create a proper Event producer for s-ramp
> -----------------------------------------
>
>                 Key: SRAMP-433
>                 URL: https://issues.jboss.org/browse/SRAMP-433
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.6.0
>
>
> Currently dtgov monitors s-ramp for changes by polling.  It would be more efficient if dtgov could listen for events it cared about.
> Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the overlord-issues mailing list