Murali
I think if you are going to do things such as auditing, identification
etc, for many services and always expose these services via the ESB for
better management, versioning and policy enforcement etc. it would be
easier and better to do this with mediators instead of handlers. Then
you could easily configure the mediators with a common sequence, and
edit any parameters etc much easily than with a module.
However, if you wish to do these closer to the actual services (maybe
for security purposes?) etc, handlers would be better too. I think this
decision is made best by you, considering your environment and use cases
asankha
Gunasekaran, Murali wrote:
Hello Group,
We are currently debating using Synapse and are at crossroads over the
implementation of certain things like auditing, consumer identification as
mediators or plain Axis2 handlers.
Mediators are very flexible and easy to develop and play well with other
mediators currently in Synapse. If we use Axis2 handlers, configuring them on a
per-service basis would involve going the ‘rampart-way’ – i.e. creating a
Neethi assertion that would be embedded as part of the Policy associated with
the service. (services.xml) . Are there any drawbacks in using Mediators (or
Handlers) with respect to the other?
If you could share your opinions/thoughts on what is a technically better solution, I would really appreciate it.
Thanks,
Murali
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.9/1294 - Release Date: 2/22/2008 6:39 PM
