title: JMS Development Best Practice
body: <p>In production we have multiple containers deployed and any one can be a consumer of one JMS queue. In our development environment, we have multiple developers each with a container that will potentially consume messages. When a developer wants to test something related to JMS by putting something on the queue, though, the message is often consumed by someone else which can be be a time sink.</p>
  
  <p>We use the same build files for every environment. We do not want to accidentally deploy something to an upper environment that is meant strictly for the development environment.</p>
  
  <p>What is a best practice in handling something like this that will not involve build tokens, etc or building differently for different environments?</p>
  
  <p>We currently have the developer ask the other developers to comment out the consuming code, but this is a risk as the commented out code could accidentally get checked in.</p>
  
  <p>One potential way would be to store a property in the database that would change from environment to environment. </p>
  
  <p>How have you handled this?</p>