tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Fisher <>
Subject Re: Dumb question: Is there a way to _not_ deploy the MDBs in a war?
Date Fri, 18 Sep 2015 18:43:20 GMT
Would having two JMS connection pools work? Have one pool point at the real
broker and the REST apps use that in the producer. Have the other JMS Pool
point nowhere, but hook an MDB container up to it?

*Jonathan S. Fisher*
*VP - Information Technology*
*Spring Venture Group*
(o) 913-653-8820

On Fri, Sep 18, 2015 at 1:41 PM, Jonathan Fisher <> wrote:

> I know this is a really really weird scenario, but I'll ask anyway. If I
> have a war file that has some JMS producers and some MDB consumers, is
> there a way *not* deploy the MDBs?
> We have some RESTful web services that put messages on queues that are
> then processed later. The Database they use is behind our firewall, but
> we'd like to run a backup of the war in the cloud in case we lose
> connectivity to our datacenter. We cant'/don't want our database on the
> cloud due to HIPAA.
> If there is a way to do deploy an app without no MDBs, we won't have to
> split the application into two (REST only and MDB only). If there isn't, oh
> well, not a big deal.
> Thanks!
> *Jonathan S. Fisher*

Email Confidentiality Notice: The information contained in this 
transmission is confidential, proprietary or privileged and may be subject 
to protection under the law, including the Health Insurance Portability and 
Accountability Act (HIPAA). The message is intended for the sole use of the 
individual or entity to whom it is addressed. If you are not the intended 
recipient, you are notified that any use, distribution or copying of the 
message is strictly prohibited and may subject you to criminal or civil 
penalties. If you received this transmission in error, please contact the 
sender immediately by replying to this email and delete the material from 
any computer.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message