Our current application (which we're refactoring) is a fairly traditional J2EE model built on session and entity beans. We're moving to Tapestry, Spring and Hiibernate.
One difference, though, is that the old app, instead of having a standard facade, is based off command/event objects, which are passed to a single session bean on the biz tier. That bean then uses XML to map the event to EventHandlers, which then access the entity beans and perform the business logic.
In our refactoring, we haven't yet decided whether to unroll this command facade into a standard facade with multiple manager beans, or keep the event model and have the central manager then delegate to other handlers.
Most applications using Spring (AppFuse, Hispacta, all the PetStores) use the multiple manager implementation. While I find that way simpler (no event objects to track), I can't see a reason why the command way is inherently inferior.
Has anyone done the command/event way in Spring, and is the facade pattern superior?