Keith,
The problem with the XSLT mediator is indeed that it replaces the part
of the message that is the source for the XSL transformation, i.e. the
input of the transformation will be no longer available after the
transformation. We are working on a set of mediators that allow to
copy part of a message; they could be used to preserve the original
message. Actually I would assume that any logic (returning true or
false) implemented by an XSLT could also be implemented using XPath.
Is that not possible in your case?
< end quote >
The logic that we need for "filtering" is pretty complex and can't
reasonably be done with xpath.
We run an xslt to check for messages that should get filtered out. The xslt
returns a report not a transformation of the incoming message. Based on the
results in the report, we allow the message through or we drop it and log
some info on why we dropped it.
I'm thinking of writing a custom mediator to handle this but I'm still new
to Synapse so I'm not sure if that is the best path to go down. Any
alternative suggestions would be appreciated.
Thanks
Keith
--
View this message in context:
http://www.nabble.com/need-to-filter-based-on-results-of-an-xslt-tp22705788p22724155.html
Sent from the Synapse - User mailing list archive at Nabble.com.
