Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JobDataMap does not persist when associated with triggers #9

Open
JG00329142 opened this issue Oct 16, 2016 · 1 comment
Open

JobDataMap does not persist when associated with triggers #9

JG00329142 opened this issue Oct 16, 2016 · 1 comment

Comments

@JG00329142
Copy link

HI, I am using redisStore for Quartz.
I see that if I pass data using JobDetail.JobDataMap.put("key","value") I can access it when my job fires doing context.getJobDetail().getJObDataMap()

But if i try to pass JobDataMap via the trigger that i used to trigger the job, trigger1.getJobDataMap().put("key","value"), then i cannot access the value when my job fires bu doing context.getTrigger().getJobDataMap().getString("key");

the above works if i use RAMStore instead of RedisStore.

Please help resolve this issue. it is urgent.
Please let me know if i am missing something here.

Thanks.

@JG00329142
Copy link
Author

HI Futher update, I was reading the RedisJobStore.java and I see that storeTigger and retriveTrigger functions NOWHERE have any reference to the JobDataMap which may have been associated with the trigger while it was created.

storeJob and retreiveJob methods in the same class, DO HAVE reference to the jobDataMap associated with Job.

I am not Sure if i Am looking at the right place, but just wanted to put my observations here, Just if they may help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant