« Return to Thread: Quartz payload not appearing in the mule message generated for a scheduled job

RE: Quartz payload not appearing the mule message generated for a scheduled job

by rkhanna :: Rate this Message:

I am having the exact same problem with the Quartz endpoint as the
original email. I am passing a hard-coded value via <quartz:payload>
that I expected to be passed as a String to my component. However, the
payload is showing up as null.

My 2.1.1 config:
<service name=" MyComponent ">
<inbound>
<quartz:inbound-endpoint name="dailyScheduler"
jobName="job1" cronExpression="0 5 4 ? * TUE-SAT">
<quartz:event-generator-job>

<quartz:payload>c:/inbox</quartz:payload>
</quartz:event-generator-job>
</quartz:inbound-endpoint>
</inbound>
<component class="com.novus.MyComponent" />
</service>

This worked fine in 1.4.3 with the following config:
<mule-descriptor name="MyComponent"
implementation="com.novus.MyComponent">
<inbound-router>
<endpoint address="quartz://dailyScheduler">
<properties>
<property name="cronExpression" value="0
5 4 ? * TUE-SAT"/>
<property name="payloadClassName"
value="java.lang.String"/>
<property name="payload"
value="c:/inbox"/>
</properties>
</endpoint>
</inbound-router>
</mule-descriptor>

-----Original Message-----
From: dhenton9000 [mailto:dhenton@...]
Sent: Thursday, November 06, 2008 4:11 PM
To: user@...
Subject: [mule-user] Quartz payload not appearing the mule message
generated for a scheduled job

Below is a simple quartz set up, with a payload of 'foo' run every ten
seconds. the log output shows a null payload. Can anyone help me with
this.
The payload isn't appearing in the message. Docs say that if the payload
property isn't set, the message is null, just as below, but the property
IS
set. Looking at the source the tests only check to see that that the
property is set on the job, not if it shows up in a message.

Any help appreciated.

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:file="http://www.mulesource.org/schema/mule/file/2.1"
xmlns:ftp="http://www.mulesource.org/schema/mule/ftp/2.1"
xmlns:jms="http://www.mulesource.org/schema/mule/jms/2.1"
xmlns:stdio="http://www.mulesource.org/schema/mule/stdio/2.1"
xmlns:smtp="http://www.mulesource.org/schema/mule/smtp/2.1"
xmlns:email="http://www.mulesource.org/schema/mule/email/2.1"
xmlns:quartz="http://www.mulesource.org/schema/mule/quartz/2.1"
xmlns:http="http://www.mulesource.org/schema/mule/http/2.1"
xmlns:pop3="http://www.mulesource.org/schema/mule/pop3/2.1"
xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.1"
xmlns:xm="http://www.mulesource.org/schema/mule/xml/2.1"
xmlns:tcp="http://www.mulesource.org/schema/mule/tcp/2.1"

xmlns:management="http://www.mulesource.org/schema/mule/management/2.1"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-2.5.xsd

http://www.mulesource.org/schema/mule/management/2.1
http://www.mulesource.org/schema/mule/management/2.1/mule-management.xsd
http://www.mulesource.org/schema/mule/http/2.1
http://www.mulesource.org/schema/mule/http/2.1/mule-http.xsd
http://www.mulesource.org/schema/mule/core/2.1
http://www.mulesource.org/schema/mule/core/2.1/mule.xsd
http://www.mulesource.org/schema/mule/ftp/2.1
http://www.mulesource.org/schema/mule/ftp/2.1/mule-ftp.xsd
http://www.mulesource.org/schema/mule/file/2.1
http://www.mulesource.org/schema/mule/file/2.1/mule-file.xsd
http://www.mulesource.org/schema/mule/jms/2.1
http://www.mulesource.org/schema/mule/jms/2.1/mule-jms.xsd
http://www.mulesource.org/schema/mule/smtp/2.1
http://www.mulesource.org/schema/mule/smtp/2.1/mule-smtp.xsd
http://www.mulesource.org/schema/mule/stdio/2.1
http://www.mulesource.org/schema/mule/stdio/2.1/mule-stdio.xsd
http://www.mulesource.org/schema/mule/vm/2.1
http://www.mulesource.org/schema/mule/vm/2.1/mule-vm.xsd
http://www.mulesource.org/schema/mule/email/2.1
http://www.mulesource.org/schema/mule/email/2.1/mule-email.xsd
http://www.mulesource.org/schema/mule/quartz/2.1
http://www.mulesource.org/schema/mule/quartz/2.1/mule-quartz.xsd
http://www.mulesource.org/schema/mule/xml/2.1
http://www.mulesource.org/schema/mule/xml/2.1/mule-xml.xsd
http://www.mulesource.org/schema/mule/tcp/2.1
http://www.mulesource.org/schema/mule/tcp/2.1/mule-tcp.xsd
http://www.mulesource.org/schema/mule/pop3/2.1
http://www.mulesource.org/schema/mule/pop3/2.1/mule-pop3.xsd">
<description>
Demo for quartz payloads in 2.1.1 mule
</description>
<quartz:connector name="quartzConnector" />

<model name="QuartzModel">
<default-service-exception-strategy />
<service name="QuartzService">
<inbound>
<quartz:inbound-endpoint
name="quartzPoll"
repeatCount="-1"
repeatInterval="10000" jobName="quartzJob"
connector-ref="quartzConnector">
<quartz:event-generator-job>

<quartz:payload>foo</quartz:payload>
</quartz:event-generator-job>
</quartz:inbound-endpoint>
</inbound>
<log-component />
</service>

</model>
</mule>

Agents Running: None *
**********************************************************************
14:59:32,826 | INFO | org.mule.component.simple.LogComponent | 41 |
************************************************************************
********
* Message received in service: QuartzService. Content is:
'{NullPayload}'
*
************************************************************************
********
14:59:42,779 | INFO | org.mule.component.simple.LogComponent | 41 |
************************************************************************
********
* Message received in service: QuartzService. Content is:
'{NullPayload}'
*
************************************************************************
********
14:59:52,779 | INFO | org.mule.component.simple.LogComponent | 41 |
************************************************************************
********
* Message received in service: QuartzService. Content is:
'{NullPayload}'
*
************************************************************************
********
15:00:02,779 | INFO | org.mule.component.simple.LogComponent | 41 |
************************************************************************
********
* Message received in service: QuartzService. Content is:
'{NullPayload}'
*
************************************************************************
********
--
View this message in context:
http://www.nabble.com/Quartz-payload-not-appearing-the-mule-message-gene
rated-for-a-scheduled-job-tp20369766p20369766.html
Sent from the Mule - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

This e-mail message, and any attachments, is intended only for the use of the individual or entity identified in the alias address of this message and may contain information that is confidential, privileged and subject to legal restrictions and penalties regarding its unauthorized disclosure and use. Any unauthorized review, copying, disclosure, use or distribution is strictly prohibited. If you have received this e-mail message in error, please notify the sender immediately by reply e-mail and delete this message, and any attachments, from your system. Thank you.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

« Return to Thread: Quartz payload not appearing in the mule message generated for a scheduled job