[
https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-433:
-----------------------------------
Gary, thanks for all that -- makes sense.
have a default queue name configured in properties (not with a dtgov
specific name, so could potentially be used by any consumer)
My only concern with
that is shouldn't it be reserved solely for dtgov? What happens if dtgov is running,
but a user attempts to pop messages off the "default queue" at the same time?
Unless the other clients use a JMS session rollback (as I understand it), dtgov won't
receive it, right? That was the intention behind using a dtgov-specific queue. Or am I
missing something there?
I hadn't intended for the topic(s) to be configurable at all, but I suppose that might
make sense in certain situations.
if you use destinations, then you won't need to worry about
whether the jndi name refers to a topic or queue
Great point -- will do.
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)