Hi, I am trying to figure out a way to add runtime weaving of aspects into my service mix message flows.
I am trying to acomplish this using Spring-AOP. As far as I can see, when one deploys a SU to a component, the component processes the xbean.xml, creates a Spring application context from that and starts the SU as a Spring app in its Spring container. Using the SUs xbean file one can introduce advices to the component. I am asking myself if that is what I am looking for. Am I correct, that when it comes to the message flows, normalized messages are routed from endpoint to endpoint, not going through the component at all? I.e. no advice will be picked up since in the SUs I can only advise the component? So, should I better look for a way to advise the endpoints? If "yes", are endpoints also managed by Spring? Where can I find the bean factory managing the endpoint (Where in the code is it created?)? Or is there no way intercepting the messages during the flow? Would compiletime weaving the only possible way to achieve what I want to do? Thanks a lot in advance for any help on this! Cheers, Oliver. -- View this message in context: http://www.nabble.com/Runtime-weaving-of-aspects-into-service-mix-message-flows-tf3999795s12049.html#a11359925 Sent from the ServiceMix - User mailing list archive at Nabble.com.
