Hi,
I am trying to get some tasks scheduled when the application starts up. I have done this in 2.8 applications without any problem - just uncomment the 'oxf.context-initialized-processor.name' context param in web.xml and then in properties.xml point to a pipeline with a call to the scheduler. However I have just tried the same thing in a 3.0 application with no luck. No messages appear in the logs and so either I am missing something or it is failing silently. Anyone have any ideas? Thanks in advance, Dave -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
David,
It is possible that context listeners don't read properties.xml in 3.0. The default context listeners since 3.0 are entirely setup in web.xml. I suggest you check out the web.xml of a recent build and do a similar setup. -Erik David Sinclair wrote: > Hi, > > I am trying to get some tasks scheduled when the application starts up. > I have done this in 2.8 applications without any problem - just > uncomment the 'oxf.context-initialized-processor.name' context param in > web.xml and then in properties.xml point to a pipeline with a call to > the scheduler. > > However I have just tried the same thing in a 3.0 application with no > luck. No messages appear in the logs and so either I am missing > something or it is failing silently. Anyone have any ideas? > > Thanks in advance, > > Dave Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Dave,
As another option for scheduling jobs, I have integrated quartz job scheduler with orbeon. Both systems work pretty well together and you get a lot of flexibility and control for pipelines scheduling. I am able to schedule pipelines when the server starts up. This option may be useful if you have a lot of scheduled pipelines that you want to track, if you only need to schedule jobs at start up maybe you don't need all of this. Jordi -----Mensaje original----- De: Erik Bruchez [mailto:[hidden email]] En nombre de Erik Bruchez Enviado el: lunes, 21 de agosto de 2006 20:28 Para: [hidden email] Asunto: Re: [ops-users] Scheduler question David, It is possible that context listeners don't read properties.xml in 3.0. The default context listeners since 3.0 are entirely setup in web.xml. I suggest you check out the web.xml of a recent build and do a similar setup. -Erik David Sinclair wrote: > Hi, > > I am trying to get some tasks scheduled when the application starts up. > I have done this in 2.8 applications without any problem - just > uncomment the 'oxf.context-initialized-processor.name' context param in > web.xml and then in properties.xml point to a pipeline with a call to > the scheduler. > > However I have just tried the same thing in a 3.0 application with no > luck. No messages appear in the logs and so either I am missing > something or it is failing silently. Anyone have any ideas? > > Thanks in advance, > > Dave Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Jordi,
Thanks for this - I dont think we need this for our current project but in the past we have certainly wanted more than the ops scheduler gives us. I will bear this in mind for the future! Dave Jordi Amatller wrote: > Dave, > > As another option for scheduling jobs, I have integrated quartz job > scheduler with orbeon. > Both systems work pretty well together and you get a lot of flexibility and > control for pipelines scheduling. I am able to schedule pipelines when the > server starts up. > This option may be useful if you have a lot of scheduled pipelines that you > want to track, if you only need to schedule jobs at start up maybe you don't > need all of this. > > Jordi > > > > -----Mensaje original----- > De: Erik Bruchez [mailto:[hidden email]] En nombre de Erik Bruchez > Enviado el: lunes, 21 de agosto de 2006 20:28 > Para: [hidden email] > Asunto: Re: [ops-users] Scheduler question > > David, > > It is possible that context listeners don't read properties.xml in 3.0. > The default context listeners since 3.0 are entirely setup in web.xml. I > suggest you check out the web.xml of a recent build and do a similar setup. > > -Erik > > David Sinclair wrote: > >> Hi, >> >> I am trying to get some tasks scheduled when the application starts up. >> I have done this in 2.8 applications without any problem - just >> uncomment the 'oxf.context-initialized-processor.name' context param in >> web.xml and then in properties.xml point to a pipeline with a call to >> the scheduler. >> >> However I have just tried the same thing in a 3.0 application with no >> luck. No messages appear in the logs and so either I am missing >> something or it is failing silently. Anyone have any ideas? >> >> Thanks in advance, >> >> Dave >> > > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
In reply to this post by Erik Bruchez
Erik,
I have just tried the following code in web.xml (based on a build from the 17th of this month). <context-param> <param-name>oxf.context-initialized-processor.name</param-name> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> </context-param> <context-param> <param-name>oxf.context-initialized-processor.input.config</param-name> <param-value>oxf:/talent-management/business-logic/scheduled-tasks/schedule-tasks.xpl</param-value> </context-param> ... my pipleine does not seem to run on startup (I have added debug line) and there are no errors in the logs at startup. Does this look about right to you? Dave Erik Bruchez wrote: > David, > > It is possible that context listeners don't read properties.xml in > 3.0. The default context listeners since 3.0 are entirely setup in > web.xml. I suggest you check out the web.xml of a recent build and do > a similar setup. > > -Erik > > David Sinclair wrote: >> Hi, >> >> I am trying to get some tasks scheduled when the application starts >> up. I have done this in 2.8 applications without any problem - just >> uncomment the 'oxf.context-initialized-processor.name' context param >> in web.xml and then in properties.xml point to a pipeline with a call >> to the scheduler. >> >> However I have just tried the same thing in a 3.0 application with no >> luck. No messages appear in the logs and so either I am missing >> something or it is failing silently. Anyone have any ideas? >> >> Thanks in advance, >> >> Dave > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
David Sinclair wrote:
> Erik, > > I have just tried the following code in web.xml (based on a build from > the 17th of this month). > > <context-param> > <param-name>oxf.context-initialized-processor.name</param-name> > > <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> > </context-param> > <context-param> > > <param-name>oxf.context-initialized-processor.input.config</param-name> > > <param-value>oxf:/talent-management/business-logic/scheduled-tasks/schedule-tasks.xpl</param-value> > > </context-param> > ... my pipleine does not seem to run on startup (I have added debug > line) and there are no errors in the logs at startup. Does this look > about right to you? Something like: <listener> <listener-class>org.orbeon.oxf.webapp.OPSServletContextListener</listener-class> </listener> <listener> <listener-class>org.orbeon.oxf.webapp.OPSSessionListener</listener-class> </listener> -Erik -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Erik Bruchez wrote:
> At first sight, yes. Are the OPS listeners hooked-up in web.xml? > Something like: > > <listener> > <listener-class>org.orbeon.oxf.webapp.OPSServletContextListener</listener-class> > > </listener> > <listener> > <listener-class>org.orbeon.oxf.webapp.OPSSessionListener</listener-class> > </listener> > Dave > -Erik > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
In reply to this post by Erik Bruchez
> At first sight, yes. Are the OPS listeners hooked-up in web.xml? > Something like: > > <listener> > <listener-class>org.orbeon.oxf.webapp.OPSServletContextListener</listener-class> > > </listener> > <listener> > <listener-class>org.orbeon.oxf.webapp.OPSSessionListener</listener-class> > </listener> > These lines were commented out. I have now uncommented them and things have sprung into live - thanks Erik! Dave > -Erik > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |