I assumed task would do a send if a message was injected. So this solves problem:
<definitions xmlns="http://ws.apache.org/ns/synapse";> <task class="org.apache.synapse.startup.tasks.MessageInjector" name="MyProxy"> <property name="to" value="http://localhost:8280/soap/MyProxy"/> <property name="soapAction" value="MyProxy"/> <property name="message"> <doNothing/> </property> <trigger interval="10"/> </task> <sequence name="DoStuff"> <log level="custom"> <property name="MSG" value=">>>>>>> In IN Sequence"/> </log> </sequence> <proxy name="MyProxy"> <target inSequence="DoStuff"/> </proxy> <in> <send/> </in> </definitions> kimhorn wrote: > > Can some one explain what is going on here: > > seting TCPMON to map 8070 to 8280 (Synapse) > > Why does this code not hit PORT 8070 ever, but goes through <in> sequence. > What is the hidden magic going on within Synapse here, can it be > documented ? > > <definitions xmlns="http://ws.apache.org/ns/synapse";> > <task class="org.apache.synapse.startup.tasks.MessageInjector" > name="MyProxy"> > <property name="to" value="http://localhost:8070/soap/MyProxy"/> > <property name="soapAction" value="MyProxy"/> > <property name="message"> > <doNothing/> > </property> > <trigger interval="10"/> > </task> > <sequence name="DoStuff"> > <log level="custom"> > <property name="MSG" value="In IN Sequence"/> > </log> > </sequence> > <proxy name="MyProxy"> > <target inSequence="DoStuff"/> > </proxy> > <in> > <log level="full"/> > </in> > </definitions> > > I would like to use timer via proxy to start a sequence. > Seems REALLY ugly to have to filter the inSequence to do this ? > > > > > > -- View this message in context: http://www.nabble.com/Task-Implementation-tp22427256p22444676.html Sent from the Synapse - User mailing list archive at Nabble.com.
