Hi Kishanthan,
I will remove that parent first configuration in the wso2as-web.xml.
According to the Java docs of ClassLoader[1] the child classes are only
need to register as parallel capable. Since the tomcat
WebappClassLoaderBase is registering it as parallel capable, we only need
to call the
Did we also look into how we can use ParallelWebappClassLoader with our
class loaded enhancements?
https://tomcat.apache.org/tomcat-8.0-doc/config/loader.html#Standard_Implementation
On Sun, Mar 13, 2016 at 11:42 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:
> If tomcat is already
If tomcat is already providing a way to configure the parent first
behaviour we should use that instead of our own. But most of the times, we
do not need to change this class loading behaviour to parent first as we
mostly use the default (child first) behaviour. This config was added
during OSGi
Hi all,
Currently in the wso2as-web.xml contains a parent first configuration
parameter per web app class loading. Also tomcat it self provide
configurable parent first class loading behavior in side the context.xml.
One benefit of using the tomcat configuration for controlling parent first
