Hi Peter,
I have cloned your fork with the fix and build the bundles. How can I actually
point eclipse (bndtools) to use the newly built bundles?
Any pointers would help. Many thanks.
---------------------------------------------
I've created a fix, please test.
> On 12 Jun 2017, at 17:51, Karel Haeck <karel.ha...@telenet.be
> <mailto:karel.ha...@telenet.be>> wrote:
>
>
> There is an error in the initialization of the enroute InternalSchedulerImpl
> component. It was logged as issue 70 on github repo osgi.enroute.bundles
> (https://github.com/osgi/osgi.enroute.bundles/issues/70
> <https://github.com/osgi/osgi.enroute.bundles/issues/70>
> <https://github.com/osgi/osgi.enroute.bundles/issues/70
> <https://github.com/osgi/osgi.enroute.bundles/issues/70>>)
> but the issue probably got lost when the code was moved to github repo
> osgi.enroute
>
>
> On 12/06/2017 10:28, Misja Heuveling wrote:
>> Hi All,
>>
>> I am trying to build a bundle which would run a scheduled service to do some
>> background tasks at a regular interval.
>>
>> I used the blog post from oktober 2015 to get started so I made the
>> following service:
>>
>> @Component(
>> property = CronJob.CRON + "=* * * * * * ?"
>> )
>> public class CronComponent implements CronJob
>> @Override
>> public void run(Object data) throws Exception {
>> System.out.println("Cron Component");
>> }
>> }
>> This service should run every second. When I run this bundle nothing
>> actually happens....
>> When I create a service tracker for the scheduler service and initiate the
>> service tracker in the bundle Activator I get a NullPointerException with
>> the message the cron syntax is incorrect.
>> When I stop and start the bundle in the running session all of a sudden see
>> the println statement output.
>> It seems I need to start the Scheduler Service or the CronComponent service
>> in some different order. (I assume the Scheduler service needs to be running
>> first...)
>> How could this be done?
>> With kind regards,
>> Misja Heuveling
>>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>> <mailto:osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> <mailto:osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> <https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.osgi.org/pipermail/osgi-dev/attachments/20170613/15a83ac0/attachment-0001.html
<http://mail.osgi.org/pipermail/osgi-dev/attachments/20170613/15a83ac0/attachment-0001.html>>
------------------------------_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
