Problem wih context name not unique

ith a different version it works. Any ideas? Thanks *Deploy log + Exception:* Set 18, 2015 10:15:52 AM org.apache.catalina.startup.HostConfig deployWAR INFORMAÇÕES: Deploying web application archive /home/ec2-user/apache-tomee-plus-1.7.2/webapps/cliente##20150918-1012.war Set 18, 2015 10:15:

Re: Problem wih context name not unique

deploy the same webapp with a > different version it works. > > Any ideas? > > Thanks > > > *Deploy log + Exception:* > > Set 18, 2015 10:15:52 AM org.apache.catalina.startup.HostConfig deployWAR > INFORMAÇÕES: Deploying web application archive > /home/ec2-user/apach

Re: Problem wih context name not unique

5:52 AM org.apache.catalina.startup.HostConfig deployWAR > > INFORMAÇÕES: Deploying web application archive > > /home/ec2-user/apache-tomee-plus-1.7.2/webapps/cliente##20150918-1012.war > > Set 18, 2015 10:15:52 AM org.apache.tomee.catalina.TomcatWebAppBuilder > init > > INFO

Dumb question: Is there a way to _not_ deploy the MDBs in a war?

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 b

Re: Dumb question: Is there a way to _not_ deploy the MDBs in a war?

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 F

Re: Dumb question: Is there a way to _not_ deploy the MDBs in a war?

Hi Jonathan, out of my head you can probably: - use a local broker (kind of "dead" broker) - use scan.xml to prevent the scanning of these MDBs (it is in WEB-INF) Romain Manni-Bucau @rmannibucau | Blog | Github