Skip to Content
Oct 14, 2009 at 10:41 AM

Hot KM Deployment - workaround?



I hace developed a portal application which contains a scheduler task (extendes ISchedulerTask).

This portal application relies all functionality in a portal service located in another portal application.

Each time I deploy the PAR with the scheduler I get a hot KM deployment and I have to restart the J2EE engine, painful...

but (and that's the worst of all) each time I deploy the PAR containing the portal service I get a hot KM deployment (I suppose because the SchedulerTask uses the portal service which has changed).

Any way to modify the portal ser