Hi,
I've got a couple of questions regarding routing and auditing in SM:
- How does containerbased routing work?
Looking at the descriptions in
"http://servicemix.org/How+does+routing+work+in+JBI"; I see that it´s
possible to let the container decide. How is this decision made and is
the container pluggable so I can add different policys? Or is the
prefered way to create a component that does the routing for me?
"# a component can let the container find the service to invoke
operations on
# a component can give the container some hints by specifying the
service, interface and/or operation to invoke and then let the container
choose which physical service endpoint to invoke using some choosing
algorithm (maybe using rules or policy driven metadata). Remember there
may be many services available for a specific service, interface and
operation names"
- Are there any plans regarding auditing and/or logging in ServiceMix?
In our usecase it is *very* important to be able to monitor the
different steps in a flow inside servicemix. And not just the message
count but sometimes the whole message.
Is there a best practice in doint auditing and logging inside SM?
I had an idea that I would derive a baseclass for our components based
on the PojoSupport and use JMX to dynamically add or remove an audit
endpoint for the component.
Every call to the component would also do an InOnly exhange with the
audit-endpoint if it is enabled. Is this a feasible solution?
Regards Mats
