Skip to content
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

camel-quarkus-activemq extension broker url configuration #1661

Closed
jwwallin opened this issue Aug 31, 2020 · 7 comments
Closed

camel-quarkus-activemq extension broker url configuration #1661

jwwallin opened this issue Aug 31, 2020 · 7 comments
Milestone

Comments

@jwwallin
Copy link

There doesn't seem to be any good way of configuring the ActiveMQ broker url for this extension. At the very least there is no documentation on how to do this.

@lburgazzoli
Copy link
Contributor

lburgazzoli commented Aug 31, 2020

Configuring component is not different from plain camel, depending on your set-up you have multiple options:

  • If you have camel-quarkue-main among the dependencies of your project, you can use the property camel.component.activemq.broker-url
  • If you run on plain CDI you can create your custom instance of the component see the bootsrtap guide

@jwwallin
Copy link
Author

jwwallin commented Aug 31, 2020

Thanks for the quick answer. I resorted to using the second option you gave as it was the only one I could find on my own.

I do still think this information should be clearly stated in the documentation for this extension. There is no indication that you would need to use either of these two approaches. It could be as simple as saying that with the camel-quarkus-main dependecy you can use the Spring Boot configuration properties.

@lburgazzoli
Copy link
Contributor

we can add it but in general components follow the same rules regardless of the runtime and if not, the difference are documented.

in this example, the documentation about this extension https://camel.apache.org/camel-quarkus/latest/reference/extensions/activemq.html redirects to the component guide as there are no difference

@jwwallin
Copy link
Author

True, it does point to the components documentation, but that doesn't help me if the way to use that information isn't clearly stated. My point here is that the necessary information should really be easy to access, easiest way being clearly stated in the context it applies. That could also just be a link to a tutorial on using camel-quarkus-main. My problem with this is solved so I'll close this issue.

@lburgazzoli
Copy link
Contributor

We probably need to reorganize the documentation in some areas, do you mind open an issue with some suggestions to the main camel project ?

@jwwallin
Copy link
Author

I'll happily do that but I didn't quite understand where exactly you mean. What do you mean by the "main camel project"?

@lburgazzoli
Copy link
Contributor

Well, as you know camel-quarkus is a sub-project of Apache Camel and since this issue is not quarkus specific, I'd recommend opening an issue against Camel (https://issues.apache.org/jira/projects/CAMEL)

@ppalaga ppalaga added this to the 1.2.0 milestone Oct 15, 2020
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

No branches or pull requests

3 participants