Conflict between usage of EAI patterns within ESB and SOA boundaries

I am maintaining a large retail business systems, segmented into SOA boundaries. Lately, we have decided to implement messaging to send events from one boundary to the other. These events are sometimes based upon complex business logic. For example, receiving an order may trigger half a dozen other events provided certain conditions are met. I have two options here to send message(s) to the ESB: 1. Write this complex business login in the publisher's boundary and publish 6 events through subtopics, or 2 Publish just one event to the ESB and write this complex business logic of creating six events within ESB using EAI patterns.

So, my question is, by writing the complex logic within ESB, am I not violating the principle of "Separation of Concerns" by peeking into the data structures of Order Entry system?