Hi Jeff, You got it, the configuration for the clone mediator should be sequence but not inSequence. You will only come across the configuration point inSequence in proxy. Your following reasoning is exactly the idea behind not having two in and out Sequences.
Thanks, Ruwan On Thu, Aug 14, 2008 at 11:52 PM, Jeff Davis <[EMAIL PROTECTED]> wrote: > Never mind on this -- I should have used <sequence> instead of > <InSequence>. > I suspect that's because it's really because clone is asynchronous, and > doesn't anticipate an out. > > jeff > > > On Thu, Aug 14, 2008 at 12:16 PM, Jeff Davis <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I'm attempting to use the clone mediator within an on-fail block, and was > > attempting something like the following: > > > > <clone continueParent="true"> > > <target > > > <endpoint> > > <address format="soap12" uri=" > > http://localhost:8280/soap/EsperService"/> > > </endpoint> > > <inSequence> > > <xslt key="xslt-key-esper-csv-err"> > > <property name="errorType" value="XML Validation Error"/> > > </xslt> > > </inSequence> > > </target> > > </clone> > > > > For whatever reason, I can never get the mediators within the > <inSequence> > > to fire (processing never seems to traverse into it). I tried using the > > alternative method whereby I specify the @inSequence attribute of the > target > > element, but there to, it never fires. > > > > If it's a bug, I can go ahead and submit a Jira. > > > > jeff > > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
