I'm not sure I can answer your questions with the information you've provided. You say that your use-case doesn't allow for any kind of WAR/servlet deployments, but you are presumably asking about deploying the REST WAR described in the documentation. That doesn't make sense to me. Also, you're asking about defining your own end-points in conjunction with the REST messaging interface, but the REST messaging interface has its own set of endpoints. It doesn't facilitate you defining your own endpoints. Maybe this all actually does make sense somehow, but I can't figure out what you're actually trying to do and how REST fits in. Please clarify.
Justin On Tue, Feb 20, 2018 at 2:46 PM, tcomprak <tcomp...@gmail.com> wrote: > However, I can say that Artemis already embeds the Jetty HTTP > server which is how it currently serves stuff like the REST management API > and the web console. You might just be able to use that > > >>>>> Sorry, I have a related question. Would using this server entail > >>>>> installing and configuring REST as described in > >>>>> https://activemq.apache.org/artemis/docs/1.0.0/rest.html ? The > problem > >>>>> I have is that my use case does not allow for any kind of WAR / > >>>>> servelet deployments. What I need is something very simple where the > >>>>> HTTP service can be started programmatically and I am able to define > >>>>> some end points. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
