Good and useful, thanks to you.
So I've prepared this "dummy" step-by-step job's migration from 5.x to 6.0:
1) implement your com.liferay.portal.scheduler.job.MessageSenderJob (was com.liferay.portal.kernel.job.IntervalJob)
2) implement your com.liferay.portal.kernel.scheduler.SchedulerEngine (was com.liferay.portal.kernel.job.Scheduler,
that was contain an org.quartz.Scheduler)
3) previously, you put your custom Schedulerxxx.java in liferay-portlet(-ext).xml under <scheduler-class> tag,
now to go live your job class, put a bean in scheduler-spring(-ext).xml (not recommended, see 3-a) )
ALSO take a look to theese points:
2-a) implement a class that uses IntervalTrigger or use the trigger that you prefer, and
instantiate for use in your SchedulerEnginexxx.schedule() call (the one used for IntervalJob was IntervalTrigger...
but CronTrigger it's a good thing too)
3-a) as you can see, in public class QuartzSchedulerEngineImpl implements SchedulerEngine:
1....
2schedulerFactory.initialize(PropsUtil.getProperties("org.quartz.", false));
3...
It Get out jobs from somewhere properties, so you can put simply in portal-ext.properties
your custom scheduler (NOT recommended, for me):
1....
2org.quartz.scheduler.instanceName=QuartzSchedulerEngineInstance
3....
(RECOMMENDED, 'cause this way adds your schedulers to default one..)
Add your custom Job(s) under (don't worry about wrong class path in comment,
the right one is like above: com.liferay.portal.kernel.scheduler.SchedulerEngine):
1
2... #
3 # Input a list of comma delimited class names that implement
4 # com.liferay.portal.kernel.job.Scheduler. These classes allow jobs to be
5 # scheduled on startup. These classes are not associated to any one portlet.
6 #
7 scheduler.classes= com.ext.liferay.portal.kernel.scheduler.SchedulerEnginexxx, ....
Bitte melden Sie sich an, um diesen Inhalt als unangebracht zu kennzeichnen.