7612 - fix(ingest): No more JNDI lookup fails during deploy #7613
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
As we produce the JMS topic and factory for Ingest in
IngestQueueProducer
since Dataverse 5.3, error messagesabout unsupported missing message-destination appeared.
This commit fixes the underlying cause by using lookup()
instead of name() for the @resource dependency injection.
Which issue(s) this PR closes:
Closes #7612
Special notes for your reviewer:
Needs manual testing of Ingest!
Suggestions on how to test this:
Usual setup. Try real ingest, so the JMS part is actually used. Not sure API tests already cover that.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
None.
Is there a release notes update needed for this change?:
Nope.
Additional documentation:
None.