-
1. Re: HornetQ support for REST API in standalone mode
clebert.suconic Dec 2, 2011 5:40 PM (in response to adridi)It's probably a simple change on the Rest implementation. If someone change it.. we can commit it right away with a patch.
-
2. Re: HornetQ support for REST API in standalone mode
adridi Dec 2, 2011 5:45 PM (in response to clebert.suconic)That will be Great Clebert!
-
3. Re: HornetQ support for REST API in standalone mode
adridi Dec 5, 2011 3:19 PM (in response to adridi)So do we need to create a jira to track this feature?
-
4. Re: HornetQ support for REST API in standalone mode
clebert.suconic Dec 5, 2011 10:09 PM (in response to adridi)We already have a JIRA for this as I remember... I don't remember the number now.. I can look it up tomorrow
-
5. Re: HornetQ support for REST API in standalone mode
adridi May 1, 2012 6:13 PM (in response to clebert.suconic)Clebert,
Looking at the 2.2.14.final release doc, it seems that the REST support for standalone didnt make it.
Any recomended workaround for this?
-
6. Re: HornetQ support for REST API in standalone mode
dcorner Dec 12, 2012 8:17 PM (in response to adridi)Did REST in standalone make it into 2.3 ?
-
7. Re: HornetQ support for REST API in standalone mode
jbertram Dec 12, 2012 10:01 PM (in response to dcorner)Reading through this thread, I'm not sure I understand the use-case. Can you elaborate on this for me?
Right now (i.e. in 2.3) HornetQ REST is only viable when HornetQ is deployed alongside a servlet container (e.g. in JBoss AS, Tomcat, etc.).
-
8. Re: HornetQ support for REST API in standalone mode
dcorner Dec 13, 2012 3:15 PM (in response to jbertram)THe environment is a specialized server running on WIndows with add in code only in C++. I would like to run the standalone HornetQ to provide distribution of messages to multiple clients. We will have a single publisher in the same system and multiple subscriber clients on other systems. We need support for JMS and either REST or STOMP or both as some clients will be in a C++ environment. It sounds like we need to run Tomcat in order to have an applet container to support REST. Another question is the issue of being also to provide REST and STOMP. The documentation indicates that this is a problem; ObjectMessage for REST vs TextMessage for STOMP. Is there any way around this? If I can only have one of them which would you recommend?
-
9. Re: HornetQ support for REST API in standalone mode
jbertram Dec 13, 2012 3:59 PM (in response to dcorner)It sounds like we need to run Tomcat in order to have an applet container to support REST.
To be clear, you need a servlet container, not an applet container. You can use Tomcat for this or JBoss AS or even TJWS (which is what the HornetQ REST test-suite uses). I don't see us removing the servlet container requirement anytime soon (if ever).
Another question is the issue of being also to provide REST and STOMP. The documentation indicates that this is a problem; ObjectMessage for REST vs TextMessage for STOMP. Is there any way around this? If I can only have one of them which would you recommend?
You should start a new thread about this since you've moved off-topic now.
-
10. Re: HornetQ support for REST API in standalone mode
jbertram Dec 13, 2012 4:17 PM (in response to dcorner)BTW, I believe Clebert was referring to HORNETQ-762 which would just de-couple the HornetQ instance from the servlet container. A servlet container would still be required.
-
11. Re: HornetQ support for REST API in standalone mode
adridi Dec 13, 2012 4:22 PM (in response to jbertram)That's correct - but not sure when will this be fixed?
Any idea?
-
12. Re: HornetQ support for REST API in standalone mode
jbertram Dec 13, 2012 5:07 PM (in response to adridi)I can't say for sure when this will be fixed. At this point there are other, higher-priority tasks.