|
»
»
« Return to Thread: Quartz payload not appearing in the mule message generated for a scheduled job
RE: Quartz payload not appearing in the mule message generated for a scheduled job
by antoine.borg
::
Rate this Message:
Hi Rick,
Why not raise JIRAs for these issues?
A
Antoine Borg, Senior Consultant | Tel: +32 28 504 696
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com
-----Original Message-----
From: rotten [mailto:rickotten@...]
Sent: Thursday, November 20, 2008 10:45 PM
To: user@...
Subject: Re: [mule-user] Quartz payload not appearing in the mule message
generated for a scheduled job
I keep getting {NullPayload} also. (with Mule 2.1.1) I tried reading the
data in from a file using the <quartz:payload file="/tmp/mydata" /> syntax.
That doesn't work either. I still get a null payload.
I also noticed that if you put an underscore "_" in the job name, it will
blow up complaining you have null jobname.
[ And while I was at it, I noticed that the "method" tag for the
http:outbound-endpoint doesn't really change the fact that it always does a
POST. (It does change the "method:" header in the HTTP request, but it
still issues a POST to the HTTP server.) ]
Anyway, here is my simple test configuration that generates a null payload:
<quartz:connector name="My-Timer" />
<model name="TimerTester>
<service name="myTest">
<inbound>
<quartz:inbound-endpoint name="Tester"
jobName="jobOne"
connector-ref="My-Timer"
cronExpression="0 0/2 6-20 * *
?">
<quartz:event-generator-job>
<quartz:payload>"Hello"</quartz:payload>
</quartz:event-generator-job>
</quartz:inbound-endpoint>
</inbound>
<outbound>
<pass-through-router>
<stdio:outbound-endpoint system="OUT" />
</pass-through-router>
</outbound>
</service>
</model>
I guess my next solution is to build a component that creates the payload
since I can't get quartz to do it for me. (Unless someone has an idea as to
why this isn't working.)
dhenton9000 wrote:
>
> 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.
>
> **********************************
>
--
View this message in context:
http://www.nabble.com/Quartz-payload-not-appearing-in-the-mule-message-gener
ated-for-a-scheduled-job-tp20369766p20610615.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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Why not raise JIRAs for these issues?
A
Antoine Borg, Senior Consultant | Tel: +32 28 504 696
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com
-----Original Message-----
From: rotten [mailto:rickotten@...]
Sent: Thursday, November 20, 2008 10:45 PM
To: user@...
Subject: Re: [mule-user] Quartz payload not appearing in the mule message
generated for a scheduled job
I keep getting {NullPayload} also. (with Mule 2.1.1) I tried reading the
data in from a file using the <quartz:payload file="/tmp/mydata" /> syntax.
That doesn't work either. I still get a null payload.
I also noticed that if you put an underscore "_" in the job name, it will
blow up complaining you have null jobname.
[ And while I was at it, I noticed that the "method" tag for the
http:outbound-endpoint doesn't really change the fact that it always does a
POST. (It does change the "method:" header in the HTTP request, but it
still issues a POST to the HTTP server.) ]
Anyway, here is my simple test configuration that generates a null payload:
<quartz:connector name="My-Timer" />
<model name="TimerTester>
<service name="myTest">
<inbound>
<quartz:inbound-endpoint name="Tester"
jobName="jobOne"
connector-ref="My-Timer"
cronExpression="0 0/2 6-20 * *
?">
<quartz:event-generator-job>
<quartz:payload>"Hello"</quartz:payload>
</quartz:event-generator-job>
</quartz:inbound-endpoint>
</inbound>
<outbound>
<pass-through-router>
<stdio:outbound-endpoint system="OUT" />
</pass-through-router>
</outbound>
</service>
</model>
I guess my next solution is to build a component that creates the payload
since I can't get quartz to do it for me. (Unless someone has an idea as to
why this isn't working.)
dhenton9000 wrote:
>
> 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.
>
> **********************************
>
--
View this message in context:
http://www.nabble.com/Quartz-payload-not-appearing-in-the-mule-message-gener
ated-for-a-scheduled-job-tp20369766p20610615.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
---------------------------------------------------------------------
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
| Free embeddable forum powered by Nabble | Forum Help |
