Ok, and at that point the "completely refactored" mediator would be in the nightly build. Is that correct?
On 4/1/09 4:15 PM, "Andreas Veithen" <[email protected]> wrote: > I was planning to implement the final version of this mediator before > next Tuesday. If you can wait a couple of days... > > Andreas > > On Wed, Apr 1, 2009 at 22:05, Keith Bohnenberger > <[email protected]> wrote: >> For now, would your recommendation be for me to write a custom mediator? >> >> >> On 4/1/09 3:55 PM, "Andreas Veithen" <[email protected]> wrote: >> >>> It is currently in synapse-experimental. Note that before 1.3 this >>> mediator will be completely refactored to support a wider range of use >>> cases. >>> >>> Andreas >>> >>> On Wed, Apr 1, 2009 at 21:45, Keith Bohnenberger >>> <[email protected]> wrote: >>>> When is 1.3 coming out? >>>> Is the detach mediator in the nightly build? >>>> >>>> Thanks >>>> >>>> Keith >>>> >>>> >>>> On 4/1/09 3:39 PM, "Asankha C. Perera" <[email protected]> wrote: >>>> >>>>> Hi Keith >>>>>> I have a xml message coming into the ESB >>>>>> The xml messages contains a list of elements that I need to validate. >>>>>> If an element in the list fails validation I would like to remove it from >>>>>> the list. >>>>>> I would then like to send the incoming xml messages minus the elements >>>>>> that >>>>>> failed validation to the next step in the process. >>>>>> >>>>>> I've been playing with the iterate and validate mediators and I've looked >>>>>> at >>>>>> the aggregate mediator but I can't seem to pull it off. >>>>>> >>>>>> Any suggestions? >>>>>> >>>>> I do not think using the iterate mediator is suitable here, since it >>>>> splits the message into multiple. It would be better to use just >>>>> validate, and pass the elements to be validated - if thats a well known >>>>> list. Then you could remove those which fail using the new detach >>>>> mediator which would be available with 1.3.. >>>>> >>>>> cheers >>>>> asankha >>>> >>>> This communication, along with any attachments, is covered by federal and >>>> state law governing electronic communications and may contain company >>>> proprietary and legally privileged information. >>>> If the reader of this message is not the intended recipient, you are hereby >>>> notified that any dissemination, distribution, use or copying of this >>>> message >>>> is strictly prohibited. >>>> If you have received this in error, please reply immediately to the sender >>>> and delete this message. Thank you. >>>> >>>> >> >> This communication, along with any attachments, is covered by federal and >> state law governing electronic communications and may contain company >> proprietary and legally privileged information. >> If the reader of this message is not the intended recipient, you are hereby >> notified that any dissemination, distribution, use or copying of this message >> is strictly prohibited. >> If you have received this in error, please reply immediately to the sender >> and delete this message. Thank you. >> >> This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
