|
»
»
Quartz payload not appearing in the mule message generated for a scheduled job
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Quartz payload not appearing in the mule message generated for a scheduled job
by dhenton9000
::
Rate this Message:
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}' * ******************************************************************************** |
|
|
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 |
|
|
RE: Quartz payload not appearing the mule message generated for a scheduled job
by rkhanna
::
Rate this Message:
Okay, we found the solution to this (it is already logged as a JIRA
issue) and wanted to share. The solution is to replace the following: <quartz:event-generator-job> <quartz:payload>c:/inbox</quartz:payload> </quartz:event-generator-job> With the following: <property key="payload" value="c:/inbox"/> <quartz:event-generator-job/> Hope that helps others out there. Best, Rishi -----Original Message----- From: Rishi Khanna [mailto:rishi@...] Sent: Friday, November 07, 2008 10:50 AM To: user@... Subject: RE: [mule-user] Quartz payload not appearing the mule message generated for a scheduled job 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 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 |
|
|
Re: Quartz payload not appearing in the mule message generated for a scheduled job
by rotten
::
Rate this Message:
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.)
|
|
|
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 |
|
|
RE: Quartz payload not appearing in the mule message generated for a scheduled job
by rotten
::
Rate this Message:
You are right, I should. So I did.
Hope that helps. Sorry. I was just a little frustrated at the end of the day yesterday to hit three bugs in a row right before I went home.
|
|
|
RE: Quartz payload not appearing in the mule message generated for a scheduled job
by rkhanna
::
Rate this Message:
Rick,
I had posted the work around that I discovered for this issue about 2 weeks ago. You can read it here: http://www.nabble.com/Quartz-payload-not-appearing-in-the-mule-message-g enerated-for-a-scheduled-job-to20369766.html I found the work around in an existing JIRA ticket for this bug. Hope that helps you. Rishi -----Original Message----- From: rotten [mailto:rickotten@...] Sent: Friday, November 21, 2008 9:41 AM To: user@... Subject: RE: [mule-user] Quartz payload not appearing in the mule message generated for a scheduled job You are right, I should. So I did. Hope that helps. Sorry. I was just a little frustrated at the end of the day yesterday to hit three bugs in a row right before I went home. antoine.borg wrote: > > 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 > > > > -- View this message in context: http://www.nabble.com/Quartz-payload-not-appearing-in-the-mule-message-g enerated-for-a-scheduled-job-tp20369766p20622403.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 |
| Free embeddable forum powered by Nabble | Forum Help |
