Additional JMS message types for forecasts, ratings, and location levels - #1883
Additional JMS message types for forecasts, ratings, and location levels#1883perrymanmd wants to merge 19 commits into
Conversation
Correct "javax.jms.MapMessage" to "jakarta.jms.MapMessage"
* rename 00010-vertical-datum.rst to 0010-vertical-datum.rst * move 0009-queue-messages.rst to 0011-queue-messages.rst * update index.rst for vertical-datum and add queue-messages
MikeNeilson
left a comment
MikeNeilson
left a comment
There was a problem hiding this comment.
Conceptually looks fine. For these let's leave out low level implementation details, like which Java package would be use. Message/Event systems are rather generic as a concept.
Additionally, some examples should be provided. The one implementation detail -> in JSON. Unless it just gets awkward and then XML. However, we should be fine with JSON.
| Summary | ||
| ======= | ||
|
|
||
| CWMS needs a JMS Pulish/Subscribe message structure to notify clients of forecast-related events. |
There was a problem hiding this comment.
| CWMS needs a JMS Pulish/Subscribe message structure to notify clients of forecast-related events. | |
| CWMS needs a Message structure to notify clients of forecast-related events. |
There was a problem hiding this comment.
or "Events" like above.
| Opinion 1 | ||
| --------- | ||
|
|
||
| Summary: Use the ``jakarta.jms.MapMessage`` structure described below for forecast-related events. |
There was a problem hiding this comment.
| Summary: Use the ``jakarta.jms.MapMessage`` structure described below for forecast-related events. | |
| Summary: Use the message structure described below for forecast-related events. |
|
|
||
| Summary: Use the ``jakarta.jms.MapMessage`` structure described below for forecast-related events. | ||
|
|
||
| All messages will be published to the ``XXX_REALTIME_OPS`` topic, where ``XXX`` represents the appropriate office identifier. |
There was a problem hiding this comment.
| All messages will be published to the ``XXX_REALTIME_OPS`` topic, where ``XXX`` represents the appropriate office identifier. | |
| All messages will be published to the appropriate ``REALTIME_OPS`` topic. Subscribers can setup appropriate filtering to receive desired messages. |
| @@ -0,0 +1,167 @@ | |||
| ======================================= | |||
| JMS Pub/Sub Message Formats - Forecasts | |||
There was a problem hiding this comment.
| JMS Pub/Sub Message Formats - Forecasts | |
| Data Event Formats - Forecasts |
Do you want the the "Value Type" columns in the tables to specify JSON types instead of Java types or leave them as they are? |
I think as they are is fine, they're fairly generic. |
2 participants
Summary
Additional JMS message types for forecasts, ratings, and location levels. Approval is required before addressing more object type
Related Issue
AQJMS Message for additional data types
Validation
Documentation only
Checklist