[
https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin....
]
Eric Wittmann commented on SRAMP-433:
-------------------------------------
One thing I would add is that I don't think queue or topic configuration should be
done by storing that information in s-ramp itself. While it's true that we are moving
some of the DTGov config information from dtgov.properties into S-RAMP artifacts, I
don't necessarily think this config is applicable. On the S-RAMP (producer) side,
there is no precedent for storing config in the repo. On the DTGov (consumer) side, it
might make more sense but thus far we have only moved configuration into the S-RAMP repo
for stuff that users are likely to "frequently" change (ie more than just
initial app config 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)