Skip to content

Add ADR doc for JMS Message Structure#1774

Open
perrymanmd wants to merge 2 commits into
USACE:developfrom
perrymanmd:develop
Open

Add ADR doc for JMS Message Structure#1774
perrymanmd wants to merge 2 commits into
USACE:developfrom
perrymanmd:develop

Conversation

@perrymanmd

Copy link
Copy Markdown

Summary

Add ADR doc for JMS Message Structure

Related Issue

Closes #

Validation

No code changed

Checklist

  • AI tools used

@krowvin

krowvin commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Is it possible to add a nested structure to the queues?

I'm thinking in terms of topics vs queues

For example

timeseries/stored
or
timeseries/renamed
or - subscribe to all with
timeseries

This would let you subscribe to a topic containing multiple queues. Bringing this up now if we are deciding on a standard for naming of the queues.

@MikeNeilson

Copy link
Copy Markdown
Contributor

Is it possible to add a nested structure to the queues?

I'm thinking in terms of topics vs queues

For example

timeseries/stored or timeseries/renamed or - subscribe to all with timeseries

This would let you subscribe to a topic containing multiple queues. Bringing this up now if we are deciding on a standard for naming of the queues.

This ADR is documenting current state only. Follow up ADRs will address future semantics.

@MikeNeilson MikeNeilson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formatting looks fine to me, so does the content, seeing only a few responses were made we can call this sufficient.

However, 9 is the wrong number, please use 11 and add it to the index.rst in that folder.

(NOTE: I took the liberty of rebasing your PR, remember to pull changes before updating those.

Correct "javax.jms.MapMessage" to "jakarta.jms.MapMessage"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants