S
Scott Balmos
Hi all,
A new facet to my system design is starting to come up in my mind. See
my other thread, "Right use for JTA transactions?", for background
info. Some other services, like mailing lists, would be on physically
separate servers from the main webapp. The webapp would issue
management messages (like create new mailing list foo, etc) via JMS.
I was wondering if anyone's got any ideas on implementing JMS message
consuming in a "normal" Java application, which would run in a normal
JVM outside of any J2EE/Servlet container? In essence, I want these
service managers to be as lightweight as possible. I don't want to have
to run JBoss on each of the other servers just to run something like
Message Driven Beans.
Ideas? Thanks!
--Scott
A new facet to my system design is starting to come up in my mind. See
my other thread, "Right use for JTA transactions?", for background
info. Some other services, like mailing lists, would be on physically
separate servers from the main webapp. The webapp would issue
management messages (like create new mailing list foo, etc) via JMS.
I was wondering if anyone's got any ideas on implementing JMS message
consuming in a "normal" Java application, which would run in a normal
JVM outside of any J2EE/Servlet container? In essence, I want these
service managers to be as lightweight as possible. I don't want to have
to run JBoss on each of the other servers just to run something like
Message Driven Beans.
Ideas? Thanks!
--Scott