...

would resolve to the following when -Dnv.ddl.profiles=test is set during DDL parsing:in the bootstrap environment.

<model>
  <env>
    <nv.discovery.descriptor>loopback://test&amp;initWaitTime=0</nv.discovery.descriptor>
  </env>
  <buses>
    <bus name="order-processing-bus" descriptor="loopback://order-processing"/>
      ...
    </bus>
  <buses>
</model>

And would resolve to the following if no nv.ddl.profiles were set (or none matching a the "test" profile name:

<model>
  <buses>
    <bus name="order-processing-bus" descriptor="activemq://activemq-host:61616">
      ...
    </bus>
  <buses>
</model>

Profile Activation Element

A profile can specify an <activation> element that can accept a list of properties that must match values in the bootstrap environment to be activated. This can be useful to localize an application based on the environment it is running in. For example the following profile could be automatically activated to set the discovery address to use when running in the prod environment based on the environment variable ENVIRONMENT_NAME=PROD being set in that environment. 

...