This content has been marked as final.
Show 4 replies
-
1. Re: ScheduledEventListener
kconner Dec 2, 2009 5:06 AM (in response to tomeicher)You shouldn't need to specify the actions, can you show us your jboss-esb.xml?
-
2. Re: ScheduledEventListener
tomeicher Dec 2, 2009 5:22 AM (in response to tomeicher)Hi Kevin,
well, looking at the jbossesb-1.1.0.xsd (also 1.0.1), everything in
jbossesb/services/service/actions/action
is "minOccurs 1", so I think a listener that does not produce a message
doesn't make sense, does it ?<service category="XXJmsDefault" description="Monitor error queues" invmScope="GLOBAL" name="XXErrorMonitor"> <listeners> <scheduled-listener name="altertingListenerPosLog" schedule-frequency="60" event-processor="xxx.AlertingListener"> <property name="queueName" value="queue/XX_POS_LOG_ERROR"/> </scheduled-listener> </listeners> <actions> <!-- action is minOccurs=1 ... need to put a NOOP action here... --> <action class="xxx.NOOPAction" name="alertingNOOPAction"/> </actions> </service>
Cheers, Tom. -
3. Re: ScheduledEventListener
kconner Dec 2, 2009 6:02 AM (in response to tomeicher)Yes, but actions is minOccurs="0"
<xsd:element maxOccurs="1" minOccurs="0" ref="jesb:actions" />
The pipeline should only be instantiated if using ScheduledEventMessageComposer, in which case it will need actions.
Kev -
4. Re: ScheduledEventListener
tomeicher Dec 2, 2009 6:45 AM (in response to tomeicher)Ah, funny how one can check, and still not see the obvious...
Sorry about that.
Cheers, Tom.