this in fact is so simple, it must be mentioned in the faq.
http://wiki.apache.org/portals/Jetspeed2/HowToManageBackgroundProcessesInMyPortalApplication
thanks Aaron
Aaron Evans wrote:
> Yeah, or more simply, you could just add a ServletContextListener to the
> portal application and do whatever
Yeah, or more simply, you could just add a ServletContextListener to the
portal application and do whatever you need to do in the contextInitialized
method.
On 2/14/06, Joachim Müller <[EMAIL PROTECTED]> wrote:
>
> Hi.
>
> I've found a way to hook into (re)deployment without changing the
> Jetspee
Hi.
I've found a way to hook into (re)deployment without changing the
Jetspeed codebase. I just define a new Servlet (i.e. SchedulerServlet)
in the web.xml of the portal application and tell the application server
to load it on startup.
Implementing the init and the destroy method of the servlet
Joachim Müller wrote:
Hi.
I there a way to hook into the deployment process when a portal
application is (re)deployed? I need a kind of "startup method" of the
portal application to start some background processes of the application.
thanks, regards,
joachim
yes, you can either extend the P
Hi.
I there a way to hook into the deployment process when a portal
application is (re)deployed? I need a kind of "startup method" of the
portal application to start some background processes of the application.
thanks, regards,
joachim
--
. frankfurt am main, 4°c, die gefühlte temperatur