http://static.springsource.org/spring-flex/docs/1.0.x/reference/html/ch02s04.html

When using the message-broker config tag, a SimpleUrlHandlerMapping is installed that by default maps all incoming DispatcherServlet requests to the Spring-managed MessageBroker using a /*path pattern. The default mapping can be overridden by providing one or more mapping child elements. If you want to provide your own HandlerMapping bean configuration, you can disable the default using the disable-default-mapping attribute of the message-broker tag. The order of the installed SimpleUrlHandlerMapping can be set (for complex scenarios where multiple handler mapping types are installed in the same context) using the mapping-order attribute.

<flex:message-broker>
<flex:mapping pattern="/messagebroker/*" />
</flex:message-broker>

Altering the messagebroker path appears to break flex messaging.

One possible way to structure an "integration" demo would be to deploy both a flex and ICEpush version of the application to the same server. To see if the current demo supported this, the max-blazeds demo was deployed under two different names. Unfortunately, both attempt to instantiate JMS servers and conflict.