-
Notifications
You must be signed in to change notification settings - Fork 17
Feature/activemq camel stomp #698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
According to the documentation: https://activemq.apache.org/components/artemis/documentation/2.19.0/using-jms.html tunneling the TCP connection over HTTP is supported by adding Interestingly enough, setting up the client subscription as durable, the client will receive all missed messages before the ClassCastException is thrown (but no further messages are sent to the client). I don't know if this error was fixed in a newer version of Artemis as JDK 11 is required beyond the 2.19.1 version I am testing. I did update the client to the latest version and that didn't change anything. |
…ut through ActiveMQ Artemis utilizes Apache Camel with the AQAPI connection factory in order to hook into Oracle Queues and route to Artemis. TODOs: - determine artemis connection/port - determine which oracle queues to subscribe to - determine clientid/durable subscriber name - register artemis queues with swagger UI and standardize naming artemis architecture docs: https://activemq.apache.org/components/artemis/documentation/2.4.0/architecture.html
…et test. Reworked CamelServletContextListener.java to switch servlet annotation, and revise message connections and endpoints. Added a new package.json file for websocket-testing and a processor for message-to-json processing. Created a new javascript file for testing STOMP over websockets using node.js. This commit lays the groundwork for more effective messaging and debugging.
2da9087
to
4b9bde3
Compare
groups routes for office as well as individual routes add basic security mechanism that requires client to specify username and apikey for the password create a specific cda apikey for authenticating within the vm
4b9bde3
to
7e0cc56
Compare
Known issues that should get addressed:
|
Uh oh!
There was an error while loading. Please reload this page.