You can configure the IBM® WebSphere® Portlet Factory servlet to dynamically load linked Java object, profile set manager and regen classes.
Normally, the WebSphere Portlet Factory servlet loads class files only at startup time. A class file might be used by a Java-based web service or a Linked Java Object builder. You might want to enable dynamic class loading to ensure that the service or object calls the most recent version of the class file available.
In normal operating mode, class files in the classpath are loaded by the default ClassLoader of the JVM each time the application server is started. However, if the class file changes while the application server is running (for instance if you recompile a Java file) the default ClassLoader does not reload the class.
In a development environment, you may want to reload a class more frequently. However, you may not want (or be able) to restart the application server every time you make a change to a class file. This is when dynamic class loading can be useful.
Be aware that you incur a performance cost when dynamic class loading is enabled. When dynamic class loading is enabled, class file time stamps are checked for each call a model makes to a service or linked object class. Given this, you are wise to enable dynamic class loading only in a development environment and to disable it in a development or production environment.
In development/production environments, make sure that all service class files are in the WebSphere Portlet Factory servlet's classpath.
It is possible to configure the WebSphere Portlet Factory servlet to dynamically load Java class files without requiring the application server to restart. You might want to do this if you share a development WebSphere Portlet Factory servlet and frequently update the Java classes used by your services.
Depending upon security implementation approach, dynamic class loading might be available on your application server.
Parent topic: Configuring dynamic class loading