Differences between revisions 1 and 2
Revision 1 as of 2006-02-15 16:38:33
Size: 836
Comment:
Revision 2 as of 2009-09-20 23:46:23
Size: 833
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Sometimes you need to install background processes in your portal application. Application specific tasks (i.e. scheduling) should be done in the portal application rather than in the Jetspeed portal (see [wiki:Jetspeed2/HowToUseScheduler How to use the Scheduler service]). Sometimes you need to install background processes in your portal application. Application specific tasks (i.e. scheduling) should be done in the portal application rather than in the Jetspeed portal (see [[Jetspeed2/HowToUseScheduler|How to use the Scheduler service]]).

How to manage background processes in my portal application

Sometimes you need to install background processes in your portal application. Application specific tasks (i.e. scheduling) should be done in the portal application rather than in the Jetspeed portal (see How to use the Scheduler service).

To achieve this, just write a class that implements the ServletContextListener interface and reference it in the web.xml of the portal application.

<listener>
    <listener-class>SampleContextListener</listener-class>
</listener> 

The methods

contextInitialized(ServletContextEvent sce) 

contextDestroyed(ServletContextEvent sce)

can be used to do things on deploy, redeploy and undeploy of the application.

Jetspeed2/HowToManageBackgroundProcessesInMyPortalApplication (last edited 2009-09-20 23:46:23 by localhost)