This release changes the behavior of Hornet channel mapping when two services result in the the same channel name being used. When two services result in the same channel name being used on the same message bus Hornet will now fail during messaging configuration to
prevent messages from the two services flowing over the same channel and reaching unintended recipients.

Case in which this can occur include:

• Two services with different namespaces but the same service name using the same channel name. For example if both com.neeve.service1.OrdersService and com.neeve.service2.OrdersService declare the channel 'neworders' the would both result in a channel named ordersservice-neworders being declared in conflict.
• Two services different names but that don't use service name prefixing using the same channel name. For example if both com.neeve.service1.OrdersService and com.neeve.service2.EventService declare the channel 'neworders' the would both result in a channel named 'neworders' being declared in conflict.

Note that in either of the above cases if the 'neworders' channel where to declare itself on a different bus this would not be considered a conflict since each channel would be distinct and configured independently.
Compatibility Notes:

Existing applications that had service channel name conflicts will now fail to start with this release. The env property nv.toa.failonchannelnamecollision=false can be set to revert to the old behavior or ignoring such collisions.