spring-projects / spring-projects/spring-integration
Allow a JmsOutboundGateway to not require a connectionFactory on initalisation [INT-3618]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Patrick Altaie opened INT-3618 and commented
With Spring Integration 4.1.2.RELEASE, it is not possible to configure a JmsOutboundGateway without a Connection Factory reference. This means that if I want to/can only figure out a Connection Factory at runtime, I need to supply some kind of fake, dummy or generic CF which will never be used, and I would then set the connection factory to whichever one it is that I need.
I think it would be fruitful to somehow be able to support not having the connectionFactory property set, such that this can be determined later on.
I see that the JmsOutboundGateway uses the JmsTemplate, which also has this limitation, so I'm not sure how feasible or easy to implement this would be.
Affects: 4.1.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the JmsOutboundGateway and JmsTemplate classes mentioned in the issue, tracing where the connectionFactory is required during initialization and how it is later used. Check the existing JMS gateway tests and determine whether runtime selection can work without a placeholder factory. Done means a gateway can initialize without a connectionFactory and use the required factory when the message is handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100