Need VSCode based screenshots for ActiveMQ integration
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 118
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 32
Description
Description
Followed the documentation below for connecting with ActiveMQ.
https://mi.docs.wso2.com/en/latest/install-and-setup/setup/brokers/configure-with-activemq/
It would be great if newer VSCode based screenshots of the low-code approach is documented.
Als in that context, the documentation has this URL - jms:/OMS?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory**&**java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=failover:(tcp://localhost:61616,tcp://localhost:61617)?randomize=false&transport.jms.DestinationType=queue
note the & in the URL. This needs to be clearly mentioned as applicable when editing the XML in the editor. When entering in the UI it has to be just '&'. Better to state it explicitly to avoid confusion.
Steps to Reproduce
Use low-code and try the same URL as in the documentation. It'll fail.
Reason is you don't need '&'. What needed in only '&'.
Component/Product
Product/mi
Environment Details (with versions)
No response
Relevant Log Output
Related Issues
No response
Suggested Labels
MI, documentation
Steps to Reproduce
Refer to above
Version
N/A
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
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 ActiveMQ integration documentation page linked in the issue and locate its low-code instructions and connection URL example. Update the page with newer VSCode-based screenshots and clearly distinguish the XML form using '&' from the UI form using '&'; done when the documented low-code flow and URL work without confusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100